On Mon, Mar 03, 2014 at 09:47:06AM -0800, Jason Barbier wrote: > > [...] > > by default. Honestly users should beable to turn this on and off > based on the direction of the mail. internally it is useful to have > it spit back the message, headers, and the raw error that the MTA > returned. Externally we should just spit back at most headers but > honestly what is internal and external needs to be set by the user > since there is no good way to determine this on its own and the MTA > honestly should handle this all as part of doing the bounce. It > makes no sense to make a filter or have a second function handle it > since we already have a function to handle bounces. >
imo we don't want to have smart decisions, it has to be explicitely requested no matter what. we could for instance have a default of only bouncing back headers, then either: listen on egress bounce-content (just an example) or: accept [...] bounce-content (another example i don't like the name) but keep in mind that if we go the knob way, then we have to make sure it is done right, we have other bounce related stuff that will want to got the knob way too and we may want to factor -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
