Re: [Mailman-Users] dkim for several mailman lists on one server

On 4/24/20 2:36 PM, csa--- via Mailman-Users wrote: > Ubuntu 16, Mailman 2.1.20, postfix 3.1.0 > > I'm running several mailing lists each with a virtual domain. I set up DKIM > for lists.domainname.tld but am getting DKIM signature missing at > https://dkimvalidator.com . It's saying it wants a

[Mailman-Users] dkim for several mailman lists on one server

Ubuntu 16, Mailman 2.1.20, postfix 3.1.0 I'm running several mailing lists each with a virtual domain. I set up DKIM for lists.domainname.tld but am getting DKIM signature missing at https://dkimvalidator.com . It's saying it wants a DKIM for hostname.domainname.tld. When I look at the mail log I

Re: [Mailman-Users] DKIM

On 12/12/18 2:32 PM, Christoffer Hansen wrote: > "Reply-To:" field can be set with the original senders email address.[0] > (This is configurable by list admins as configuration option out of > several possible) > > Cheers > > Christoffer > > [0]:

Re: [Mailman-Users] DKIM

On 12/12/18 11:35 AM, Bernie Cosell wrote: > I have two questions about the DKIM/spf munging that mailman does. > > First: when it replaces the 'from' with a munged address [replacing the name > with "name via thislist" does it stick the original email address somewhere > in the > message, so

Re: [Mailman-Users] DKIM

Bernie, On 12/12/2018 20:35, Bernie Cosell wrote: > First: when it replaces the 'from' with a munged address [replacing the name > with "name via thislist" does it stick the original email address somewhere > in the > message, (...) "Reply-To:" field can be set with the original senders email

[Mailman-Users] DKIM

I have two questions about the DKIM/spf munging that mailman does. First: when it replaces the 'from' with a munged address [replacing the name with "name via thislist" does it stick the original email address somewhere in the message, so if a listmember wanted to reply to the original sender

Re: [Mailman-Users] DKIM signing issue - relaying mailman e-mails from third party sources

On 10/12/2017 02:15 PM, Grant Taylor via Mailman-Users wrote: > On 10/11/2017 12:12 PM, Mark Sapiro wrote: >> solution 2). Your mail relaying process can rewrite the envelope >> sender to your domain, e.g., campa...@myserver.com or some other >> appropriate @myserver.com address. This will break

Re: [Mailman-Users] DKIM signing issue - relaying mailman e-mails from third party sources

On 10/11/2017 12:12 PM, Mark Sapiro wrote: solution 2). Your mail relaying process can rewrite the envelope sender to your domain, e.g., campa...@myserver.com or some other appropriate @myserver.com address. This will break mailman's automated bounce processing for mail from

Re: [Mailman-Users] DKIM signing issue - relaying mailman e-mails from third party sources

On 10/11/2017 01:23 AM, Dlugasny via Mailman-Users wrote: > > The problem is that we are sending an E-mail which looks as follow: > > From: campa...@myserver.com > Return-Path: mailman-boun...@external-company.com > To: @gmail.com > > The problem is that DKIM check on the gmail server server

[Mailman-Users] DKIM signing issue - relaying mailman e-mails from third party sources

Hallo Mark, Kolleagues, maybe somebody will be able to help me here. I would like to relay (also check with Antivir and sign them with DKIM) all Mailman e-mails from our external partners to our final customers. Relaying seems to work nice but we have a problem with DKIM authentication and

Re: [Mailman-Users] DKIM / DMARC woes...

On 10/03/2017 10:24 AM, Mark Sapiro wrote: It is not a list setting. It applies to the entire installation. It is documented in Mailman/Defaults.py and if you want to change the default, set it in Mailman/mm_cfg.py. Thank you Mark. Sorry if I'm asking obvious questions. I've not admined

Re: [Mailman-Users] DKIM / DMARC woes...

On 10/02/2017 11:24 PM, Grant Taylor via Mailman-Users wrote: > > Is the REMOVE_DKIM_HEADERS option a per mailing list setting?  Or is it > Mailman wide? > > I'm looking through the list admin interface for Mailman 2.1.20 and not > finding it. It is not a list setting. It applies to the entire

Re: [Mailman-Users] DKIM / DMARC woes...

On 09/21/2017 03:23 PM, Mark Sapiro wrote: The default behavior does nothing to DKIM related headers. This is from Defaults.py Is the REMOVE_DKIM_HEADERS option a per mailing list setting? Or is it Mailman wide? I'm looking through the list admin interface for Mailman 2.1.20 and not

Re: [Mailman-Users] DKIM / DMARC woes...

On 09/21/2017 02:43 PM, Grant Taylor via Mailman-Users wrote: > > Would I be correct in assuming that REMOVE_DKIM_HEADERS needs to be set > to 2 or 3 to remove the DKIM headers if no from header munging is > happening?  (from_is_list or dmarc_moderation_action both at their > default value.)

Re: [Mailman-Users] DKIM / DMARC woes...

Thank you for the reply Mark. On 09/21/2017 03:23 PM, Mark Sapiro wrote: The default behavior does nothing to DKIM related headers. This is from Defaults.py Would I be correct in assuming that REMOVE_DKIM_HEADERS needs to be set to 2 or 3 to remove the DKIM headers if no from header munging

Re: [Mailman-Users] DKIM / DMARC woes...

On 09/21/2017 12:37 PM, Grant Taylor via Mailman-Users wrote: > > Does setting from_is_list and / or dmarc_moderation_action to munge > cause Mailman to do anything with existing DKIM-Signature headers?  Will > they be removed or left there? The default behavior does nothing to DKIM related

[Mailman-Users] DKIM / DMARC woes...

Hello, Does setting from_is_list and / or dmarc_moderation_action to munge cause Mailman to do anything with existing DKIM-Signature headers? Will they be removed or left there? -- Grant. . . . unix || die -- Mailman-Users mailing list

Re: [Mailman-Users] DKIM, SPF, DMARC, Mail_as_list all working, but MUAs not happy

Mark: Thanks much. I think I will give Munge From and see what happens. Computers are supposed to be deterministic. This stuff, well, not so much. Thanks again, Arlen Raasch On Tue, Apr 5, 2016 at 4:00 PM, Mark Sapiro wrote: > On 04/05/2016 12:14 PM, Arlen Raasch wrote:

Re: [Mailman-Users] DKIM, SPF, DMARC, Mail_as_list all working, but MUAs not happy

On 04/05/2016 12:14 PM, Arlen Raasch wrote: > > A large number of our users are not happy with how mail is presented when > Mail_as_list is active. They messages appear as attachments in some MUAs. > > If I change from Mail_as_list to Mung From, DKIM does not validate. I'm guessing you are

[Mailman-Users] DKIM, SPF, DMARC, Mail_as_list all working, but MUAs not happy

All: I am using a very old version of mailman, 2.1.16. I wanted to update to a newer version during this migration, but I was too concerned that I would break something in this complex server by upgrading and changing the dependencies that new versions of mailman require. A large number of our

Re: [Mailman-Users] DKIM Failures cause posts from gmail users to not be relayed to the list

On 08/12/2015 06:21 AM, Peter Bossley wrote: The MTA was configured to reject DKIM failures. This is wrong and is the cause of your issue. See RFC 6376 http://www.rfc-editor.org/rfc/rfc6376.txt sec 4.4, sec 6.1 and sec 6.3. The issue is your mail list transformations break gmail's DKIM

Re: [Mailman-Users] DKIM Failures cause posts from gmail users to not be relayed to the list

On Wed, 12 Aug 2015 10:04:14 -0400 Barry Warsaw ba...@list.org wrote: Hello Barry, FWIW, lists.debian.org does not run Mailman. Fair enough. Seems to me to be less likely that Peter's problem is the same, as other list owners of mailman run lists would probably be reporting similar errors. --

Re: [Mailman-Users] DKIM Failures cause posts from gmail users to not be relayed to the list

On 08/12/2015 06:44 AM, Brad Rogers wrote: *All* lists run from list.debian.org are to have their footers turned off because of valid DKIM signature breakage. In order to avoid DKIM signature breakage, you also have to turn off subject prefixing, content filtering, reply-to header munging

Re: [Mailman-Users] DKIM Failures cause posts from gmail users to not be relayed to the list

On Wed, 12 Aug 2015 13:21:58 + Peter Bossley p...@bossley.me wrote: Hello Peter, mailing lists need to work properly as well. Does anyone have any suggestions or ideas on why the Munge setting didn't seem to have an impact? I'm far from being an expert regarding DKIM, DKMS and mailman, but

[Mailman-Users] DKIM Failures cause posts from gmail users to not be relayed to the list

This is going to be a lengthy explanation, as I've spent a bit of time troubleshooting this issue. I am running Mailman 2.1.20 as part of a server running WHM/cpanel. The MTA is Exim. The MTA was configured to reject DKIM failures. The domain was configured to sign outgoing messages with DKIM. We

Re: [Mailman-Users] DKIM best practise

On 22/06/2015 1:58 PM, Stephen J. Turnbull wrote: As Mark already said, according to the standards it is correct and good practice to add a DKIM signature to every message you process outside of the MTA and then reinject into the Internet mail system. In more friendly terms, if you simply

Re: [Mailman-Users] DKIM best practise

On 06/21/2015 08:58 PM, Stephen J. Turnbull wrote: Yasir Assam writes: I noticed that this list, mailman-users@python.org, doesn't add a DKIM header unless the list itself generates the email, i.e. the email you sent to this list only has your DKIM header (d=msapiro.net), whereas

[Mailman-Users] DKIM best practise

I have a list which all subscribers can post to. I'm using mailman 2.1.18 on Debian Jessie with exim4. I have full personlisation and verp turned on. What should I do about DKIM? At the moment I preserve the original poster's DKIM header and my list's MTA also adds DKIM to all outgoing mail.

Re: [Mailman-Users] DKIM best practise

On 06/20/2015 06:39 PM, Yasir Assam wrote: I'm using mailman 2.1.18 on Debian Jessie with exim4. I have full personlisation and verp turned on. What should I do about DKIM? At the moment I preserve the original poster's DKIM header and my list's MTA also adds DKIM to all outgoing mail.

Re: [Mailman-Users] DKIM best practise

Thanks Mark. What you describe below makes sense, and I agree hotmail is behaving badly, but I'm stuck with its bad behaviour. In any case, if From Munging is not good to do generally then I have to figure out another way placate Yahoo's spam filter. Yasir On 22/06/2015 12:33 PM, Mark Sapiro

Re: [Mailman-Users] DKIM best practise

Many thanks for your response Mark. Comments below. On 22/06/2015 1:46 AM, Mark Sapiro wrote: On 06/20/2015 06:39 PM, Yasir Assam wrote: I'm using mailman 2.1.18 on Debian Jessie with exim4. I have full personlisation and verp turned on. What should I do about DKIM? At the moment I

Re: [Mailman-Users] DKIM best practise

Yasir Assam writes: I noticed that this list, mailman-users@python.org, doesn't add a DKIM header unless the list itself generates the email, i.e. the email you sent to this list only has your DKIM header (d=msapiro.net), whereas the original welcome email has DKIM with d=python.org.

Re: [Mailman-Users] DKIM best practise

On 06/20/2015 06:39 PM, Yasir Assam wrote: Is there any way I can get hotmail to reply to the list when the From: header is munged? Is munging considered bad form (when not mitigating DMARC reject policies)? It may not have been clear from my earlier reply, but yes, From Munging is considered

[Mailman-Users] dkim and email list software - potential solution

I proposed some ideas around DKIM compatibility with mail lists and tried to send to the dev list too. Obviously the anti-cross-post feature on mailman- develop...@python.org is working well (which on some levels I appreciate). As leading maillist product I'm keep to know your opinion. This has

Re: [Mailman-Users] [dkim-milter-discuss] dkim + mailman + postfix - dkim=fail. RESOLVED

awesome!!! It worked. Thanks so much Jason and everyone. It was exactly same issue that you identified. Appreciate great help from Jason, Mouss and team. Following changes were done in mailman configuration to make it work. -- REMOVE_DKIM_HEADER = YES in defaults.py SMTPPORT=587

Re: [Mailman-Users] DKIM/DK-milter with Mailman

SM wrote: The workaround is to configure Mailman as follows: Change the Mailman/Handlers/CleanseDKIM.py lines from: def process(mlist, msg, msgdata): del msg['domainkey-signature'] del msg['dkim-signature'] to def process(mlist, msg, msgdata): del

[Mailman-Users] DKIM/DK-milter with Mailman

Hi, I tested Mailman 2.1.8 with dkim-milter 0.4.1 and dk-milter 0.3.4. The server running Mailman signs all outgoing mail and inserts DKIM-Signature and DomainKey-Signature headers. Incoming mail verifies successfully. Mail sent by Mailman fails DomainKeys/DKIM verification at the