Hi Viktor,
On Thu, 9 May 2019, Viktor Dukhovni wrote:
On May 9, 2019, at 1:13 PM, Andreas Thienemann wrote:
I have the following items in my config:
http://www.postfix.org/DEBUG_README.html#mail
fair enough...
Problem description:
smtpd_recipient_restrictions seems to be working differe
On 9 May 2019, at 09:53, Viktor Dukhovni wrote:
> But in fact, my view is that bounces should always be headers-only,
> and if you're sending important content whose only copy is in the
> outbound message, which is "lost" if not delivered, then that's the
> problem, fix the sending software to arc
> On May 9, 2019, at 1:37 PM, Bastian Blank
> wrote:
>
> Don't split restrictions into multiple lists.
I disagree. Indeed as of Postfix 2.10 we have separate relay restrictions
by default. The OP's problem will be evident once the "postconf -n" output
is posted.
--
Viktor.
> On May 9, 2019, at 1:13 PM, Andreas Thienemann wrote:
>
> I have the following items in my config:
http://www.postfix.org/DEBUG_README.html#mail
--
Viktor.
Hi Andreas
On Thu, May 09, 2019 at 07:13:22PM +0200, Andreas Thienemann wrote:
> smtpd_recipient_restrictions = check_recipient_access
> proxy:mysql:/etc/postfix/bounce_spam_alias.cf
>check_recipient_access
> proxy:mysql:/etc/postfix/bounce_routes.cf
What I forgo
Matus UHLAR - fantomas:
Seems that I assumed too much, e.g. that since TLS isn't mandatory on SMTP
port, starttls and thus tlsproxy isn't important. Perhaps starttls could be
avoided by setting:
postscreen_discard_ehlo_keywords = starttls
On 09.05.19 13:34, Wietse Venema wrote:
That would b
On Thu, May 09, 2019 at 07:13:22PM +0200, Andreas Thienemann wrote:
> I was under the impression, that smtpd_recipient_restrictions and other
> restriction configuration items were being processed top to bottom.
Show logs. Show complete config.
See http://www.postfix.org/DEBUG_README.html#mail.
Matus UHLAR - fantomas:
> Seems that I assumed too much, e.g. that since TLS isn't mandatory on SMTP
> port, starttls and thus tlsproxy isn't important. Perhaps starttls could be
> avoided by setting:
>
> postscreen_discard_ehlo_keywords = starttls
That would be a BIG MISTAKE. Especially in Ger
Wietse Venema:
> Arjen Van Drie:
> >
> > It works exactly as Wietse pointed out. Set bounce_size_limit high
> > enough and you get the full original message appended.
>
> Perhaps like this?
>
> bounce_size_limit = $message_size_limit
That will fail when the original message was already close
Hi,
I was under the impression, that smtpd_recipient_restrictions and other
restriction configuration items were being processed top to bottom.
I am running postfix 3.2.2 and as far as I can see my postfix is showing a
different behavior.
I have the following items in my config:
smtpd_reci
On Thu, May 09, 2019 at 06:23:32PM +0200, Bastian Blank wrote:
> On Thu, May 09, 2019 at 06:11:46PM +0200, Arjen Van Drie wrote:
>
> > I fully agree with you, if it were not that our application needs the full
> > message in the bounce. You indeed argue that we should rewrite the
> > application,
On Thu, May 09, 2019 at 06:11:46PM +0200, Arjen Van Drie wrote:
> I fully agree with you, if it were not that our application needs the full
> message in the bounce. You indeed argue that we should rewrite the
> application, and again I agree. For now, and for various reasons, that just
> isn't pos
On 09/05/2019 17:53, Viktor Dukhovni wrote:
On May 9, 2019, at 7:31 AM, Arjen Van Drie
wrote:
Isn't the bounce_size always larger than the original message_size due to added
postmaster delivery failure stanza?
Yes, but it can't be larger than the message size limit. Postfix
will not creat
> On May 9, 2019, at 7:31 AM, Arjen Van Drie
> wrote:
>
> Isn't the bounce_size always larger than the original message_size due to
> added postmaster delivery failure stanza?
Yes, but it can't be larger than the message size limit. Postfix
will not create queue files that exceed the limit.
>Matus UHLAR - fantomas:
>> does it make sense to run tlsproxy when post-220 tests are not run?
On 03.05.19 12:40, Wietse Venema wrote:
>tlsproxy is required when:
>
>- postscreen: always when the server announces STARTTLS.
>
>- smtp client: always when connection reuse for TLS is enabled.
>
>T
Isn't the bounce_size always larger than the original message_size due
to added postmaster delivery failure stanza?
Arjen.
On 5/9/19 1:12 PM, Wietse Venema wrote:
Arjen Van Drie:
It works exactly as Wietse pointed out. Set bounce_size_limit high
enough and you get the full original message
Matus UHLAR - fantomas:
> On 03.05.19 12:40, Wietse Venema wrote:
> >Matus UHLAR - fantomas:
> >> does it make sense to run tlsproxy when post-220 tests are not run?
> >
> >tlsproxy is required when:
> >
> >- postscreen: always when the server announces STARTTLS.
> >
> >- smtp client: always when c
Arjen Van Drie:
>
> It works exactly as Wietse pointed out. Set bounce_size_limit high
> enough and you get the full original message appended.
Perhaps like this?
bounce_size_limit = $message_size_limit
Wietse
On 03.05.19 12:40, Wietse Venema wrote:
Matus UHLAR - fantomas:
does it make sense to run tlsproxy when post-220 tests are not run?
tlsproxy is required when:
- postscreen: always when the server announces STARTTLS.
- smtp client: always when connection reuse for TLS is enabled.
The postscr
It works exactly as Wietse pointed out. Set bounce_size_limit high
enough and you get the full original message appended.
Arjen.
On 5/8/19 9:10 PM, Arjen Van Drie wrote:
Thanks,
I will try it and provide feedback.
Arjen.
On 5/8/2019 7:55 PM, Wietse Venema wrote:
Arjen Van Drie:
Hi List
20 matches
Mail list logo
