Stefan Bauer:
> Our quick and dirty approach is to parse output of mailq, delete mail and
> construct a bounce message, but that is far away from a clean solution ;/
> No other way available?
Yes, see http://www.postfix.org/postconf.5.html#default_delivery_status_filter
The primary use case was a
Viktor Dukhovni:
>
>
> > On Sep 10, 2018, at 12:06 PM, Wietse Venema wrote:
> >
> > What about this?
> >
> > Example 1: convert specific soft TLS errors into hard errors, by over-
> > riding the first number in the enhanced status code.
> >
> > /etc/postfix/main.cf:
> >smtp
> On Sep 10, 2018, at 12:06 PM, Wietse Venema wrote:
>
> What about this?
>
> Example 1: convert specific soft TLS errors into hard errors, by over-
> riding the first number in the enhanced status code.
>
> /etc/postfix/main.cf:
> smtp_delivery_status_filter = pcre:/etc/
Viktor Dukhovni:
>
>
> > On Sep 10, 2018, at 7:50 AM, Stefan Bauer wrote:
> >
> > Our quick and dirty approach is to parse output of mailq, delete mail and
> > construct a bounce message, but that is far away from a clean solution ;/
> > No other way available?
>
> Not presently.
What about
> On Sep 10, 2018, at 7:50 AM, Stefan Bauer wrote:
>
> Our quick and dirty approach is to parse output of mailq, delete mail and
> construct a bounce message, but that is far away from a clean solution ;/
> No other way available?
Not presently.
--
Viktor.
Our quick and dirty approach is to parse output of mailq, delete mail and
construct a bounce message, but that is far away from a clean solution ;/
No other way available?
Am So., 9. Sep. 2018 um 19:27 Uhr schrieb Viktor Dukhovni <
postfix-us...@dukhovni.org>:
>
>
> > On Sep 9, 2018, at 1:01 PM,
our system is only outbound but here when TLS fails so remote sites, we
would be happy to have an option to instantly bounce as this is mostly a
fixed state.
Am So., 9. Sep. 2018 um 19:27 Uhr schrieb Viktor Dukhovni <
postfix-us...@dukhovni.org>:
>
>
> > On Sep 9, 2018, at 1:01 PM, Stefan Bauer
> On Sep 9, 2018, at 1:01 PM, Stefan Bauer wrote:
>
> any way to inform my users about TLS fails via bounce without waiting queue
> lifetime?
http://www.postfix.org/postconf.5.html#delay_warning_time
In corporate systems I tend to split the mail plant into separate inbound
and outbound syst
seems to only work when postfix is server. I need this for postfix as
client when remote site is not offering tls.
Am So., 9. Sep. 2018 um 18:59 Uhr schrieb Herbert J. Skuhra <
herb...@gojira.at>:
> On Sun, Sep 09, 2018 at 06:49:07PM +0200, Stefan Bauer wrote:
> > Hi,
> >
> > delays=422/0.03/0.09
any way to inform my users about TLS fails via bounce without waiting queue
lifetime?
Am So., 9. Sep. 2018 um 18:58 Uhr schrieb Viktor Dukhovni <
postfix-us...@dukhovni.org>:
>
>
> > On Sep 9, 2018, at 12:49 PM, Stefan Bauer
> wrote:
> >
> > delays=422/0.03/0.09/0, dsn=4.7.4, status=deferred (TL
On Sun, Sep 09, 2018 at 06:49:07PM +0200, Stefan Bauer wrote:
> Hi,
>
> delays=422/0.03/0.09/0, dsn=4.7.4, status=deferred (TLS is required, but
> was not offered by host
>
> seems to me like a permanent error - postfix sees it as a temporary one. I
> would like to have instant bounce message for
> On Sep 9, 2018, at 12:49 PM, Stefan Bauer wrote:
>
> delays=422/0.03/0.09/0, dsn=4.7.4, status=deferred (TLS is required, but was
> not offered by host
>
> seems to me like a permanent error - postfix sees it as a temporary one. I
> would like to have instant bounce message for this case
Hi,
delays=422/0.03/0.09/0, dsn=4.7.4, status=deferred (TLS is required, but
was not offered by host
seems to me like a permanent error - postfix sees it as a temporary one. I
would like to have instant bounce message for this case when TLS is not
available.
sending postfix is configured 'encryp
13 matches
Mail list logo
