Accept email with 5xx status code

2019-01-16 Thread Pali Rohár
Hello, it is possible to accept emails with 5xx status code? Why such behavior? I want to return 5xx status codes when email is reject (to prevent sending bounces), but I would like to store copy of rejected emails in case some inspection would be needed in future. Storing copy of those emails int

detecting TLS issues in delivery - Cannot start TLS: handshake failure

2019-01-16 Thread Stefan Bauer
Hi, how can the following error be detected and an instant bounce/reject will be send to the sender? -- 880 Kbytes in 3 Requests. root@mx1:~# mailq -Queue ID- --Size-- Arrival Time -Sender/Recipient--- A97288008B 776694 Sun Jan 13 13:14:29 sender@sender

Re: Query about restriction scenario in RESTRICTION_CLASS_README

2019-01-16 Thread Wietse Venema
Mayuresh: > Sure. Basically I see only one hash in your snippet - that of the > protected destinations. I did not notice a hash of senders allowed to send > to the protected destinations. Am I missing something? Original example: /etc/postfix/main.cf: smtpd_recipient_restrictions =

Re: detecting TLS issues in delivery - Cannot start TLS: handshake failure

2019-01-16 Thread Wietse Venema
Stefan Bauer: > Hi, > > how can the following error be detected and an instant bounce/reject will > be send to the sender? > > -- 880 Kbytes in 3 Requests. > root@mx1:~# mailq > -Queue ID- --Size-- Arrival Time -Sender/Recipient--- > A97288008B 776694 Sun Jan 13 13:14:29 sender@se

Re: Accept email with 5xx status code

2019-01-16 Thread Wietse Venema
Pali Roh?r: > Hello, it is possible to accept emails with 5xx status code? By replying with 5XX after SMTP end-of-data. Wietse > Why such behavior? I want to return 5xx status codes when email is > reject (to prevent sending bounces), but I would like to store copy of > rejected emails i

Re: detecting TLS issues in delivery - Cannot start TLS: handshake failure

2019-01-16 Thread Stefan Bauer
reject_unverified_recipient is no option as remote sites don't like probing/verify requests. After rechecking, i had a typo in my regex. Damn! It was working as documented. Sorry. Am Mi., 16. Jan. 2019 um 13:17 Uhr schrieb Wietse Venema < wie...@porcupine.org>: > Stefan Bauer: > > Hi, > > > > h

Re: Query about restriction scenario in RESTRICTION_CLASS_README

2019-01-16 Thread Mayuresh
On Wed, Jan 16, 2019 at 07:14:37AM -0500, Wietse Venema wrote: > All I suggested was to split smtpd_recipient_restrictions > and use smtpd_relay_restrictions for the spam blocks. > > That was, TO SPLIT smtpd_recipient_restrictions, NOT TO REMOVE > the hash maps. Ok, thanks. Mayuresh

Re: detecting TLS issues in delivery - Cannot start TLS: handshake failure

2019-01-16 Thread Wietse Venema
Stefan Bauer: > reject_unverified_recipient is no option as remote sites don't like > probing/verify requests. After rechecking, i had a typo in my regex. reject_unverified RECIPIENT, not reject_unverified_SENDER Wietse > Damn! It was working as documented. Sorry. > > > Am Mi., 16. Jan

Re: detecting TLS issues in delivery - Cannot start TLS: handshake failure

2019-01-16 Thread Viktor Dukhovni
> On Jan 16, 2019, at 9:56 AM, Wietse Venema wrote: > >> reject_unverified_recipient is no option as remote sites don't like >> probing/verify requests. After rechecking, i had a typo in my regex. > > reject_unverified RECIPIENT, not reject_unverified_SENDER Specifically, because it would be us

Re: Accept email with 5xx status code

2019-01-16 Thread Bill Cole
On 16 Jan 2019, at 4:15, Pali Rohár wrote: Hello, it is possible to accept emails with 5xx status code? Why such behavior? I want to return 5xx status codes when email is reject (to prevent sending bounces), but I would like to store copy of rejected emails in case some inspection would be need

Re: detecting TLS issues in delivery - Cannot start TLS: handshake failure

2019-01-16 Thread Stefan Bauer
"Some sites may blacklist you when you are probing them too often (a probe is an SMTP session that does not deliver mail), or when you are probing them too often for a non-existent address. This is one reason why you should use sender address verification sparingly, if at all, when your site receiv

Re: detecting TLS issues in delivery - Cannot start TLS: handshake failure

2019-01-16 Thread Viktor Dukhovni
> On Jan 16, 2019, at 3:24 PM, Stefan Bauer wrote: > > "Some sites may blacklist you when you are probing them too often (a probe is > an SMTP session that does not deliver mail), or when you are probing them too > often for a non-existent address. This is one reason why you should use > sende

Question on how to deal with bad recipient address

2019-01-16 Thread Ski Kacoroski
Hi, I have a blackbox UPS that send this email when I look at it with postcat *** MESSAGE CONTENTS deferred/B/BFE60169 *** regular_text: Received: from loki.nsd.org (ups-tms.nsd.org [10.145.1.25]) regular_text: by sys.nsd.org (Postfix) with ESMTP id BFE60169 regular_text: for ; Wed, 16 Jan 20

Re: Question on how to deal with bad recipient address

2019-01-16 Thread Wietse Venema
Ski Kacoroski: > Hi, > > I have a blackbox UPS that send this email when I look at it with postcat > > *** MESSAGE CONTENTS deferred/B/BFE60169 *** > regular_text: Received: from loki.nsd.org (ups-tms.nsd.org [10.145.1.25]) > regular_text: by sys.nsd.org (Postfix) with ESMTP id BFE60169 >

Re: Query about restriction scenario in RESTRICTION_CLASS_README

2019-01-16 Thread Mayuresh
On Wed, Jan 16, 2019 at 07:14:37AM -0500, Wietse Venema wrote: > insiders_only = check_sender_access hash:/etc/postfix/insiders, reject On above line if I replace reject with reject_unauth_destination it becomes permissive rather than rejecting. What is the exact difference between reject