Re: Block email based on reply field

2019-12-18 Thread li...@lazygranch.com
On Wed, 18 Dec 2019 13:10:50 -0500 Viktor Dukhovni wrote: > [ I'm on the list, there's no need to Cc: me directly] > > On Wed, Dec 18, 2019 at 01:36:17AM -0800, li...@lazygranch.com wrote: > > > Viktor Dukhovni wrote: > > > > > header-checks.pcre: > > > if /^Reply-To:/ > > > #

Re: Rejecting email based upon MAIL FROM:, RCPT TO: and From: values

2019-12-18 Thread Bill Cole
On 18 Dec 2019, at 18:55, Konstantin Boyandin wrote: Hello, I need to possibly reject mail, in case the below is all true - domain part of From: header and RCPT TO: addresses is the same - domain part of MAIL FROM: differs from domain part of From: header Looks like I need to use filtering

Re: Rewriting e-mail headers (recipients) in Postfix (not header_checks) depending on complex logic

2019-12-18 Thread Bill Cole
On 18 Dec 2019, at 14:22, voroni...@soft-masters.ru wrote: I have a mail system on Postfix+dovecot+amavisd+spamassassin+clamav. Now there is a task, an easy one, actually, but I still cannot find a solution. I need to change headers in emails according to several rules. For example, IF (

Re: Rejecting email based upon MAIL FROM:, RCPT TO: and From: values

2019-12-18 Thread Wietse Venema
Konstantin Boyandin: > Hello, > > I need to possibly reject mail, in case the below is all true > > - domain part of From: header and RCPT TO: addresses is the same > - domain part of MAIL FROM: differs from domain part of From: header > > Looks like I need to use filtering via

Rejecting email based upon MAIL FROM:, RCPT TO: and From: values

2019-12-18 Thread Konstantin Boyandin
Hello, I need to possibly reject mail, in case the below is all true - domain part of From: header and RCPT TO: addresses is the same - domain part of MAIL FROM: differs from domain part of From: header Looks like I need to use filtering via check_policy_service; question is, into which

Re: Rewriting e-mail headers (recipients) in Postfix (not header_checks) depending on complex logic

2019-12-18 Thread Noel Jones
On 12/18/2019 1:22 PM, voroni...@soft-masters.ru wrote: I have a mail system on Postfix+dovecot+amavisd+spamassassin+clamav. Now there is a task, an easy one, actually, but I still cannot find a solution. I need to change headers in emails according to several rules. For example, |IF (

Rewriting e-mail headers (recipients) in Postfix (not header_checks) depending on complex logic

2019-12-18 Thread voronin_k
I have a mail system on Postfix+dovecot+amavisd+spamassassin+clamav. Now there is a task, an easy one, actually, but I still cannot find a solution. I need to change headers in emails according to several rules. For example, IF ( CONTAINS 'ALIAS_1' AND CONTAINS 'SOMEONE FROM ALIAS_1') OR (IF

Re: Block email based on reply field

2019-12-18 Thread Viktor Dukhovni
[ I'm on the list, there's no need to Cc: me directly] On Wed, Dec 18, 2019 at 01:36:17AM -0800, li...@lazygranch.com wrote: > Viktor Dukhovni wrote: > > > header-checks.pcre: > > if /^Reply-To:/ > > # Adjust to exactly match the observed header > > # Includes rule id in reject

Re: configuration postscreen

2019-12-18 Thread Claus R. Wickinghoff
Hi Wietse, So for me it still makes sense to combine postscreen with postgrey, as postscreen works mainly on ip addresses (their reputation in fact) while postgrey also takes care on sender's and recipient's e-mail addresses. By design, postscreen does not know the sender or recipient. In

Re: configuration postscreen

2019-12-18 Thread Wietse Venema
Wietse Venema: > Claus R. Wickinghoff: > > So for me it still makes sense to combine postscreen with postgrey, as > > postscreen works mainly on ip addresses (their reputation in fact) while > > postgrey also takes care on sender's and recipient's e-mail addresses. > > By design, postscreen

Re: DMARC usage opinion

2019-12-18 Thread Roberto Carna
Perfect!!! Now I understand and I'll to start DMARC implementation with p=none to see what happen. Regards !!! El mié., 18 dic. 2019 a las 7:22, Gregory Heytings () escribió: > > Hi, > > I'd second Viktor Dukhovni's opinion. For the vast majority of mail > servers, a minimalistic DMARC policy

Re: configuration postscreen

2019-12-18 Thread Wietse Venema
Claus R. Wickinghoff: > So for me it still makes sense to combine postscreen with postgrey, as > postscreen works mainly on ip addresses (their reputation in fact) while > postgrey also takes care on sender's and recipient's e-mail addresses. By design, postscreen does not know the sender or

Re: DMARC usage opinion

2019-12-18 Thread Gregory Heytings
Hi, I'd second Viktor Dukhovni's opinion. For the vast majority of mail servers, a minimalistic DMARC policy suffices, just add the following record in the domain's DNS root zone: _dmarc 10800 IN TXT "v=DMARC1; p=none;" If you want to go a step further, you can just monitor how DMARC is

Re: Block email based on reply field

2019-12-18 Thread li...@lazygranch.com
On Wed, 11 Dec 2019 21:56:48 -0500 Viktor Dukhovni wrote: > > On Dec 11, 2019, at 9:38 PM, li...@lazygranch.com wrote: > > > > I have a spammer who uses all sorts of "from" addresses but the same > > "reply" address. Any way to block this spammer in Postfix. > > main.cf: > pcre =

Re: Advice: NFS, hardware, SATA vs SAS etc

2019-12-18 Thread Matus UHLAR - fantomas
> > > Yes. Do any Postfix administrators with busy systems rely on NFS? > > > That seems like a really bad idea, honestly. > So NFS is a poor, outdated choice for mail storage in 2020 for a small/medium > enterprise? On any large number of users some kind of hash is used to distribute email