If people want to use a non RFC compliant verification system, then
they're going to have problems with false positives on their spam
filter.
The operative word being: they.
Your customer needs to get their email vendor to whitelist your trac
instance. You don't need to do anything....
--
Mike.
Quoting Dirk Stöcker <post...@dstoecker.de>:
On Sat, 18 Mar 2017, Richard Damon wrote:
- On your side, don't reject RCPT TO for the no-reply address.
- On your side, add a telepathic policy service that can distinguish
between RCPT TO to verify an address, and RCPT to deliver mail.
smtpd_recipient_restrictions =
....
reject_unauth_destination
check_policy_service unix:/some/where/telepathic-service
check_recipient_access inline:{
{ t...@email.tld = reject this address does not receive email }
}
Wietse
Couldn't you do something where you accept at the RCPT TO, and then
reject at End of Data having it just reject everything as spam?
http://www.postfix.org/SMTPD_PROXY_README.html
When its even possible to check spam without generating a bounce
message, why do I need telepathy to reject a mail for a known
situation in a later stage of mail delivery?
It is a bit of overkill to write a filter for that. I hoped there
would be an easier way.
Could it work to "Configure the Postfix SMTP pass-through proxy
feature" with the after filter SMTP server being directly the target
(i.e. omitting the filter) and putting the recipient reject on this
one instead of the initial connect?
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
Cheers,
--
Mike.
