On Mon, Nov 25, 2024 at 11:11 AM Simplelists - Andy Beverley via mailop < mailop@mailop.org> wrote:
> Hi all, > > I spotted this on the Yahoo SMTP error codes webpage[1] today: > > For mailing lists, also known as “listservs,” you should change your > sending behavior by adding the mailing lists' address to the “From:” > line, rather than the sender's address. Also, enter the actual > user/sender address into the “Reply-To:” line. > > I'm wondering what other people's experiences of this are? > > We only rewrite the from address if required because of DMARC, but the > statement above implies that a special case needs to be made when > delivering to Yahoo. > > I've checked our mail logs, and I can see about 0.1% of emails to Yahoo > being bounced with an authentication error. > I have been using Mailman (2.x and now 3.x) for my mailing lists and it has no problem with this requirement. I don't even do any rewriting as MM3 does it. It also has a provision for what Yahoo says above - you can munge the Reply-To: header or just leave it untouched. This is what Mailman2 says in the relevant setting: ``` Where are replies to list messages directed? No Munging is strongly recommended for most mailing lists. This option controls what Mailman does to the Reply-To: header in messages flowing through this mailing list. When set to No Munging, no Reply-To: header is added by Mailman, although if one is present in the original message, it is not stripped. Setting this value to either Reply to List, Explicit Reply, or Reply Only causes Mailman to insert a specific Reply-To: header in all messages, overriding the header in the original message if necessary (Explicit Reply inserts the value of reply_to_address). Explicit Reply-to set; no Cc added is useful forannounce-only lists where you want to avoid someone replying to the list address. There are many reasons not to introduce or override the Reply-To: header. One is that some posters depend on their own Reply-To: settings to convey their valid return address. Another is that modifying Reply-To: makes it much more difficult to send private replies. See `Reply-To' Munging Considered Harmful <http://marc.merlins.org/netrants/reply-to-harmful.html> for a general discussion of this issue. See `Reply-To' Munging Considered Useful <http://marc.merlins.org/netrants/reply-to-useful.html> for a dissenting opinion. Some mailing lists have restricted posting privileges, with a parallel list devoted to discussions. Examples are `patches' or `checkin' lists, where software changes are posted by a revision control system, but discussion about the changes occurs on a developers mailing list. To support these types of mailing lists, select Explicit Reply and set the Reply-To: address option to point to the parallel list. ``` And just to add, I strongly discourage any subscribers from joining with a Yahoo address. Maybe you should migrate to Mailman3, and have peace of mind? :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
