On 1 Nov 2018, at 12:03, Viktor Dukhovni wrote:
On Nov 1, 2018, at 11:30 AM, Bill Cole
wrote:
I intend to experiment with postscreen on 587 on the next Postfix
system I work with where compromised accounts are a problem.
Don't waste your time. Postscreen cannot help you with this.
Postscre
Viktor Dukhovni:
> > On Nov 1, 2018, at 11:30 AM, Bill Cole
> > wrote:
> >
> > I intend to experiment with postscreen on 587 on the next Postfix
> > system I work with where compromised accounts are a problem.
>
> Don't waste your time. Postscreen cannot help you with this.
> Postscreen mainta
Bill Cole:
> On 31 Oct 2018, at 17:12, Noel Jones wrote:
>
> > Postscreen *should not* be used on ports used for client
> > authenticated SMTP.
>
> Generally, this has been true...
>
> However, I have recently seen spambots using compromised accounts on
> port 587 without properly waiting for t
> On Nov 1, 2018, at 11:30 AM, Bill Cole
> wrote:
>
> I intend to experiment with postscreen on 587 on the next Postfix
> system I work with where compromised accounts are a problem.
Don't waste your time. Postscreen cannot help you with this.
Postscreen maintains dynamic IP-address whitelists
On 31 Oct 2018, at 17:12, Noel Jones wrote:
Postscreen *should not* be used on ports used for client
authenticated SMTP.
Generally, this has been true...
However, I have recently seen spambots using compromised accounts on
port 587 without properly waiting for the greeting banner. This was o
On 10/31/2018 3:52 PM, Fazzina, Angelo wrote:
> Hi, i am learning/testing Postscreen on Postfix 2.10.1
>
> I read the man page and need a little help understanding this :
>
>
>
> This program should not be used on SMTP ports that receive mail from
> end-user clients (MUAs). In a typical
>
>
Hi, i am learning/testing Postscreen on Postfix 2.10.1
I read the man page and need a little help understanding this :
This program should not be used on SMTP ports that receive mail from end-user
clients (MUAs). In a typical
deployment, postscreen(8) handles the MX service on TCP port