Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad forwarding -- too many "References" headers #133

Open
scanner opened this issue Feb 1, 2024 · 2 comments
Open

Bad forwarding -- too many "References" headers #133

scanner opened this issue Feb 1, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@scanner
Copy link
Owner

scanner commented Feb 1, 2024

When forwarding we need to have only one References header.

as google said:

smtp;550 5.7.1 This message is not RFC 5322 compliant. There are multiple References headers. To reduce the amount of spam sent to Gmail, this message has been blocked. For more information, go to https://support.google.com/mail/?p=RfcMessageNonCompliant and review RFC 5322 specifications. f3-20020a256a03000000b00dc21f1382b1si6986606ybc.672 - gsmtp

in this message:

References: <qrUYRrEzS8Cv8jve07Uvwg@geopod-ismtpd-36>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
X-PM-MTA-Pool: transactional-2
References: <c8bd4235-7152-414b-a77d-2c97345c58d5@mtasv.net>

Check to see if we can use "Original-References"

@scanner scanner added the bug Something isn't working label Feb 1, 2024
@scanner scanner self-assigned this Feb 1, 2024
@scanner
Copy link
Owner Author

scanner commented Feb 1, 2024

Note: References is a list of message-id's that is appended to whenever a message is replied to.
Since we are forwarding we need to either add to this field, or remove it from the original since postmark is adding it.

@scanner
Copy link
Owner Author

scanner commented Feb 1, 2024

https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.4

Though listed as optional in the table in [section 3.6](https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6), every message
   SHOULD have a "Message-ID:" field.  Furthermore, reply messages
   SHOULD have "In-Reply-To:" and "References:" fields as appropriate
   and as described below.

   The "Message-ID:" field contains a single unique message identifier.
   The "References:" and "In-Reply-To:" fields each contain one or more
   unique message identifiers, optionally separated by CFWS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant