I can confirm this
from my rejectlog:
2003-10-11 03:33:31 H=pcp02665442pcs.longhl01.md.comcast.net [68.49.23.108]
sender verify fail for <ebae@???>: response to "RCPT
TO:<ebae@???>" from mx1.mail.yahoo.com [64.156.215.6] was: 553 VS10-RT
Possible forgery or deactivated due to abuse (#5.1.1)
2003-10-11 03:33:31 H=pcp02665442pcs.longhl01.md.comcast.net [68.49.23.108]
F=<ebae@???> rejected RCPT <m.mackensen@???>: Sender verify failed
But now it seems that callouts are very ineffective (for yahoo.com).
Maybe I should deny all yahoo.com mails...it's 99.99% (maybe more) SPAM.
Or is there a better solution?
Mit freundlichen Grüßen
Matthias Lewandowski
Systemtechnik Internet
Telefon +49 (30) 59 00 69-00
Telefax +49 (30) 59 00 69-99
CBXNET combox internet service gmbh
Potsdamer Strasse 96 - D-10785 Berlin
Amtsgericht Berlin-Charlottenburg - HRB 71171
Geschäftsführer: Lutz Treutler
<
http://www.cbxnet.de> - <
mailto:support@cbxnet.de>
> -----Ursprüngliche Nachricht-----
> Von: Andreas Metzler [mailto:eximusers@downhill.at.eu.org]
> Gesendet: Donnerstag, 4. Dezember 2003 11:49
> An: exim-users@???
> Betreff: Re: [Exim] yahoo.com makes callout senderverify unusable!?
>
>
> On Thu, Dec 04, 2003 at 11:29:03AM +0100, Matthias Lewandowski wrote:
> > the last days I recognized a lot of frozen bounces
> > to yahoo.com addresses.
> [...]
> > So what are the yahoo-MTAs doing? Accept every null-sender
> mail, making
> > callouts impossible?
> [...]
>
> They usually simply reject after DATA instead of after RCPT TO, so
> callouts generally don't work. However if a yahoo account is misused
> for spamming and they start getting $bignumber of bounces, they reject
> _this_ account after RCPT TO, so yahoo-callouts are not totally
> useless.
> cu andreas
>
> --
>
> ## List details at
> http://www.exim.org/mailman/listinfo/exim-users Exim details
> at http://www.exim.org/ ##
>
