On 2012-12-01, Patrick Shanahan <ptilopt...@gmail.com> wrote: > * Grant Edwards <grant.b.edwa...@gmail.com> [12-01-12 10:27]: >> On 2012-12-01, Patrick Shanahan <ptilopt...@gmail.com> wrote:
>>> Yahoo now requires posting from a yahoo account via their smtp or >>> from their web service, >> >> Weird. I posted to a Yahoo list two weeks ago by sending an e-mail >> via GMail's SMTP server. At the time I didn't even have a Yahoo >> account. I have since created a Yahoo account so I could access the >> download files area for one of the lists, but I still don't use it to >> access the list. >> >>> since last year some time. I have dropped all but one group, but >>> only read. I refuse to use their web service. >> >> It must vary by list. > > I am not explaining properly/sufficiently. Yahoo *requires* your posting > addr matches your smtp. Ah, that's indeed quite different than what you wrote previously. Requring that the From: address match up with the sending SMTP server is not an unusual anti-spam measure. > Mine does not and I will not open *more* spam floodgates. All you need to do is to send the message via the GMail smtp server. How does that "open more spam floodgates"? I have mutt configured to send mail via GMail's SMTP server when I'm using my GMail address, and I don't think it's created any additional spam. > I post via my isp using a gmail addr and my isp smtp. It does not > match yahoo's req's as the posting addr and smtp do not match. In the past, I've found that causes problems with other destinations as well. I suspect it's comparing the From: address, the envelope from, the SMTP sender, and the Return-Path: values. If they don't match up in certain ways, it's being tossed as likely spam/phishing. I know my employer's MS Outlook server does that, though I don't remember exactly which combinations have to match... -- Grant
