Bounces from mailing list

Steve and other mail-list admins,

I’m sure you are aware of the problem given the amount of g-mail users. I have been experiencing a few ‘Your lammps-users membership has been disabled due to excessive bounces.’ Upon looking into this, I suspect that it is likely due to the recently changed yahoo DMARC reject policy, where yahoo e-mails not originating on Yahoo!'s servers are bounced by all DMARC-enabled providers (http://www.pcworld.com/article/2141120/yahoo-email-antispoofing-policy-breaks-mailing-lists.html).

Are there any plans to work around this, or can I expect to keep receiving these e-mails and needing to re-enlist every 2 days?

Steve and other mail-list admins,

i am not an admin, but...

I'm sure you are aware of the problem given the amount of g-mail users. I
have been experiencing a few 'Your lammps-users membership has been disabled
due to excessive bounces.' Upon looking into this, I suspect that it is

i've seen this a couple times in the past, but not recently.

likely due to the recently changed yahoo DMARC reject policy, where yahoo
e-mails not originating on Yahoo!'s servers are bounced by all DMARC-enabled
providers
(http://www.pcworld.com/article/2141120/yahoo-email-antispoofing-policy-breaks-mailing-lists.html).

no. unlikely.

Are there any plans to work around this, or can I expect to keep receiving
these e-mails and needing to re-enlist every 2 days?

how many times, was your membership suspended?

since sourceforge is hosting the mailing list, you should contact
their user support, as these things are not configured by the
projects.

axel.

I had the same thing twice already, thought it was a problem on my end

Thanks for the response Axel. I will contact them.

I’ve received a warning about every day or two since the beginning of last week.

Dear all,

Same here, my membership was disabled thrice last week. We got a mail
regarding a similar problem on the VMD mailing list, is it the same
phenomenon?

Best regards,
Laurent

2014-04-15 0:11 GMT+01:00 Eric Murphy <[email protected]>:

Just an update. I contacted Sorceforge’s support about the problem, and never heard anything back. However, I haven’t received any more account suspension warnings, which were originally occurring quite frequently. So as of now, I’m considering the problem resolved.

Axel and I think this is due to the recent Heartbleed open-ssh bug, and

mail servers becoming more agressive in their checks.

The important thing to realize is that if your account is disabled

(due to bounces), then you can re-enable it yourself.

Just go to this page:
https://lists.sourceforge.net/lists/options/lammps-users

enter the email address you have mail-list postings sent to,
and the pword you chose for your LAMMPS mail list subscription.

Then you get a page of options. The first one (Mail delivery) is to

enable/disable your account. Be sure to “Submit My Changes” at
the bottom of the page.

Of course, if you are currently disabled, you won’t get this email :frowning:

Steve

Hey Steve,

Isn’t this the Yahoo issue? See here:
http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html and
http://www.theregister.co.uk/2014/04/08/yahoo_breaks_every_mailing_list_in_the_world_says_email_guru/

The relevant passage:

The reason this matters is that over the weekend Yahoo published a
DMARC record with a policy saying to reject all [yahoo.com](http://yahoo.com) mail that
fails DMARC.  I noticed this because I got a blizzard of bounces from
my church mailing list, when a subscriber sent a message from her
[yahoo.com](http://yahoo.com) account, and the list got a whole bunch of rejections from
gmail, Yahoo, Hotmail, Comcast, and Yahoo itself.  This is definitely
a DMARC problem, the bounces say so.

The problem for mailing lists isn't limited to the Yahoo subscribers.
Since Yahoo mail provokes bounces from lots of other mail systems,
innocent subscribers at Gmail, Hotmail, etc. not only won't get Yahoo
subscribers' messages, but all those bounces are likely to bounce them
off the lists.  A few years back we had a similar problem due to an
overstrict implementation of DKIM ADSP, but in this case, DMARC is
doing what Yahoo is telling it to do.

The VMD list has some of workaround. I can fish for the email explaining it if you want.

-s-

Hey Steve,

Isn't this the Yahoo issue? See here:

yes. steve misunderstood.

i think this contributes to the issue, but is not the only thing.
places that host a lot of mailing lists, need to keep an eye on
reducing the load on their mail server due to bounces, and at the same
time fight spammers, that try to abuse those machines.
most spam usually uses some random valid(!) e-mail address as the
envelope address (the one nobody usually gets to see) to get past some
spam protection filter that will block senders with fake envelope
addresses. harvesting e-mail addresses from mailing lists is quite
common in this case.

http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html and
http://www.theregister.co.uk/2014/04/08/yahoo_breaks_every_mailing_list_in_the_world_says_email_guru/

The relevant passage:

The reason this matters is that over the weekend Yahoo published a
DMARC record with a policy saying to reject all yahoo.com mail that
fails DMARC. I noticed this because I got a blizzard of bounces from
my church mailing list, when a subscriber sent a message from her
yahoo.com account, and the list got a whole bunch of rejections from
gmail, Yahoo, Hotmail, Comcast, and Yahoo itself. This is definitely
a DMARC problem, the bounces say so.

The problem for mailing lists isn't limited to the Yahoo subscribers.
Since Yahoo mail provokes bounces from lots of other mail systems,
innocent subscribers at Gmail, Hotmail, etc. not only won't get Yahoo
subscribers' messages, but all those bounces are likely to bounce them
off the lists. A few years back we had a similar problem due to an
overstrict implementation of DKIM ADSP, but in this case, DMARC is
doing what Yahoo is telling it to do.

The VMD list has some of workaround. I can fish for the email explaining it
if you want.

well, this is ultimately an issue that sourceforge, the mailing list
host, has to address. VMD/NAMD is different because TCBG runs their
own mail list servers.

axel.