Community
Participate
Working Groups
It appears most users were removed from the trace compass mailing list. Is this deliberate?
Based on an email in the webmaster inbox it appears that Bernds last message to the list triggered a flurry of: <user@gmail.com>: host gmail-smtp-in.l.google.com said: 550-5.7.26 Unauthenticated email from ericsson.com is not accepted due to 550-5.7.26 domain's DMARC policy. Please contact the administrator of 550-5.7.26 ericsson.com domain if this was a legitimate mail. Please visit 550-5.7.26 https://support.google.com/mail/answer/2451690 to learn about the 550 5.7.26 DMARC initiative. w9si1326785qka.21 - gsmtp (in reply to end of DATA command) Those in turn triggered mailmans bounce action processor for those users, and they were automatically set as 'nomail' since mailman is trying to prevent us from either spamming or abusing other mail services. I can re-enable these users, but I suspect the same thing will happen again so that's not a long term solution. Most of our options for dealing with this require changing the list behaviour from what most of us expect. I'll discuss our options with the rest of the webmaster team. -M.
Ok, is there a "Blessed" solution that most other mls use?
Is this bug related? https://bugs.eclipse.org/bugs/show_bug.cgi?id=522316 I saw the word DMARC in the error message.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=541216 <- looks like there's another bug
(In reply to Matthew Khouzam from comment #2) > Ok, is there a "Blessed" solution that most other mls use? I haven't seen any specific guidance on what the 'right' solution is. So here's what I'm going to do: I'll set the tracecompass-dev list to replace the 'from' address with the list address and reactivate the affected users. If this keeps things moving then we'll configure all lists this way(after notifying the community) . I'll then work on getting bug 541216 sorted. The one risk is that right now, this change will break DKIM signing so we may end up no further ahead without resolving 541216 . -M.
As a side-effect of what happened, now the sender is replace with "tracececompass developer discussion", so we loose the name of the sender, as can be seen in https://www.eclipse.org/lists/tracecompass-dev/msg01443.html
(In reply to Genevieve Bastien from comment #6) This is what I was referring to in comment #1 about the list behaviour not being what we have traditionally expected. There aren't really a lot of options here. It's unreasonable to expect anyone that interacts with our mailing lists to add our mail service to their DMARC policies so that other users that rely on DMARC for filtering/spoofing protection can receive these messages. -M.
Even if the 'from' address is changed, is it possible to keep the name of the original sending user, so it's easier to follow a conversation and see who sent/replied? Also, Bernd has sent many emails on this list before. I don't know why yesterday's message had this effect now. @Matthew, do you have any additional information on this topic? Thanks
Any followup on this? Our mailing list is not very active, but discussions are hard to follow when we have no information about authors of messages. Many people on the ML don't sign their email, so we don't even have a name for the sender! Is there any solution to the DMARC policy? Other mailing lists served by Mailman don't have this issue, either they do not support DMARC,DKIM or there's a potential fix.
(In reply to Genevieve Bastien from comment #9) Sorry, the webmaster team has been pretty busy recently, so this has kind of fallen down the priority list. > Is there any solution to the DMARC policy? Not that webmaster has any direct control over, as these policies are controlled by the IT teams behind the mail servers that receive mail we send. >Other mailing lists served by > Mailman don't have this issue, either they do not support DMARC,DKIM or > there's a potential fix. Lists at Eclipse.org or elsewhere? -M.
> > >Other mailing lists served by > > Mailman don't have this issue, either they do not support DMARC,DKIM or > > there's a potential fix. > > Lists at Eclipse.org or elsewhere? > > -M. Lists elsewhere. I'm not on too many Eclipse.org lists but those I'm on don't have this issue either (tools-pmc, ease-dev for instance). But maybe no one sends from a server with DMARC enabled.
The Trace Compass mailing is getting more attention right now. It's getting harder to follow not knowing who send emails to the mailing list. Any progress on this bug and dependent bug?
(In reply to Bernd Hufmann from comment #12) > Any progress on this bug and dependent bug? Unfortunately not as things keep pushing them down the queue. I'll see what I can do about pushing it back up. Part of that is so far this seems to be the only list that has experienced this issue. -M.
(In reply to Eclipse Webmaster from comment #5) > The one risk is that right now, this change will break DKIM signing so we > may end up no further ahead without resolving 541216 . BTW Email currently sent by EF employees to Eclipse mailing lists are already failing DKIM. While direct email from the same people to my inbox are not failing DKIM. e.g. https://www.eclipse.org/lists/eclipse.org-committers/msg01245.html has: SPF: PASS with IP 64.147.108.52 Learn more DKIM: 'FAIL' with domain eclipse-foundation.org Learn more
Hi, I was wondering if it's possible see if we can have the same config as the other projects, at the moment we have cannot see who sent the mail and we need to remember to sign every reply. Thanks!
(In reply to Matthew Khouzam from comment #15) Ok I've reverted the changes from comment 5, as that is the only change I'm aware of. -M.
Fixed, I think
