|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Setting the sender at SMTP level to <> is not a good idea, as the notifications about invalid email addresses, or rather addresses which were valid but are not valid anymore, will get lost. As there will be no information which addresses got invalid, notifications to those addresses will be sent forever. Some providers tend to mark sending servers as spammers, if they continuously insist to send emails to invalid addresses. This could leave to marking the emails sent from the MTA behind Jenkins to valid addresses as spam, just because the sending server is spamming, according to the rule above.
The header
Auto-Submitted: auto-generated
is enough. The last paragraph of RFC 5230 "Sieve Email Filtering: Vacation Extension", section 4.6. "Restricting Replies to Automated Processes and Mailing Lists" explicitly suppresses sending out-of-office messages to emails containing the above header.