/dev/rob0:
On Fri, Jun 03, 2011 at 01:09:28PM -0400, Wietse Venema wrote:
postscreen_whitelist_interfaces matters only for clients that are
not yet whitelisted (or that have expired).
Issue: previously whitelisted client gets WHITELIST VETO on secondary
Of course, being whitelisted once
On Sun, Jun 05, 2011 at 09:21:21AM -0400, Wietse Venema wrote:
/dev/rob0:
On Fri, Jun 03, 2011 at 01:09:28PM -0400, Wietse Venema wrote:
postscreen_whitelist_interfaces matters only for clients that
are not yet whitelisted (or that have expired).
Issue: previously whitelisted client
/dev/rob0:
Jun 5 01:50:46 cardinal postfix/postscreen[15628]: CONNECT from
[174.37.3.121]:33695 to [216.23.247.74]:25
Jun 5 01:50:52 cardinal postfix/postscreen[15628]: PASS OLD
[174.37.3.121]:33695
Jun 5 01:50:52 cardinal postfix/smtpd[15816]: connect from
Hello all,
Since till now i was using postfix 2.5 i am planning to upgrade to 2.8
because i see 2 major feature multi -instance and postscreen can any one
give me with example of an ideal conguration .
Regards,
Kshitij
On Sun, Jun 5, 2011 at 7:51 PM, Wietse Venema wie...@porcupine.org wrote:
On 06/05/2011 04:54 PM, kshitij mali wrote:
Hello all,
HI!
Please:
1. DO NOT Top-post,
2. Reply to the LIST, and
3. DO NOT hijack threads for your own issues.
Thanks!
--
J.
On Sun, Jun 05, 2011 at 10:21:38AM -0400, Wietse Venema wrote:
/dev/rob0:
Jun 5 01:50:46 cardinal postfix/postscreen[15628]: CONNECT from
[174.37.3.121]:33695 to [216.23.247.74]:25
Jun 5 01:50:52 cardinal postfix/postscreen[15628]: PASS OLD
[174.37.3.121]:33695
Jun 5 01:50:52
On Fri, Jun 03, 2011 at 01:09:28PM -0400, Wietse Venema wrote:
postscreen_whitelist_interfaces matters only for clients that are
not yet whitelisted (or that have expired).
Issue: previously whitelisted client gets WHITELIST VETO on secondary
MX IP address (excluded from
The postconf(5) manual entry for postscreen_whitelist_interfaces
includes this text:
When postscreen(8) listens on both primary and backup MX addresses,
the postscreen_whitelist_interfaces parameter can be used to disable
whitelisting on backup MX addresses. With this configuration,
/dev/rob0:
The postconf(5) manual entry for postscreen_whitelist_interfaces
includes this text:
When postscreen(8) listens on both primary and backup MX addresses,
the postscreen_whitelist_interfaces parameter can be used to disable
whitelisting on backup MX addresses. With this
