Ok Site5 and U Washington seem to be unable / unwilling to fix so I tried mailmanlists.net from your link there, messages to yahoo and aol pass fine so as you say, probably time to change providers and, to boot, mailmanlists.net is cheaper
thanks > On Aug 1, 2019, at 10:18 PM, Stephen J. Turnbull > <turnbull.stephen...@u.tsukuba.ac.jp> wrote: > > Loren Engrav writes: > >> does anyone know of a Mailman host that successfully sends to yahoo >> and aol addresses? > > Many do. > > Your problem is very unlikely to have anything to do with Mailman. As > Mark points out, the status message says the connection is dropped > abruptly at RCPT TO, so at that point the Yahoo/AOL server knows the > following things: > > 1. Your Mailman host's IP address, > 2. The domain name that your host claims > 3. The "envelope return address", which is normally the address of > the author of the post (for your test messages, that's you) > 4. The addressees you're trying to deliver to. > > 4 is extremely unlikely to be the problem, as long as they're real > addresses at those hosts (providers don't keep users very long if they > refuse all mail to them!), and even if one is nonexistent, usually you > get a failure for that address, but the others go through. You could > try confirming that those addresses exist; if you have a pile of > non-existent addresses, the receiving server might decide you're a > spammer. However, most likely all (or 99%) of your addresses are > valid, and as Mark suggested the receiving server is willing to > deliver to certain administrative addresses such as "postmaster" and > "abuse", but discards all others. > > 3 is not very likely unless you personally have offended Yahoo! quite > severely so your tests don't go through, and of course any messages > from others wouldn't be affected by your personal reputation. > > It's theoretically possible that a mismatch between 1 and 2 is the > problem, although you say you've got your server correctly configured. > The theoretical problem is that if looking up the IP address doesn't > give the domain or vice versa, some hosts will refuse mail. But those > hosts normally do that immediately without waiting for your envelope > (the return address and the recipients). So this also is extremely > unlikely to be the problem. > > So it looks like 1 or 2, i.e., the identity of your host, is the > problem. That is, either that domain or the IP address it is using > has been abusive in the past (spamming, phishing, DoS attacks, etc), > and the reputation has not been rehabilitated. > > There's not much we can do to help, because it's a host configuration > problem or reputation problem. I hate to say this because list admins > hate to hear it, but you are dependent on your hosting provider. If > they can't help you, your only good option is to switch providers. > Here is a page with several pointers to providers of Mailman hosting: > > https://wiki.list.org/COM/Mailman%20hosting%20services > > Here's another with pointers to other pages with information about a > variety of providers and related services: > > https://wiki.list.org/DOC/Do%20you%20offer%20Mailman%20hosting%2C%20consulting%2C%20or%20contractor%20services%3F > ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org