microsoftgraph / microsoftgraph/msgraph-sdk-java

Sending SMIME messages with sendMail endpoint is broken.

Abierto
#2,544 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

status:waiting-for-triage type:bug
Lenguaje dominante
Java
Estrellas
444
Forks
154
Merge medio
18 h 28 min
PR fusionados (30 d)
4

Descripción

Describe the bug

Hello,

We are using Microsoft Graph Java SDK to send encrypted SMIME Messages.
We are already encrypting the content and provide a full MIME document to endpoint:
https://graph.microsoft.com/v1.0/me/sendMail

For example our MIME Message looks like this (saved on content variable):

Date: Tue, 10 Feb 2026 11:24:45 +0000 (UTC)
From: HenriettaM@xyz.onmicrosoft.com
To: xxx-test@gmx.de
Message-ID: <....>
Subject: Test2
MIME-Version: 1.0
Content-Type: application/pkcs7-mime; name="smime.p7m"; smime-type=authEnveloped-data
Content-Transfer-Encoding: base64

MIAGCyqGSIb3DQEJEAEXoIAwgAIBADGCAdswggHXAgEAMIGPMHcxCzAJBgNVBAYTAkRFMQwwCgYD
...

We are using the following code snipplet to send the Email:

initializeGraphClient();
String encoded = Base64.getEncoder().encodeToString(content.getBytes());

RequestInformation requestInfo = new RequestInformation();
requestInfo.httpMethod = HttpMethod.POST;
requestInfo.urlTemplate = "{+baseurl}/users/{+email}/sendMail";
requestInfo.pathParameters = new HashMap<>();
requestInfo.pathParameters.put("baseurl", "https://graph.microsoft.com/v1.0");
requestInfo.pathParameters.put("email", config.getMailbox());
requestInfo.headers.put("Content-Type", Set.of("text/plain"));
requestInfo.setContentFromScalar(client.getRequestAdapter(), "text/plain", encoded);

HashMap<String, ParsableFactory< ? extends Parsable>> errorMapping = new HashMap<>();
errorMapping.put("4XX", ODataError::createFromDiscriminatorValue);
errorMapping.put("5XX", ODataError::createFromDiscriminatorValue);

client.getRequestAdapter().sendPrimitive(requestInfo, errorMapping, Void.class);

However our SMIME content is converted into an attachment and send as an attachment packed into a multipart/mixed structure by sending the Email.

Here is what we get on the reciever side:

Content-Type: multipart/mixed;
	boundary="_002_155174533371770722695547_"
MIME-Version: 1.0

--_002_155174533371770722695547_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

--_002_155174533371770722695547_
Content-Type: application/pkcs7-mime; name="smime.p7m"
Content-Description: smime.p7m
Content-Disposition: attachment; filename="smime.p7m"; size=4483;
	creation-date="Tue, 10 Feb 2026 11:33:38 GMT";
	modification-date="Tue, 10 Feb 2026 11:33:38 GMT"
Content-ID: <C06558A1F17AA04CAE95309F8C325E89@namprd19.prod.outlook.com>
Content-Transfer-Encoding: base64

MIAGCyqGSIb3DQEJEAEXoIAwgAIBADGCAdswggHXAgEAMIGPMHcxCzAJBgNVBAYTAkRFMQwwCgYD

Can you fix sending a SMIME by using this sendMail endpoint or is there any alternative ways for sending SMIME with Graph API?
We basically followed the Example 4 in this documentation page:

https://learn.microsoft.com/en-us/graph/api/user-sendmail?view=graph-rest-1.0&tabs=http#example-4-send-a-new-message-using-mime-format

Expected behavior

Sending SMIME messages should work with the sendMail endpoint when Content-Type is provided as text/plain.

How to reproduce

See the code snipplet above for example code.
We can also provide a full SMIME example content if you want.

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

No response

Configuration

No response

Other information

No response

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comience con el ejemplo MIME de sendMail en la documentación vinculada de Microsoft Graph y reproduzca la solicitud RequestInformation mostrada en el issue, incluidos su Content-Type y el cuerpo codificado. Compare la solicitud con el mensaje multipart/mixed recibido para determinar si el comportamiento corresponde al Java SDK o al endpoint de Graph. Se considera terminado con una corrección confirmada del SDK, o con una limitación documentada de Graph y una alternativa compatible.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
java
Área
api
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.