1. Forum
  2. Usenet
  3. COMP.MAIL.SENDMAIL

  • Re: Gmail overwriting Message-Id header

    From Joshua Grippo@21:1/5 to nayib....@gmail.com on Fri Aug 26 14:33:25 2022
    On Friday, August 24, 2018 at 10:02:01 PM UTC-5, nayib....@gmail.com wrote:
    On Wednesday, November 29, 2017 at 10:39:42 PM UTC-5, Grant Taylor wrote:
    On 11/28/2017 06:07 PM, direct....@gmail.com wrote:
    Yes, gmail seems to only overwrite the Message ID if you submit it in
    a wrong format. In our case, we have a space in our message-id for which google pushed it to X-Google-Original-Message-ID. If we remove the space,
    then it is properly setting Message-ID. Same error occured with @ symbol as well.

    I'm not surprised that the space caused problems.

    Check out § 3.6.4 of RFC 5322, which defines what a Message-ID is supposed to be. Note that the dot-atom-text (atext defined in § 3.2.3) does not include a space.

    The @ symbol should exist exactly once in the Message-ID.

    From above experiment, we believe google reserved certain characters
    and hence if they encoutered in Message-ID, it converts it into X-Google-Original-Message-ID. If there is a consolidated list they specifiy somewhere, please let us know.

    I would be more apt to suspect that Google is rejecting anything that
    does not conform to the well defined Message-ID format (§ 3.6.4 of RFC 5322).



    --
    Grant. . . .
    unix || die
    Hello Guys,

    We are using the Gmail API to send emails on behalf of the users of our App. On the header of the emails we send via the Gmail API, we are setting a custom Message-ID.

    Nevertheless Gmail is overwriting the Message-ID we set with a different one . The following are some Message-IDs that we have tried:

    <8368110f-6ffc-46f8-8e67-7ebf0e1a1d83@domain>

    <4fb7a8b7013099c524f70906e009b46218461fff0b2dc0f8b794eb2df26e93d7@domain>

    Any idea why this ID overwriting is happening ?

    I would really appreciate any help

    Thanks in advance

    Did anyone find a solution? I am using <GUID@Domain>
    EX:
    <be573f3d-d48c-47a5-94f2-cbc4e3f81262@emaildev.backdocket.com>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ganesh Bhattathiri@21:1/5 to Joshua Grippo on Mon Nov 20 20:28:21 2023
    On Saturday, 27 August, 2022 at 3:03:27 am UTC+5:30, Joshua Grippo wrote:
    On Friday, August 24, 2018 at 10:02:01 PM UTC-5, nayib....@gmail.com wrote:
    On Wednesday, November 29, 2017 at 10:39:42 PM UTC-5, Grant Taylor wrote:
    On 11/28/2017 06:07 PM, direct....@gmail.com wrote:
    Yes, gmail seems to only overwrite the Message ID if you submit it in a wrong format. In our case, we have a space in our message-id for which
    google pushed it to X-Google-Original-Message-ID. If we remove the space,
    then it is properly setting Message-ID. Same error occured with @ symbol
    as well.

    I'm not surprised that the space caused problems.

    Check out § 3.6.4 of RFC 5322, which defines what a Message-ID is supposed to be. Note that the dot-atom-text (atext defined in § 3.2.3) does not include a space.

    The @ symbol should exist exactly once in the Message-ID.

    From above experiment, we believe google reserved certain characters and hence if they encoutered in Message-ID, it converts it into X-Google-Original-Message-ID. If there is a consolidated list they specifiy somewhere, please let us know.

    I would be more apt to suspect that Google is rejecting anything that does not conform to the well defined Message-ID format (§ 3.6.4 of RFC 5322).



    --
    Grant. . . .
    unix || die
    Hello Guys,

    We are using the Gmail API to send emails on behalf of the users of our App. On the header of the emails we send via the Gmail API, we are setting a custom Message-ID.

    Nevertheless Gmail is overwriting the Message-ID we set with a different one . The following are some Message-IDs that we have tried:

    <8368110f-6ffc-46f8-8e67-7ebf0e1a1d83@domain>

    <4fb7a8b7013099c524f70906e009b46218461fff0b2dc0f8b794eb2df26e93d7@domain>

    Any idea why this ID overwriting is happening ?

    I would really appreciate any help

    Thanks in advance
    Did anyone find a solution? I am using <GUID@Domain>
    EX:
    <be573f3d-d48c-47a5...@emaildev.backdocket.com>
    I am facing same issue . Just wanted to know if there is any solution found by anybody. from the looks of it, no, but still trying my luck

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Tue Nov 21 09:14:25 2023
    Am 20.11.2023 um 20:28:21 Uhr schrieb Ganesh Bhattathiri:

    I am facing same issue . Just wanted to know if there is any solution
    found by anybody. from the looks of it, no, but still trying my luck

    Does GMail really change the Message-ID when the mail is sent via SMTP?
    If not, why don't you use SMTP?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)