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

Duplicate precedence header tripping up Amazon SES #110

Closed
racke opened this issue Oct 30, 2017 · 5 comments
Closed

Duplicate precedence header tripping up Amazon SES #110

racke opened this issue Oct 30, 2017 · 5 comments
Milestone

Comments

@racke
Copy link
Contributor

racke commented Oct 30, 2017

Precedence: list
Precedence: bulk

This is causing Amazon SES to reject the message, thus it is a quite serious problem.

status=bounced (host email-smtp.eu-west-1.amazonaws.com[52.30.4.9] said: 554 Transaction failed: Duplicate header 'Precedence'. (in reply to end of DATA command))

@racke
Copy link
Contributor Author

racke commented Oct 30, 2017

@ikedas
Copy link
Member

ikedas commented Oct 31, 2017

Precedence: field has no standard definition. Duplicate fields with values list and bulk were intended (See also below).

I suppose a better solution is removing this (these) field, if we can confirm that the other measures to prevent mail loop are sufficiently effective.


  1. RFC 2076, 3.9. "Precedence:".
  2. [sympa-users] Handling out/of/office replies to list. Dec. 2007.
  3. The first commit.

@ikedas ikedas added bug and removed bug labels Oct 31, 2017
@racke
Copy link
Contributor Author

racke commented Oct 31, 2017

We actually need this field to prevent autoreplies hitting the list, but it should be configurable instead of hardcoded. That would solve my problem.

@ikedas
Copy link
Member

ikedas commented Jan 6, 2018

@racke, does PR #152 solve the problem?

@ikedas
Copy link
Member

ikedas commented Apr 7, 2018

As PR #152 was merged, this issue is closed.

@ikedas ikedas closed this as completed Apr 7, 2018
@ikedas ikedas added this to the 6.2.32 milestone Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants