Re: email from servers claiming to be ours

2021-11-16 Thread Ruben Safir
On Wed, Nov 17, 2021 at 07:56:12AM +0100, Benny Pedersen wrote: > On 2021-11-16 23:55, Ruben Safir wrote: > >I got an email from cpa...@mrbrklyn.com which is not from > >us, as we are mrbrklyn.com > > local envelope sender should be rejected in port 25, no real users > do this > my mailing lists

Re: email from servers claiming to be ours

2021-11-16 Thread Ruben Safir
On Wed, Nov 17, 2021 at 07:56:12AM +0100, Benny Pedersen wrote: > On 2021-11-16 23:55, Ruben Safir wrote: > >I got an email from cpa...@mrbrklyn.com which is not from > >us, as we are mrbrklyn.com > > local envelope sender should be rejected in port 25, no real users > do this > > symtoms is enve

Re: email from servers claiming to be ours

2021-11-16 Thread Benny Pedersen
On 2021-11-17 05:08, Ruben Safir wrote: In /etc/postfix/main.cf: smtpd_sender_restrictions = permit_mynetworks permit_sasl_authenticated check_sender_access pcre:/etc/postfix/sender-access permit I want it to accept email from my local machines and my own serv

Re: email from servers claiming to be ours

2021-11-16 Thread Dominic Raferd
On 16/11/2021 22:55, Ruben Safir wrote: I got an email from cpa...@mrbrklyn.com which is not from us, as we are mrbrklyn.com How do I block email with this on the From line From cpa...@mrbrklyn.com Tue Nov 16 03:59:34 2021 Return-Path: X-Original-To: ru...@mrbrklyn.com Delivered-To: ru...@mr

Re: email from servers claiming to be ours

2021-11-16 Thread Benny Pedersen
On 2021-11-16 23:55, Ruben Safir wrote: I got an email from cpa...@mrbrklyn.com which is not from us, as we are mrbrklyn.com local envelope sender should be rejected in port 25, no real users do this symtoms is envelope sender is equal to envelope recipient, but this should only be accepted

Re: email from servers claiming to be ours

2021-11-16 Thread raf
On Tue, Nov 16, 2021 at 11:22:03PM -0500, Ruben Safir wrote: > On 11/16/21 19:57, raf wrote: > > This only applies the check for email that isn't coming > > from your own networks/users. > > Sorry - I misunderstood. Thanks I will study this > > Reuvain The following documents will help: The

Re: email from servers claiming to be ours

2021-11-16 Thread Ruben Safir
On 11/16/21 19:57, raf wrote: > This only applies the check for email that isn't coming > from your own networks/users. Sorry - I misunderstood. Thanks I will study this Reuvain -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proport

Re: email from servers claiming to be ours

2021-11-16 Thread Ruben Safir
On Wed, Nov 17, 2021 at 11:57:28AM +1100, raf wrote: > On Tue, Nov 16, 2021 at 05:55:03PM -0500, Ruben Safir > wrote: > > > I got an email from cpa...@mrbrklyn.com which is not from > > us, as we are mrbrklyn.com > > > > How do I block email with this on the From line > > > > >From cpa...@mrbr

Re: email from servers claiming to be ours

2021-11-16 Thread raf
On Tue, Nov 16, 2021 at 05:55:03PM -0500, Ruben Safir wrote: > I got an email from cpa...@mrbrklyn.com which is not from > us, as we are mrbrklyn.com > > How do I block email with this on the From line > > >From cpa...@mrbrklyn.com Tue Nov 16 03:59:34 2021 I think the simplest approach to re

Re: email from servers claiming to be ours

2021-11-16 Thread postfix
> On 11-16-2021 5:55 pm, Ruben Safir wrote: > I got an email from cpa...@mrbrklyn.com which is not from > us, as we are mrbrklyn.com > > How do I block email with this on the From line You could just block any mail received on port 25 with mrbrklyn.com using a header check as someone else menti

Re: email from servers claiming to be ours

2021-11-16 Thread Ralph Seichter
* Ruben Safir: > How do I block email with this on the From line You can use Postfix's header_checks(5) content inspection for message headers, and check_sender_access to reject based on the envelope sender address. -Ralph

email from servers claiming to be ours

2021-11-16 Thread Ruben Safir
I got an email from cpa...@mrbrklyn.com which is not from us, as we are mrbrklyn.com How do I block email with this on the From line >From cpa...@mrbrklyn.com Tue Nov 16 03:59:34 2021 Return-Path: X-Original-To: ru...@mrbrklyn.com Delivered-To: ru...@mrbrklyn.com Received: from bizcloud-linmaxt

Re: heads up: dkimpy-milter signing breaks w/ python 3.10 (e.g., @ fedora 45 -> 35 upgrade)

2021-11-16 Thread PGNet Dev
On 11/2/21 16:26, Scott Kitterman wrote: On November 2, 2021 8:18:54 PM UTC, PGNet Dev wrote: i've reported the bug here, python 3.10 incompat, exec FAILs @ "SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats" https://bugs.launchpad.net/dkimpy-milter/+bug/1949520 fwi

Re: header_checks - transport problem

2021-11-16 Thread postfix-users
Yes, smtp-sec and smtp-safe is the same (copy paste mistake...) Thanks for the explanation. postfix-us...@mattern.org: and a test header check: /^Subject: test1test/?? FILTER smtp-sec: ... Nov 16 13:38:19 mailtest1 postfix/cleanup[1147934]: 5C0D85B05: filter: header Subject: test1test fro

Re: feature request: improve vague/incorrect error message

2021-11-16 Thread Matus UHLAR - fantomas
On 16.11.21 13:16, Jim wrote: At first glance I wouldn't see that related to mbox vs. maildir, but I've been surprised before. if you only need to read header of each file (maildir), it should be faster than read whole file (mbox). yes, IMAP sometimes needs to read while mail file for its stru

Re: feature request: improve vague/incorrect error message

2021-11-16 Thread Jim
On Tue, Nov 16, 2021 at 11:41 (-0500), Kris Deugau wrote: > Jim wrote: >> On Mon, Nov 15, 2021 at 12:25 (-0500), Wietse Venema wrote: >>> Instead, use Maildir format with one message per file, >> I thought about that once, but I decided I have too many e-mail >> messages for that. (I don't want

Re: feature request: improve vague/incorrect error message

2021-11-16 Thread Kris Deugau
Jim wrote: On Mon, Nov 15, 2021 at 12:25 (-0500), Wietse Venema wrote: Finally, if you want to keep lots of mail around, don't keep everything in one huge mailbox file. I actually have a bunch of huge mailbox files ;-) (Yeah, way too much email.) Instead, use Maildir format with one message

Re: header_checks - transport problem

2021-11-16 Thread Wietse Venema
postfix-us...@mattern.org: > and a test header check: > /^Subject: test1test/?? FILTER smtp-sec: ... > Nov 16 13:38:19 mailtest1 postfix/cleanup[1147934]: 5C0D85B05: > filter: header Subject: test1test from unknown[192.0.2.1]; > from= to= proto=ESMTP > helo=: smtp-safe: If smtp-sec (smtp-safe

Re: Postfix -> bogofilter -> Dovecot -> Sieve

2021-11-16 Thread Benny Pedersen
On 2021-11-16 03:37, Mike wrote: I've been successful at getting it to add the bogofilter header as needed, but don't understand what I need to do in order to have it get routed to sieve. its job of dovecot to use the sieve filter not postfix, thats why its undokumented in postfix Anyone

header_checks - transport problem

2021-11-16 Thread postfix-users
Hi all, I try to use header_checks to route mails with a specific header through a different SMTP with special TLS options. Therefore I configured a new SMTP service in master.cf:     smtp-sec  unix  -   -   y   -   -   smtp   -o smtp_header_checks=   -o syslog_

Re: I need problem tu]o understand

2021-11-16 Thread natan
Matus: On 16.11.2021 12:09, Matus UHLAR - fantomas wrote: >>> On 16.11.21 10:06, natan wrote: I need some help about uderstand log: I have FILTER smtp-amavis:[127.0.0.1]:10628 > >> On 16.11.2021 10:22, Matus UHLAR - fantomas wrote: >>> you have this where? > > On 16.11.21 10:41

Re: I need problem tu]o understand

2021-11-16 Thread Matus UHLAR - fantomas
On 16.11.21 10:52, natan wrote: cat /var/log/mail.log |grep "4Hth4H05w6z20nfj" Nov 16 10:45:03 thebe4 postfix/smtpd[21880]: 4Hth4H05w6z20nfj: client=s2b.hekko.net.pl[195.78.66.142] Nov 16 10:45:03 thebe4 postfix/cleanup[23606]: 4Hth4H05w6z20nfj: message-id=<3dd29e4f-f107-67f0-2331-3219fd752...@pe

Re: I need problem tu]o understand

2021-11-16 Thread Matus UHLAR - fantomas
On 16.11.21 10:06, natan wrote: I need some help about uderstand log: I have FILTER smtp-amavis:[127.0.0.1]:10628 On 16.11.2021 10:22, Matus UHLAR - fantomas wrote: you have this where? On 16.11.21 10:41, natan wrote: in master.cf: smtp-amavis unix    -   -   -   -  

Re: I need problem tu]o understand

2021-11-16 Thread natan
Matus: cat /var/log/mail.log |grep "4Hth4H05w6z20nfj" Nov 16 10:45:03 thebe4 postfix/smtpd[21880]: 4Hth4H05w6z20nfj: client=s2b.hekko.net.pl[195.78.66.142] Nov 16 10:45:03 thebe4 postfix/cleanup[23606]: 4Hth4H05w6z20nfj: message-id=<3dd29e4f-f107-67f0-2331-3219fd752...@pendragon.pl> Nov 16 10:45:0

Re: I need problem tu]o understand

2021-11-16 Thread natan
On 16.11.2021 10:22, Matus UHLAR - fantomas wrote: > On 16.11.21 10:06, natan wrote: >> I need some help about uderstand log: >> >> I have >> FILTER smtp-amavis:[127.0.0.1]:10628 > > you have this where? in master.cf: smtp-amavis unix    -   -   -   -   140   smtp    

Re: I need problem tu]o understand

2021-11-16 Thread Matus UHLAR - fantomas
On 16.11.21 10:06, natan wrote: I need some help about uderstand log: I have FILTER smtp-amavis:[127.0.0.1]:10628 you have this where? this is local haproxy where connect postfix to port 10628 like: ... bind 127.0.0.1:10628   server amavis1 86.xxx.xxx.125:10628 check maxconn   server amavi

Re: Postfix not talking to postgrey

2021-11-16 Thread Matus UHLAR - fantomas
On 15.11.21 14:32, Greg Earle wrote: I installed postgrey on a mail server host running Fedora, but for some reason Postfix doesn't seem to want to talk to it. why did you configure postgrey? It's largely obsoleted with postfix' much better postscreen functionality - weighed block/allowlists,

I need problem tu]o understand

2021-11-16 Thread natan
Hi I need some help about uderstand log: I have FILTER smtp-amavis:[127.0.0.1]:10628 this is local haproxy where connect postfix to port 10628 like: ... bind 127.0.0.1:10628   server amavis1 86.xxx.xxx.125:10628 check maxconn   server amavis2 86.xxx.xxx.155:10628 check maxconn   server amavis3 8