Use relay host if direct delivery fails

://ipcheck.proofpoint.com/?ip=xxx.xxx.xxx.xxx) What would be the best way to achieve my plan, when I don’t know ahead of time which destinations will be causing failures and I don’t want to relay through backup relay host all mail. Thanks, -sashk

Re: use relay host on direct connection failure

- see https://ipcheck.proofpoint.com/?ip=XXX.XXX.XXX.XXX  -sashk 28.04.2021, 09:50, "Aban Dokht" :sashk wrote: Hi, I have a server which is being blocked by one of the recipient, whose provider won't respond to unblock requestsHi,can you give the error line from your mail.log, when tr

use relay host on direct connection failure

Hi, I have a server which is being blocked by one of the recipient, whoseprovider won't respond to unblock requests (new server, new ip usualbs), and would like to workaround this by using relay host for suchcases. I know I can setup transport list for known domains, but how do Isetup this for unkn

Re: logrotate script for Postfix

%M - minute%m - month. you have a typo, should be: maillog_file_rotate_suffix = %Y%m%d-%H%M%S 09.05.2020, 11:32, "Larry Stone" : On May 9, 2020, at 9:45 AM, Wietse Venema wrote: If the log is written by Postfix you must use "postfix logrotate". This ensures that Postfix stops

Re: 3.3.0 -> 3.3.2 and sasl error

rg/contents?file=&path=&name=cyrus-sasl-login&branch=v3.9&repo=main&arch=x86_64 16.02.2019, 11:22, "sashk" : > Hello Patrick, > > Thanks for the response. > >>  The other side offers PLAIN LOGIN, but your smtp client doesn't like th

Re: 3.3.0 -> 3.3.2 and sasl error

Hello Patrick, Thanks for the response. > The other side offers PLAIN LOGIN, but your smtp client doesn't like that > because those are mechanisms which send identification data in clear (read: > unencrypted). That's because you have this (default) in place: > > smtp_sasl_security_options = no

3.3.0 -> 3.3.2 and sasl error

Hi, I've attempted upgrade of my postfix docker container from alpine 3.8 (which has postfix 3.3.0) to alpine 3.9 (postfix 3.3.2). Perfectly working config which just worked with 3.3.0 now causing SASL auth error: warning: SASL authentication failure: No worthy mechs found Here is verbose l

Re: destination_rate_delay and deferred queue

ns at once will cause a lock out, even if you send 3 messages for the day if they are sent in less than a second we will lock the connection. Thank you, -sashk

Re: destination_rate_delay and deferred queue

addressto Gmail.Well, google says otherwise. They say, there was two attempts to connect within the second, and they're banning me for that.  Thank you,-sashk  

Re: destination_rate_delay and deferred queue

recipient_limit = 5slow_initial_destination_concurrency = 1slow_destination_concurrency_limit = 1slow_destination_recipient_limit = 5slow_destination_rate_delay = 12stransport:gmail.com slow:domain.com slow:Thank you. -sashk 

Re: destination_rate_delay and deferred queue

s on first attempt to deliver messages, right after it received them from the smtp connection.Could you please point me into right direction?  Thank you. -sashk

destination_rate_delay and deferred queue

queue is not attempting to deliver messages more frequently than I specified in slow configuration; or  - deliver more than one email to google per connection;  Thank you in advance for your help. -sashk