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

On Sun, Oct 22, 2023 at 6:46 AM Norbert Harrer <[email protected]> wrote:

> On 21.10.2023 21:55, Sam Varshavchik wrote:
>
> Norbert Harrer writes:
>
> 1. There was no sign of the maildrop error in
>
> I never thought much about it, because it was so cryptic. Turns out I had
> left this in .courier on an earlier debugging attempt:
>
> |/usr/bin/maildrop -w 90 -V 5 -d <address>
>
> The argument -V 5 logs very much and "authlib: groupid=114" is only the
> very first line.
>
> Once I use -V 1 or omit -V, the complete output of maildrop shows up in
> syslog. I guess the long maildrop output got truncated somewhere?
>

Yes, there are various limits. syslog itself cuts off long lines, and
Courier will  only capture output from a delivery process up to a certain
point, to prevent a rogue process from pummeling the log files with junk.

>
> "courier show all" showed that the address was blacklisted.
>
> I couldn't clear it with either "courier clear all" or "courier clear
> <mailaddress>." "courier show all" still displayed the same address.
> However, I don't remember if I had tried to run "courier flush" after
> "courier clear" once more.
>

Which version of Courier are you running? There was a bug related to this
which was fixed in 1.0, which was released in 2018.

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