Hello,
We have in main.cf always_bcc = zz...@xx.com and our domain is xx.com
For specific 2 recipients of our domain, we don't want always_bcc to
be implemented. ie. if a mail is addressed to a...@xx.com (our domain
only), mail should not be Bcc to zz...@xx.com. similarly if mail
I added onmicrosoft.com to my sender access file, I've dumped 10 so far.
On 1/7/24 1:41 PM, Matus UHLAR - fantomas via Postfix-users wrote:
On 07.01.24 10:17, John Hill via Postfix-users wrote:
First I am really amazed at the amount of support, that's not true
everywhere. I also like the tone
On 07.01.24 10:17, John Hill via Postfix-users wrote:
First I am really amazed at the amount of support, that's not true
everywhere. I also like the tone of the posts, very respectful.
I have 3.7.9 and all the settings.
Outlook protection is slamming me, 6 to 10 worthless emails every day.
Thx. Will do!
--john
On 1/7/24 12:57 PM, mailmary--- via Postfix-users wrote:
Same here, but I found some interesting facts about outlook spam, they have 4
common marks that can be used to catch them with Spamassassin.
The following rules block all outlook spam, but will also block some
Same here, but I found some interesting facts about outlook spam, they have 4
common marks that can be used to catch them with Spamassassin.
The following rules block all outlook spam, but will also block some legitimate
emails that use "undisclosed recipients". Not a big deal for me and my
First I am really amazed at the amount of support, that's not true
everywhere. I also like the tone of the posts, very respectful.
I have 3.7.9 and all the settings.
Outlook protection is slamming me, 6 to 10 worthless emails every day.
glad they don't make condoms.
I have sent everyone
Damian via Postfix-users:
> If I remember correctly, on the wire there was \r\n\r\n.\r\r\n
That is not a viable spoofing attack pattern.
To understand why, recall that an authenticated attacker sends an
email message to email service A, that contains a non-standard
End-of-DATA in the middle
On Sat, Jan 06, 2024 at 20:10:34 -0500, Wietse Venema via Postfix-users wrote:
> People are welcome to test tools against postfix-3.9-20240106.
With postfix-3.9-20240106 (with smtpd_forbid_bare_newline=yes but
smtpd_forbid_unauth_pipelining=no) all smuggling tests now fail,
including CRCRL
People are welcome to test tools against postfix-3.9-20240106.
I could test against a 3.7.9 codebase if you posted a patch for it.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to
