[swinog] Re: Swiss Domain Security Report Q3 2022

2023-06-08 Diskussionsfäden Sebastian Philipp via swinog
On 08 Jun 2023 Jonas Meier via swinog wrote: > maybe there is an option to remove the signature. If anyone has > experience with mailman3 and dkim, please write to me directly. You can set `remove_dkim_headers: yes` in mailman.cfg [1] (Sending this to the list, as this may be relevant for more pe

[swinog] Re: Swiss Domain Security Report Q3 2022

2023-06-08 Diskussionsfäden Jeroen Massar via swinog
Noting you do part of this already. But. note this nasty effect: --- From: Jonas Meier via swinog Reply-To: Jonas Meier --- Now add that to people having "automatically add recipient to addressbook" and when one wants to send an email to Jonas... it autocompletes to the public list

[swinog] Re: Swiss Domain Security Report Q3 2022

2023-06-08 Diskussionsfäden Jeroen Massar via swinog
> On 8 Jun 2023, at 11:47, Jonas Meier via swinog > wrote: > > Hi Franco, Dear List > > Thank you for your feedback. > > 1) I configured mailman3 [1] dmarc_mitigate_action to "munge_from" (to > replace the from header) and dmarc_mitigate_unconditionally to true. My > thought was that this

[swinog] Re: Swiss Domain Security Report Q3 2022

2023-06-08 Diskussionsfäden Jonas Meier via swinog
Hi Franco, Dear List Thank you for your feedback. 1) I configured mailman3 [1] dmarc_mitigate_action to "munge_from" (to replace the from header) and dmarc_mitigate_unconditionally to true. My thought was that this would mean that there can no longer be a dmarc policy which sets dkim to stric

[swinog] ### SwiNOG #38 - Agenda ###

2023-06-08 Diskussionsfäden Simon Ryf via swinog
Dear SwiNOG community, we could finally compile the agenda for the upcoming SwiNOG #38 – June Wednesday 21st Have a look at https://www.swinog.ch/meetings/swinog38/ There is still time to https://register.swinog.ch/ if you have not done it already. We have a super packed agenda. On the other h

[swinog] Re: Swiss Domain Security Report Q3 2022

2023-06-08 Diskussionsfäden Adrian Ulrich via swinog
Hi Daniel, > Your nameserver breaks https://www.rfc-editor.org/rfc/rfc8020 I'd rather say 'does not implement' instead of 'break': As RFC 8020 points out, the (almost 30 years older) RFC 1034 is very unspecific about the details on how a nameserver should behave in such a situation. (And opinion