Perfect, Thanks.

Is there a way to set this as a default for all new lists being created? Still working on the new styles, I imagine that can be set there during the selection of the list type.

-- Samir Faci

On Fri, May 15, 2020 at 9:44 AM Mark Sapiro <mark@msapiro.net> wrote:

On 5/15/20 9:31 AM, Samir Faci wrote:

...

Is there a way to force mailman to ensure that the list name shows up in the from field?

In Postorius Settings -> DMARC Mitigations set DMARC mitigation action to Replace From with list address and set DMARC Mitigate unconditionally to Yes.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

-- Thank you Samir Faci https://keybase.io/csgeek

Hi,

I had the same issue and Mark helped with the following hint: Go to list setting, "DMARK Mitigation" Set Replace From: with list address and DMARC mitigation unconditionally to yes.

It works for some mail agents, no so well with outlook. I am still chewing on this.

Thanks Mohsen

-----Original Message----- From: Samir Faci <samir@esamir.com> Sent: Friday, May 15, 2020 12:32 PM To: mailman-users@mailman3.org Subject: [MM3-users] Mailman Header Behavior

[EXTERNAL EMAIL]

I'm trying to use AWS SES as a mail relay for IP Health and other tidbits and it seems like it's very particular on what the headers look like.

The FROM field has to be from a verified email meaning the list name has to be in the from field.

I'm getting something along these lines for the rejection:

May 15 16:28:26 lists postfix/smtp[2938320]: 1EA6C13880A: to=< csgeek@esamir.com>, relay=email-smtp.us-west-2.amazonaws.com[52.88.99.145]:587, delay=0.76, delays=0.01/0.02/0.43/0.31, dsn=5.0.0, status=bounced (host email-smtp.us-west-2.amazonaws.com[52.88.99.145] said: 554 Message rejected: Email address is not verified. The following identities failed the check in region US-WEST-2: Samir Faci <samir@esamir.com> (in reply to end of DATA command))

If on the other hand I enable the Anonymous list option then everything works, but I obviously have no clue who sent the email or how to respond to the person (if they're not subscribed)

Is there a way to force mailman to ensure that the list name shows up in the from field?

-- Thank you Samir Faci https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkeybase.io...

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...

Is there a way to munge/rewrite the -owner and -bounces emails? = Otherwise, I had to go through the following to be able to use AWS SES:

A note for going through AWS SES=E2=80=A6 The messages to -owner and = -bounces just get forwarded through, not re-written/munged. Because = they can come from anyone, you cannot send them through AWS. I ended up = using header dependent relays in Postfix:

main.cf: header_checks =3D pcre:/etc/postfix/header_dependent_relay

And in /etc/postfix/header_dependent_relay file:

# # Bounce messages are supposed to go to us # /^From:.*-bounces\@lists\.example\.com/ DUNNO /^From:.*-owner\@lists\.example\.com/ DUNNO =20 # # Send certain domains out through Amazon # /^From:.*\@lists\.example\.com/ FILTER = smtpamazon:[your-smtp-relay.amazonaws.com]:587

And add this block to /etc/postfix/main.cf:

# # Send through Amazon SES # smtpamazon unix - - - - 10 smtp -o smtp_sasl_password_maps=3Dhash:/etc/postfix/sasl_passwd

That will let the emails from -bounces and -owner directly out, but = redirect any list traffic through SES.

Seth

On May 15, 2020, at 12:31 PM, Samir Faci <samir@esamir.com> wrote: =20 I'm trying to use AWS SES as a mail relay for IP Health and other = tidbits and it seems like it's very particular on what the headers look like. =20 The FROM field has to be from a verified email meaning the list name = has to be in the from field. =20 I'm getting something along these lines for the rejection: =20 May 15 16:28:26 lists postfix/smtp[2938320]: 1EA6C13880A: to=3D< csgeek@esamir.com>, = relay=3Demail-smtp.us-west-2.amazonaws.com[52.88.99.145]:587, delay=3D0.76, delays=3D0.01/0.02/0.43/0.31, dsn=3D5.0.0, = status=3Dbounced (host email-smtp.us-west-2.amazonaws.com[52.88.99.145] said: 554 Message rejected: Email address is not verified. The following identities = failed the check in region US-WEST-2: Samir Faci <samir@esamir.com> (in reply = to end of DATA command)) =20 If on the other hand I enable the Anonymous list option then = everything works, but I obviously have no clue who sent the email or how to = respond to the person (if they're not subscribed) =20 Is there a way to force mailman to ensure that the list name shows up = in the from field? =20 =20 --=20 Thank you Samir Faci https://keybase.io/csgeek

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

Seth,

I also had assumed that the list name had to be in the header, but in = fact it does not. I munged the =E2=80=98From=E2=80=99 to another list address on the same = server. This list address is an auto-response list that informs the original sender (now = recipient) that he/she likely did not mean to use that address and suggests sending to the = intended address instead.

Yours,

Allan Hansen hansen@rc.org

On May 15, 2020, at 14:29 , Seth Seeger <seth@tofutavern.com> wrote: =20 Is there a way to munge/rewrite the -owner and -bounces emails? =3D Otherwise, I had to go through the following to be able to use AWS = SES: =20 A note for going through AWS SES=3DE2=3D80=3DA6 The messages to = -owner and =3D -bounces just get forwarded through, not re-written/munged. Because =3D=

they can come from anyone, you cannot send them through AWS. I ended = up =3D using header dependent relays in Postfix: =20 main.cf: header_checks =3D3D pcre:/etc/postfix/header_dependent_relay =20 And in /etc/postfix/header_dependent_relay file: =20

...

# # Bounce messages are supposed to go to us # /^From:.*-bounces\@lists\.example\.com/ DUNNO /^From:.*-owner\@lists\.example\.com/ DUNNO =3D20 # # Send certain domains out through Amazon # /^From:.*\@lists\.example\.com/ FILTER =3D smtpamazon:[your-smtp-relay.amazonaws.com]:587 =20 And add this block to /etc/postfix/main.cf: =20 # # Send through Amazon SES # smtpamazon unix - - - - 10 smtp -o smtp_sasl_password_maps=3D3Dhash:/etc/postfix/sasl_passwd =20 =20 =20 That will let the emails from -bounces and -owner directly out, but =3D redirect any list traffic through SES. =20 Seth =20 =20 =20 =20 On May 15, 2020, at 12:31 PM, Samir Faci <samir@esamir.com> wrote: =3D20 I'm trying to use AWS SES as a mail relay for IP Health and other =3D tidbits and it seems like it's very particular on what the headers look like. =3D20 The FROM field has to be from a verified email meaning the list name = =3D has to be in the from field. =3D20 I'm getting something along these lines for the rejection: =3D20 May 15 16:28:26 lists postfix/smtp[2938320]: 1EA6C13880A: to=3D3D< csgeek@esamir.com>, =3D relay=3D3Demail-smtp.us-west-2.amazonaws.com[52.88.99.145]:587, delay=3D3D0.76, delays=3D3D0.01/0.02/0.43/0.31, dsn=3D3D5.0.0, =3D status=3D3Dbounced (host email-smtp.us-west-2.amazonaws.com[52.88.99.145] said: 554 Message rejected: Email address is not verified. The following identities =3D failed the check in region US-WEST-2: Samir Faci <samir@esamir.com> (in = reply =3D to end of DATA command)) =3D20 If on the other hand I enable the Anonymous list option then =3D everything works, but I obviously have no clue who sent the email or how to =3D respond to the person (if they're not subscribed) =3D20 Is there a way to force mailman to ensure that the list name shows up = =3D in the from field? =3D20 =3D20 --=3D20 Thank you Samir Faci https://keybase.io/csgeek

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ =20

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/