> I would never do this. My rule is very simple, anything we accept gets
> delivered to the user. Anything we reject gets rejected during the SMTP
> transaction. If it is LEGITIMATE mail, the sender will see the rejection.
This simple rule ensures a timely notification of the sender if something is
On 20 May 2019, at 01:42, Brent Clark wrote:
> My colleague has proposed that at smtp time, if a mail is deemed as spam, the
> server issues a reject code, but then to too accept the mail and forward the
> mail the user for incase its a false positive.
The odds of a mail scoring over 10.0 on Sp
Hi all,
I was looking through a few lists of RBLs and I’m not finding quite what I want.
I have quite a bit of my spam blocking working fairly well, but I’m seeing
quite a bit of “snowshoe spam” from a few providers. Rather than look up their
netblocks and outright block them, I’d like to incor
On 5/20/2019 2:42 AM, Brent Clark wrote:
Good day Guys
Just want to check with the community.
My colleague has proposed that at smtp time, if a mail is deemed as
spam, the server issues a reject code, but then to too accept the
mail and forward the mail the user for incase its a false positiv
Fred Barachant:
> Hi.
>
> SNI support for smtp server and client is said to be there, from
> what i read in release notes from 3.4.0. (
> http://www.postfix.org/announcements/postfix-3.4.0.html ) However,
> docs still say that it is not done not planned (
> http://www.postfix.org/TLS_README.html )
On 20 May 2019, at 3:42, Brent Clark wrote:
Good day Guys
Just want to check with the community.
My colleague has proposed that at smtp time, if a mail is deemed as
spam, the server issues a reject code, but then to too accept the mail
and forward the mail the user for incase its a false pos
Good day Guys
Just want to check with the community.
My colleague has proposed that at smtp time, if a mail is deemed as
spam, the server issues a reject code, but then to too accept the mail
and forward the mail the user for incase its a false positive.
His logic is that, that the spammer d
On 20.05.19 09:17, sandermo...@telenet.be wrote:
Thanks. I modified the internal server to reply with 550 instead of 450 and now
postfix is using 550 too :-)
Other question:
Can I somehow have postfix only verify recipient addresses for internal
mailservers?
Right now it's doing this for outg
Thanks. I modified the internal server to reply with 550 instead of 450 and now
postfix is using 550 too :-)
Other question:
Can I somehow have postfix only verify recipient addresses for internal
mailservers?
Right now it's doing this for outgoing emails too, verifying the recipient
address,
On 20.05.19 08:46, sandermo...@telenet.be wrote:
I have:
# postconf |grep unverified_recipient_reject_
unverified_recipient_reject_code = 550
unverified_recipient_reject_reason = Unknown recipient address
Yet, postfix is still rejecting with:
May 20 08:38:27 mx10 postfix/smtpd[8934]: NOQUEUE:
10 matches
Mail list logo
