Hi Users, I'm hoping this is an obvious fix, but I don't have too much experience with Postfix so before I change something, I want to ask the experts.
I am receiving a SOFTBOUNCE status in my Postfix logs: Aug 10 08:21:22 MyServer postfix/local[28836]: 51FA9285F85: to=<jenkins-mybuild@MyServer>, relay=local, delay=248145, delays=248144/0.01/0/0.24, dsn=4.3.0, status=SOFTBOUNCE (Command died with status 3: "/usr/bin/wget -o /dev/null http://myserver:8080/job/mytest/build";) I have a Jenkins CI software instance running on the same server as Postfix. I want to "send Jenkins an email" when I want the build to fire, and it works beautifully. The build fires, no problem. The issue, I presume, is that the SOFTBOUNCE causes Postfix to attempt to deliver the message every hour and then five minutes after that, so now my build is running every hour and every sixty-five minutes. The message states "Command died with status 3" but when I run the command manually, I receive no sign of failure and the build is kicked off as it should. My alias is defined as: jenkins-mybuild: "|/usr/bin/wget -o /dev/null http://myserver:8080/job/mytest/build"; My postconf -n output is: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no config_directory = /etc/postfix default_destination_concurrency_limit = 5 inet_interfaces = 10.7.7.11,127.0.0.1 mailbox_size_limit = 0 mydestination = myserver, localhost.localdomain, localhost, myserver.mydomain.com myhostname = myserver mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128, 10.7.7.0/24 myorigin = /etc/mailname readme_directory = no recipient_delimiter = + relay_destination_concurrency_limit = 1 relayhost = [smtp.gmail.com]:587 smtp_connection_cache_destinations = smtp.gmail.com smtp_enforce_tls = yes smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_security_options = noanonymous smtp_sasl_tls_security_options = noanonymous smtp_tls_CAfile = /etc/postfix/cacert.pem smtp_tls_enforce_peername = no smtp_tls_note_starttls_offer = yes smtp_tls_scert_verifydepth = 5 smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) smtpd_tls_ask_ccert = yes smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_req_ccert = no smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes soft_bounce = yes Questions: 1.) What is a SOFTBOUNCE? (http://en.wikipedia.org/wiki/Soft_bounce doesn't help, I understand what a bounce is, but if it's a bounce, why is Jenkins being triggered?) 2.) How can I stop this from happening (the server re-trying every hour to resend the message) as a short-term fix? And, 3.) What is the long-term solution that will allow me to have aliases that call the "curl" directive and not produce a SOFTBOUNCE? I'm sending the message to jenkins-mybuild@myserver, not myserver.com, because I'm only sending with machines that are local to the Postfix server (for now) and the messages are being delivered to Postfix just fine. I don't see that as being my problem, directly. Perhaps the fact that it can't do a lookup on the domain causes a SOFTBOUNCE but I don't want it to perform that lookup if the recipient matches the alias. I also see in the config the "soft_bounce" flag, but I'm not sure what the implications are of saying "no" Thanks for your time. Pete
