but that *does not* help in case of the OP
read the thread start
it is simply impossible doing on one hand RCPT-verification because
no verification on the root-cause (webserver) but at the same time
not reject messages from the webserver in case verification on the
final destination is
Alexandre Ellert:
Is there anyway to populate a cache (file, SQL, ?) with real hard
bounces from remote SMTP and tell postfix to stop send mail to
these addresses next time ?
Postfix logs remote SMTP server responses. You provide a tool
that populates a table with bad addresses, and you
Alexandre Ellert skrev den 2014-01-10 22:12:
How can I tell Postfix to queue the mail in case of remote reply 4xx ?
4xx is softfails, so you already do
Am 11.01.2014 18:57, schrieb Benny Pedersen:
Alexandre Ellert skrev den 2014-01-10 22:12:
How can I tell Postfix to queue the mail in case of remote reply 4xx ?
4xx is softfails, so you already do
but that *does not* help in case of the OP
read the thread start
it is simply impossible
Wietse :
You can push the problem back to the webservers, by using the the
Postfix SMTP server's reject_unverified_recipient feature.
With this, Postfix will make one connection for the recipient
address, and then the Postfix SMTP server answers with 5XX to the
web application when that
Alexandre Ellert:
Wietse :
You can push the problem back to the webservers, by using the the
Postfix SMTP server's reject_unverified_recipient feature.
With this, Postfix will make one connection for the recipient
address, and then the Postfix SMTP server answers with 5XX to the
web
Wietse :
In that case use:
/etc/postfix/main.cf:
smtpd_recipient_restrictions =
...
check_sender_access hash:/etc/postfix/sender_access
...
/etc/postfix/sender_access:
x...@example.com reject_unverified_recipient
example.net
This works like a charm.
One last thing, concerning order of smtpd_recipient_restrictions, I currently
have this in master.cf :
submission inet n - - - - smtpd
...
-o
Alexandre Ellert:
[reject_unverified_recipient]
Can you confirm that in case of greylisting at the destination
SMTP, it will work fine ?
If the remote SMTP server uses greylisting, then the address
verification result will be don't know (*) and the Postfix SMTP server
will reply with 4xx
Wietse :
If the remote SMTP server uses greylisting, then the address
verification result will be don't know (*) and the Postfix SMTP server
will reply with 4xx (unless you configure Postfix otherwise).
Wietse
(*) The Postfix SMTP client does not distiunguish between different
Wietse :
If the remote SMTP server uses greylisting, then the address
verification result will be don't know (*) and the Postfix SMTP server
will reply with 4xx (unless you configure Postfix otherwise).
Wietse
(*) The Postfix SMTP client does not distiunguish between different
kinds
I made more tests and greylisting is still a problem.
I've tried with :
unverified_recipient_tempfail_action = permit
in main.cf
But I got :
fatal: bad configuration
in mail.log
How can I tell Postfix to queue the mail in case of remote reply 4xx ?
I answer to myself, it seems
Alexandre Ellert:
But I got :
fatal: bad configuration
in mail.log
Show the complete logfile record!
Wietse
Hi,
I relay transactional mail for my customer's web sites.
Each website has it's own SASL authenticated account and mail are sent via
submission or smtps.
But, some website doesn't verify email existence when a user submit a web form
or 'create an account'.
That's why I often see my postfix
Alexandre Ellert:
Hi,
I relay transactional mail for my customer's web sites.
Each website has it's own SASL authenticated account and mail are
sent via submission or smtps.
But, some website doesn't verify email existence when a user submit
a web form or 'create an account'.
That's
On 1/9/2014 4:41 PM, Alexandre Ellert wrote:
Hi,
I relay transactional mail for my customer's web sites.
Each website has it's own SASL authenticated account and mail are
sent via submission or smtps.
But, some website doesn't verify email existence when a user submit
a web form or
On 1/9/2014 5:01 PM, Noel Jones wrote:
On 1/9/2014 4:41 PM, Alexandre Ellert wrote:
Hi,
I relay transactional mail for my customer's web sites.
Each website has it's own SASL authenticated account and mail are
sent via submission or smtps.
But, some website doesn't verify email existence
17 matches
Mail list logo
