OK, the list *really* needs to be fixed
heather at livecode.com
Thu Jan 5 12:30:46 CET 2017
Folks, I have been monitoring the lists and its bounces for a few weeks. The problem does appear to be the notorious DMARC issue, which our list software does not deal well with. I have made a change to the way it handles DMARC mail which may or may not help with the problem. You can and I'm sure will let me know.
It is possible that the only real solution here is to stop using Mailman. This could be quite disruptive to all, but is something we will take under consideration. To be fair, this list has been running on this software for... 18 years? Its not surprising if it ultimately reaches end of life as the world moves on.
Regards, and a Happy New Year to you all!
Customer Services Manager
> On 4 Jan 2017, at 22:30, Mike Bonner <bonnmike at gmail.com> wrote:
> Just got kicked again. *sigh* Despite successfully receiving a boatload
> of messages from the list today.
> On Tue, Jan 3, 2017 at 11:03 AM, Bob Sneidar <bobsneidar at iotecdigital.com>
>> Fair enough, except that list servers are supposed to be configured in
>> such a way so as to get around this. A list server *should* send a separate
>> email to each user in a list, NOT one email to ALL the users in the list.
>> The latter will definitely get "DMARC'd" as spam, especially if the
>> addresses are not in the BCC field. Also, the list server *should* send the
>> emails in a throttled way, so as not to raise any flags.
>> It may be that gmail has tightened their DMARC rules, and so an adjustment
>> needs to be made in the list server to accomodate them. If this cannot be
>> done, it might be advisable to use a different domain. Mail issues like
>> this are definitely a nuisance, but in the modern age where email accounts
>> are getting compromised, providers are understandably a bit skittish.
>> Bob S
>>> On Jan 3, 2017, at 09:08 , J. Landman Gay <jacque at hyperactivesw.com>
>>> Found this explanation:
>>> It includes this:
>>> Let us say you have 5 users on your list, user1 at aol.com, user2 at
>> aol.com, user3 at aol.com user4 at aol.com and user5 at aol.com. user1 at
>> aol.com posts a piece of mail to your list. mailman tries to deliver to
>> user2, user3, user4 and user5 @ aol.com aol says "drop dead, we don't
>> talk to you because of our DMARC policy" mail to user2 user3 user4 and
>> user5 bounces. Their bounce count is incremented.
>>> user2 at aol.com posts a piece of mail to your list. mailman tries to
>> deliver to user1, user3, user4 and user5 @ aol.com aol says "drop dead,
>> we don't talk to you because of our DMARC policy" mail to user1 user3 user4
>> and user5 bounces. Their bounce count is incremented. and so on. Every time
>> somebody from aol sends mail to the list, it bounces for every other aol
>> member on your list. Their bounce counts increase.
>>> One day, some message sends some of the bounce counts over the limit
>> mailman has, after which it says -- Too many bounces! I cannot deliver mail
>> to this account! Unsubscribe this person! And, because of the way things
>> have happened you get a triggering message which causes a lot of
>> unsubscribes _from the same site_.
>>> Jacqueline Landman Gay | jacque at hyperactivesw.com
>>> HyperActive Software | http://www.hyperactivesw.com
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode