>> the problem then is... will the NDR sending MTA keep that header ? >> Or will it just throw away it ? In the latter case the "X-Header" won't >> be of any help; that's why I thought to "mangling" the mail address >> since that one WILL be used to send back the NDR
> A good question. I'm not suggesting that it should block if its missing > - but we should maybe block if its wrong. just to expand the idea a little; you can't be 100% sure the NDR will contain any "useful data"; it may just be a plain vanilla mail message w/o any attachments saying that the email you sent from the address "x" to the mailbox "y" wasn't accepted for whatever reason; in such a case there won't be anything to check/filter; on the other hand, even if the MTA sending back the NDR will send a piece of (or the whole) message attached or embedded, you can't be sure it won't be "mangled" or it will contain the infos you need but let's think about this a little; if brain serves me correctly the MTA uses the mail header infos to send back an NDR and NOT the envelope infos (MAIL FROM/RCPT TO); this means that ASSP may use the "unmangled" address for the envelope and "mangle" the "return-path" header adding the "valid bounce" tag; this way whitelisting (at mailserver level) will stil work and at the same time, any NDR will be sent back to a "tagged" address Again, there's probably more than the above, but if you think to the whole thing by stuffing in something like "address rewriting" (which ASSP can already handle) you'll see that it may be feasible in any case, I think this should be an option and one should be able to enable/disable it at will ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
