24. Apr 2016 13:51 by krem...@kreme.com:
> I agree, in general, but it may be useful in some cases to notify someone
> about issues who does not otherwise have access to the mail server logs. A
> front line support person, for example.
That is what I mean by the comment
"Here the reade
On Sun Apr 24 2016 10:46:20 Viktor Dukhovni
said:
>
> My advice is:
>
># No email about email problems, such notices can compound problems.
># Instead monitor your logs for spikes in message latency and other
># problems.
>#
>notify_classes =
I agree, in general, but it
On Sun, Apr 24, 2016 at 12:01:00PM -0400, Wietse Venema wrote:
> If someone has the time, they can propose a patch (considering that
> this code was written in 1997, I don't see it as an urgent problem).
> While they are at it, they might also enforce that the transcript
> is sent to the recipient
24. Apr 2016 09:01 by wie...@porcupine.org:
> If someone has the time, they can propose a patch (considering that
> this code was written in 1997, I don't see it as an urgent problem).
> While they are at it, they might also enforce that the transcript
> is sent to the recipient that is configure
list...@tutanota.com:
> 24. Apr 2016 07:09 by wie...@porcupine.org:
>
> > You need to distinguish between the effect (the client dropped the
> > connection) and the cause (Postfix rejected mail because it did not
> > satisfy policy).
> >
>
> Okay I was a little confused because I thought 'reason' m
24. Apr 2016 07:09 by wie...@porcupine.org:
> You need to distinguish between the effect (the client dropped the
> connection) and the cause (Postfix rejected mail because it did not
> satisfy policy).
>
Okay I was a little confused because I thought 'reason' means 'cause'.
So I see in thi
list...@tutanota.com:
> I am experimenting with postfix notify_classes.
>
> To start the config is
>
> notify_classes = bounce, 2bounce, data, delay, policy, protocol,
> resource, software
>
> Now in my postmaster inbox I received a message,
>
> Subject: Postfix SMTP server: errors fro
