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

On 14.10.2023 11:53, Alessandro Vesely wrote:
>>> If you catch the control file in the queue (C*) you get a list of
>>> attempts.
>>
>> What and where is that?
>
> # msgq="$(courier-config| sed -rn
> '/^localstatedir=/s/^[^=]*=(.*)/\1/p')/msgq"
> # find $msgq -name C\*
>
> Interesting meanings are readily guessable, but control file format is
> documented toward the end of this file:
> http://www.courier-mta.org/queue.html

The problem happened again, and thanks to your tip to check the queue
status file, I found out it was caused by a troublesome maildrop
.mailfilter file. I fixed it, and everything's fine now.

But I've got two questions:

1. There was no sign of the maildrop error in the log files. How can I
make maildrop errors show up in /var/log/mail.log? When I run maildrop
manually from the command line with:

/usr/bin/maildrop -V 1 -d <mailaddress> < message

It shows the error on stderr. But when courier calls maildrop, I don't
see the error in the log file. My /etc/courier/courierd has:

DEFAULTDELIVERY="|/usr/bin/maildrop -w 90 -V 1 -d \$USER"

It's probably a misconfiguration in my Debian system, and this might not
be the best place to ask, but maybe someone here has an idea where I can
start.


2. How can I recover/reset the stuck mailbox in the 456 state. I tried:

* cancelmsg the message in the queue.
* courier flush
* courier clear all
* courier clear <mailaddress>
* restarted courier

None of these worked, and it took some time for the mailbox to start
accepting emails again on its own.

Thanks for all the help so far,
Norbert.



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