> On Wed, 11 Nov 2009, Philip A. Prindeville wrote: >> Return-Path: <evan_law...@davidark.net> >> Received: from web1111.biz.mail.sk1.yahoo.com ....
On 11.11.09 17:15, Charles Gregory wrote: > The 'not from our server' response makes me think that Yahell needs > to update their e-mail response robot. > > A while ago Yahell started partnering with companies like Rogers telecom > here in Ontario, so that they were the e-mail 'provider' for any of > Rogers DSL customers, many of whom have addresses at domains *other* than > Yahell. I would suspect that they adjusted their mail interface to allow > custom envelope senders from these sources, but did not update theior > robot to handle the case where Return-Path is not a Yahoo address.... imho, if a user uses someone's mailservers to receive mail, (s)he should use their servers to send mail too. That is the only way to properly implement anti-forging techniques like SPF, DKIM etc. I also do not like people using our competitors' mailsevrers for receiving mail (and pay them for that) while sending spam through us... > Either that or the server name is 'new' and not handled by the robot. > Either way, I would find a way to MUNG the contents of the e-mail > sufficiently that Yahoo can no longer 'parse' the headers and 'auto > respond'. Then you might get a human to look at it.... MAYBE. :) -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. 2B|!2B, that's a question!
