On 8 March 2018 at 14:37, Tony Nelson <tonynelson@xxxxxxxxxxxxxxxxx> wrote: > On 18-03-07 14:14:38, Nicolas Mailhot wrote: >> >> Le mercredi 07 mars 2018 à 12:18 -0500, Josh Boyer a écrit : >> > On Wed, Mar 7, 2018 at 12:11 PM, Nicolas Mailhot >> > <nicolas.mailhot@xxxxxxxxxxx> wrote: >> > > Le mercredi 07 mars 2018 à 11:31 -0500, Stephen John Smoogen a écrit >> > > : >> > > > >> > > > I don't know if this is useful but in the RHL and early Fedora >> > > > days, >> > > > the way to do inplace upgrades was to first update just the 'core' >> > > > tools needed by rpm. >> > >> > This is a totally unrelated comment, but I will personally send you $5 >> > if you can configure your email client to stop adding <DKIM> in the >> > Subject line for every thread you reply to. >> >> I'm pretty sure that's added by one of the MTAs in the chain between >> Fedora SMTP and my ISP MTA, to attest they did DKIM verification, since >> I see it already positioned on some received messages before I ever >> replied to them. > > > Presumably by bastion01.phx2.fedoraproject.org (Postfix), which adds the > lines: > No, I don't think so. I can't find anything in the configuration which would do this and I have a sneaking suspicion that if it was bastion then most emails would get their subject changed. After going through most of the email logs for the last 2 days, the only emails which consistently passed DKIM tests were SPAM from various shady sources. Most user email do not pass DKIM tests on any of the spamassassin logs we have. So I would expect a lot of people to see DKIM in their headers. The only one I could find is email from Nicholas. The problem looks to be what Nicholas said in a different email about mailman not stripping headers. The laposte servers are particular about how they interpret simple DKIM signatures versus wraparound and this is where his replies seem to fork a new thread. [There are multiple types of DKIM headers depending on whether email servers only limit to X characters per line or similar limitations]. In any case, the mailman3 server will now dkim from emails and will see if that fixes the issue. If it doesn't then we will go to see what else could be causing the issue. > DKIM-Filter: OpenDKIM Filter v2.11.0 bastion01.phx2.fedoraproject.org > 2E4116051DFD > Authentication-Results: bastion01.phx2.fedoraproject.org; dkim=fail > reason="signature verification failed" (2048-bit key) header.d=laposte.net > header.i=@laposte.net header.b="bKrmUuvt" > > -- > ____________________________________________________________________ > TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> > ' <http://www.georgeanelson.com/> > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
