On Thu, April 8, 2010 12:32 pm, Dirk H. Schulz said:
> I have configured my Postfix to use multiple access lists like that:
>> check_client_access hash:/usr/pkg/etc/postfix-in/list1,
>> hash:/usr/pkg/etc/postfix-in/list2
> I think this has worked some time, but it do
Hi all,
I have configured my Postfix to use multiple access lists like that:
check_client_access hash:/usr/pkg/etc/postfix-in/list1,
hash:/usr/pkg/etc/postfix-in/list2
I think this has worked some time, but it does not now - list2 seems not
to be used.
I do not find anything in official docs
Hi Wietse,
Wietse Venema schrieb:
Dirk H. Schulz:
Hi folks,
I am running postfix mail gateways on several UNIXes, and they have the
same or similar configurations.
On my NetBSD gateway I get lots of these errors in the mail log:
spawn[18506]: fatal: spawn_comand: execvp
/usr/local
Hi folks,
I am running postfix mail gateways on several UNIXes, and they have the
same or similar configurations.
On my NetBSD gateway I get lots of these errors in the mail log:
spawn[18506]: fatal: spawn_comand: execvp
/usr/local/lib/postfix-policyd-spf-perl: No such file or directory
This
I am thinking of concepts like this now and then. They do have one
advantage over simple replication techniques:
- with replication, you have a replication interval and a certain
guarantee for losses of those mails received within the replication
interval in case of a creash (you can solve tha
