Precedence: header in email -


my web application sends email often, , sends 3 kinds of emails: initiated user, in response event in system, , in automatic response email received application.

i make sure third type of email not stuck in endless loop of auto-responders talking each other. currently, use header:

precedence: junk 

but yahoo! mail treating these messages spam. not ideal, because read our auto-response , make decision on it, not out-of-office reply.

what best way send email without triggering either junk filters or auto-responders?

precedence: junk?  precedence: bulk?  precedence: list?  x-priority: 2? 

rfc 2076 discourages use of precedence header. have noted, many clients filter off (especially precedence: junk variety). may better use null path avoid auto responder wars:

return-path: <> 

ultimately use priority try around this, seems going against spirit of header. i'd suggest using return-path header this, , avoiding precedence. in cases may have write in way drop auto-responders in application (to avoid getting responder war), can't remember situation in happened using appropriate return-path. (most auto responder wars recall having deal result of badly formed emails)

note: return-path header is, in short, destination notifications (bounces, delay delivery, etc...), , described in rfc 2821 -- because it's required smtp. it's 1 method drop bad mail (as theoretically mail set appropriate return-path).


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -