Re: Sporadically deferred mail, followed by 456 Address temporarily unavailable

Hi Alessandro.

On 13.10.2023 13:25, Alessandro Vesely wrote:
> On Thu 12/Oct/2023 23:07:43 +0200 Norbert Harrer wrote:
>> > Oct 12 17:19:19 stargate maildrop[3132753]: maildrop started: From:
> ......... <[email protected]>, To: s....... Alle
> <[email protected]>, Subject: Letzter Aufruf für's s....... Skifahren,
> Message-ID: 000000000214519A.0000000065280E76.002FCD48; Thu, 12 Oct
> 2023 17:19:18 +0200, Maildir: /var/courier/nh...../Maildir
>
>
> Wow, I never had such a log line.  How do you produce it?

Thanks for your reply.
Right. That line is logged by my /etc/maildroprc, where I had added:

SYSLOG="/usr/bin/logger -i -p mail.info -t maildrop "

REFORMAIL=/usr/bin/reformail
SENDMAIL=/usr/sbin/sendmail

# add custom header
xfilter "$REFORMAIL -A 'X-Equilaris-Account: Yes'"

# log some mail details
/Received: from .* id\s+(.*)/:h
LOG_MESSAGE_ID=$MATCH1

/From:\s+(.*)/:h
LOG_FROM=$MATCH1

/To:\s+(.*)/:h
LOG_TO=$MATCH1

/Subject:\s+(.*)/:h
LOG_SUBJECT=$MATCH1

`$SYSLOG maildrop started: From: $LOG_FROM, To: $LOG_TO, Subject:
$LOG_SUBJECT, Message-ID: $LOG_MESSAGE_ID, Maildir: $DEFAULT`


>> Oct 12 20:04:47 stargate courieresmtpd:
>> error,relay=::ffff:209.85.221.71,port=45134,from=<[email protected]>,to=<[email protected]>:
>> 456 Address temporarily unavailable.
>
> 456 is the backscatter suppression, triggered by a previous error
> which I didn't see.

Me neither. I couldn't find anything unusual further up the log file
from the first deferred message. Could it be that the deferred message
is not even the problem, but rather a symptom of an earlier issue?

> If you catch the control file in the queue (C*) you get a list of
> attempts.

What and where is that?


Thank you,
Norbert.


_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users