The reason I would think it makes more sense there is determining the
direction of it. But to be honest thinking about it some more it may be
as a rule we would just need a way to determine directionality since we
may want to have a way to cross domain boundries with the messages,
maybe having it defined where we accept messages to be sent on second
thought may make more sense since the message is going out and we are
trying to change an outbound message.
allow DSN full for table accepted_domains for relay
allow DSN Headers-Only for relay
On 03/03/14 11:35, Gilles Chehade wrote:
On Mon, Mar 03, 2014 at 11:32:44AM -0800, Jason Barbier wrote:
Well yeah it would be somthing simple like that I think it would
make more sense on listen to be honest so
Listen on egress DSN {Full, Reject, Header-only, Disable}
Full is full messages with headers and the like
Reject would make the connector reject anything that gets bounced or
requires a DSN
Header-Only would make it just bounce the headers back with whatever DSN
Disable would turn DSN off all together.
with the default being Header-Only
why do you think it makes more sense on a listener than on a rule ?
On 03/03/14 11:23, Gilles Chehade wrote:
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
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
