On 11/7/2017 2:36 PM, Seb wrote:
>> I can confirm that the example greylist.pl program and sample
>> configuration work perfectly.
>
> This is very comforting. Would you mind telling me more? Did you try
> it yourself, just following the instructions in
> http://www.postfix.org/SMTPD_POLICY_RE
Hello,
Just because I don't see your implementation error doesn't mean there
isn't one.
Fair point.
I can confirm that the example greylist.pl program and sample
configuration work perfectly.
This is very comforting. Would you mind telling me more? Did you try it
yourself, just followin
On 11/7/2017 1:53 PM, Seb wrote:
> Well I just followed that path: reading carefully the documentation
> and reproducing as closely as possible the examples given within, to
> no avail. The documentation does mention sockets, even though its
> examples don't use them. So either way you are right :-
Hello,
My first guess is http://www.postfix.org/DEBUG_README.html#no_chroot
Sorry, wrong guess. Your test program is not a policy server.
http://www.postfix.org/addon.html#policy
I see. So the example given in the online documentation can't work, and
the more complete, apparently self-suff
On 11/7/2017 10:55 AM, Seb wrote:
>
> Hello,
>
>
My first guess is
http://www.postfix.org/DEBUG_README.html#no_chroot
>> Sorry, wrong guess. Your test program is not a policy server.
>> You need something that listens on a unix or tcp socket. An
>> incomplete list of available policy
Hello,
My first guess is
http://www.postfix.org/DEBUG_README.html#no_chroot
Sorry, wrong guess. Your test program is not a policy server. You need
something that listens on a unix or tcp socket. An incomplete list of
available policy servers can be found here:
http://www.postfix.org/addon
On 11/7/2017 10:18 AM, Seb wrote:
>
> Hello,
>
>
>> My first guess is
>> http://www.postfix.org/DEBUG_README.html#no_chroot
>
Sorry, wrong guess. Your test program is not a policy server. You
need something that listens on a unix or tcp socket. An incomplete
list of available policy servers
Hello,
My first guess is
http://www.postfix.org/DEBUG_README.html#no_chroot
So I went through /etc/postfix/master.cf and changed each line to make
sure that nothing was left in a chroot:
#egrep '^[a-z]' master.cf
smtp inet n - n - - smtpd
pickupfifo
On 11/7/2017 9:40 AM, Seb wrote:
>
> Hello,
>
>
>>> I run a small publishing company and for the sake of easing
>>> communication between authors (who work in teams) I have provided
>>> each of them with a local alias. Typically, mail sent to
>>> .@ is redirected to
>>> .@gmail.com, the usual em
Hello,
I run a small publishing company and for the sake of easing
communication between authors (who work in teams) I have provided each
of them with a local alias. Typically, mail sent to
.@ is redirected to
.@gmail.com, the usual email address of the
author.
You can use a postfix policy
Hello,
Thanks a lot Noel for this bird's-eye view of possible solutions. The most
promising tool for my setting seems to be Postfwd, which I'll now explore.
Sébastien.
One of the casualties in the war on spam is mail forwarders.
The built-in postfix way to control the sender/recipient p
On 10/19/2017 4:48 AM, Seb wrote:
>
> Hello,
>
>
> I run a small publishing company and for the sake of easing
> communication between authors (who work in teams) I have provided
> each of them with a local alias. Typically, mail sent to
> .@ is redirected to
> .@gmail.com, the usual email addre
On 19 October 2017 at 10:48, Seb wrote:
>
> ...
> Typically, mail sent to .@ is redirected
> to .@gmail.com, the usual email address of the
> author.
>
> I've been using this for 15+ years and it's been great. Unfortunately, I'm
> losing the war against spam. In spite of careful configuration of
Hello,
I run a small publishing company and for the sake of easing communication
between authors (who work in teams) I have provided each of them with a
local alias. Typically, mail sent to .@ is
redirected to .@gmail.com, the usual email address of
the author.
I've been using this for 15
14 matches
Mail list logo
