Re: Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Jim Popovitch
On Mon, 2021-05-31 at 19:07 -0400, Wietse Venema wrote: > Jim Popovitch: > > > Postfix will try each IP address in the order as returned from > > > getaddrinfo(3) until it can establish a TCP connection. Postfix > > > will not reconnect when an established Milter connection goes bad. > > > For exam

Re: Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Wietse Venema
Jim Popovitch: > > Postfix will try each IP address in the order as returned from > > getaddrinfo(3) until it can establish a TCP connection. Postfix > > will not reconnect when an established Milter connection goes bad. > > For example, the Milter does not respond, or produces bad responses. > >

Re: Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Jim Popovitch
On Mon, 2021-05-31 at 18:20 -0400, Wietse Venema wrote: > Jim Popovitch: > > On Mon, 2021-05-31 at 16:18 -0400, Wietse Venema wrote: > > > Jim Popovitch: > > > > Hello, > > > > > > > > If given hostname that resolves to multiple A/ records, will > > > > smtpd_milters=inet:... cycle through all

Re: Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Wietse Venema
Jim Popovitch: > On Mon, 2021-05-31 at 16:18 -0400, Wietse Venema wrote: > > Jim Popovitch: > > > Hello, > > > > > > If given hostname that resolves to multiple A/ records, will > > > smtpd_milters=inet:... cycle through all A/ records until if > > > finds a host that it can connect to? >

Re: Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Wietse Venema
Jaroslaw Rafa: > Dnia 31.05.2021 o godz. 16:18:03 Wietse Venema pisze: > > > > Postfix will try each IP address (as returned from getaddrinfo(3)) > > until it can establish a TCP connection. Postfix does not randomize > > the order of these IP addresses, > > Although the DNS resolver itself could

Re: Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Jaroslaw Rafa
Dnia 31.05.2021 o godz. 16:18:03 Wietse Venema pisze: > > Postfix will try each IP address (as returned from getaddrinfo(3)) > until it can establish a TCP connection. Postfix does not randomize > the order of these IP addresses, Although the DNS resolver itself could randomize it. -- Regards,

Re: Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Jim Popovitch
On Mon, 2021-05-31 at 16:18 -0400, Wietse Venema wrote: > Jim Popovitch: > > Hello, > > > > If given hostname that resolves to multiple A/ records, will > > smtpd_milters=inet:... cycle through all A/ records until if > > finds a host that it can connect to? > > Postfix will try each IP a

Re: Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Wietse Venema
Jim Popovitch: > Hello, > > If given hostname that resolves to multiple A/ records, will > smtpd_milters=inet:... cycle through all A/ records until if > finds a host that it can connect to? Postfix will try each IP address (as returned from getaddrinfo(3)) until it can establish a TCP co

Does smtpd_milters=inet:.... round-robin if the hostname has multiple IPs?

2021-05-31 Thread Jim Popovitch
Hello, If given hostname that resolves to multiple A/ records, will smtpd_milters=inet:... cycle through all A/ records until if finds a host that it can connect to? If so, does it make sense to reduce milter_connect_timeout to 10 or 15 seconds? tia, -Jim P.

Re: authentication required error codes

2021-05-31 Thread Wietse Venema
Matus UHLAR - fantomas: > Hello, > > looking at postfix logs I found out that with standard restrictions > inherited from main.cf at ports 465/587, the client gets error message like: > > May 30 12:05:04 mail postfix/submission/smtpd[22649]: NOQUEUE: reject: RCPT > from unknown[192.0.2.1]: 504 5

Re: authentication required error codes

2021-05-31 Thread Jaroslaw Rafa
Dnia 31.05.2021 o godz. 16:48:41 Matus UHLAR - fantomas pisze: > > standard master.cf contains proposed overrides for submission/submissions > services: > > # -o smtpd_client_restrictions=$mua_client_restrictions > # -o smtpd_helo_restrictions=$mua_helo_restrictions > # -o smtpd_sender_restric

authentication required error codes

2021-05-31 Thread Matus UHLAR - fantomas
Hello, looking at postfix logs I found out that with standard restrictions inherited from main.cf at ports 465/587, the client gets error message like: May 30 12:05:04 mail postfix/submission/smtpd[22649]: NOQUEUE: reject: RCPT from unknown[192.0.2.1]: 504 5.5.2 : Helo command rejected: need fu

Re: Re: Use both recipient_bcc_maps and always_bcc

2021-05-31 Thread r . barclay
Matus and Viktor, thank you for your responses! I'm trying to add an additional BCC for some mail recipients but not for all. All mails must go into the archive (always_bcc). This works so far. But now, for some recipients, I'd like to have an additional BCC. So recipient_bcc_maps seems to be wha

Re: Use both recipient_bcc_maps and always_bcc

2021-05-31 Thread Viktor Dukhovni
On Mon, May 31, 2021 at 10:07:13AM +0200, r.barc...@habmalnefrage.de wrote: > I use the "always_bcc" option to collect all emails for a local email archive. > > Can one use recipient_bcc_maps in addition to that? > > So I could make emails to "u...@example.org" go into the archive (always_bcc)

Re: Use both recipient_bcc_maps and always_bcc

2021-05-31 Thread Matus UHLAR - fantomas
On 31.05.21 10:07, r.barc...@habmalnefrage.de wrote: I use the "always_bcc" option to collect all emails for a local email archive. Can one use recipient_bcc_maps in addition to that? this worked here iirc. So I could make emails to "u...@example.org" go into the archive (always_bcc) and al

Use both recipient_bcc_maps and always_bcc

2021-05-31 Thread r . barclay
Hello! I use the "always_bcc" option to collect all emails for a local email archive. Can one use recipient_bcc_maps in addition to that? So I could make emails to "u...@example.org" go into the archive (always_bcc) and also to another BCC address defined through recipient_bcc_maps? In the mai