On May 4, 2004, at 13:03, Edgar Lovecraft wrote:
> Tor Slettnes wrote:
>> Also, it has nothing to do with your smarthost router. Sender
>> verification works by calling the MX of the sender's domain directly,
>> no
>> other routing involved. In fact, you have a very good reason to keep
>> using a smarthost (see below).
>
> Yes it does (or could) have everything to do with the smarthost.
You are right, I was wrong. I use 'smtp.comcast.net' in a smarthost
router, and when running "exim4 -bhc <ipaddress>" to verify "MAIL FROM:
<anotherbob@???>", I get:
[....]
>>> Connecting to smtp.comcast.net [216.148.227.125]:25 ... connected
>>> SMTP<< 220 comast.net - Maillennium ESMTP/MULTIBOX rwcrmhc11
#136
>>> SMTP>> HELO dot.slett.net
>>> SMTP<< 250 comcast.net
>>> SMTP>> MAIL FROM:<>
>>> SMTP<< 250 ok
>>> SMTP>> RCPT TO:<anotherbob@???>
>>> SMTP<< 250 ok; [simple] forward to <anotherbob@???>
>>> SMTP>> QUIT
...
I.e. the result of the sender callout verification will (nearly) always
be positive, which is not very useful at all.
Can I write something in the "smarthost" router to skip it when doing
callout verification? Something like "condition = ${if !callout
{true}{false}}"..
(I realize that the callout may not neccessarily be valid in this case
either, since hosts may reject my "dynamic" IP address after "RCPT
TO:", but I'd like to give this a try...)
-tor
