RE: [courier-users] Courier reports "451 Could not complete sender verify callout"

courier-users-admin@lists.sourceforge.net wrote:
> Ken Sarkies writes:
>
>> Aug 8 08:36:40 hta21 courieresmtp:
>>
> id=0012ED09.42F5FD34.00000A25,from=<ksarkies@trini ty.asn.au>,a
> ddr=<xxxxxx@salagaras.info>:
>> 451 Could not complete sender verify callout
>>
>> followed by deferred. There are no other related entries here or in
>> syslog. The recipient can mail us and knows of no other mailer that
>> has problems with his address. The recipient's domain is directed to
>> a machine mailhost.planetdomain.com managed by a large ISP (iPrimus),
>> who incidentally use other mailhosts for their subscribed user base.
>> I thought initially that the remote machine could not callout the
>> sender here. However if we mail the same person through MSX it goes
>> without a hitch. My dim understanding of sender verify callout is
>> that the remote machine tries to start up a dummy mail delivery to
>> the sender and aborts after authentication occurs. As port 25 is
>> forwarded to the Courier server, we should see the same problem
>> regardless of which mailer we use.
>>
>> Is this maillog entry saying that Courier cannot get an
>> authentication for the user on the remote machine?
>
> No, it means that when Courier sends the recipient's address
> to the remote machine, the remote machine replies responds
> with "451 Could not complete sender verify callout".
>
> That's all that this log entry means. Not a thing more. Not a thing
> less.
>
> Why the remote machine sends this response is something that
> only the remote machine's administrator can figure out.

Actually not in this case. I think this is a standard error message from
Exim, if the remote machine is configured to verify senders (e.g. callout or
dialout). If you are seeing this message in Courier's logs, it means that
Courier is trying to send an email with a sender that cannot be confirmed.
Why it cannot be confirmed can be for various reasons, but take a look a
close look at your logs and configuration.

>> What sort of tests can I use to track down the problem further? Is
>> there for example a way to change Courier's level of logging to see
>> the dialogue between the machines?
>
> The above log entry tells you exactly how the dialogue went.




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users