> The idea is so simple, that it is possible, that some others > have had it before. This does not matter - I have some less > to do (the DRAFT) - but it works great in ASSP.
Just to wipe some "fog" :) When sending a message through an FBMTV enabled ASSP the latter will retrieve the original message ID for the message and prepend a unique signature to it; so, for example having a message with a Message-ID header like 001501ca62d6$915c7740$213fd...@example.com and sending it through ASSP, the message ID, after ASSP FBMTV processing may become sig.1566bcf893.001501ca62d6$915c7740$213fd...@example.com notice the "sig.xxxxx.<original-message-id>" at this point, since the Message-ID isn't "mangled" by other servers when someone will reply to your message, ASSP will check the incoming Message-ID for a valid (and own) FBMTV signature and will strip it off, so the message ID will become (again) 001501ca62d6$915c7740$213fd...@example.com by the way, in case of bounces, if the bounce is "valid" that is generated by a message with a valid FBMTV tag, it will pass otherwise, missing the tag in the signature the message will be considered an "invalid bounce" and will be rejected The beauty of this approach is that it doesn't mangle the sender email address (as BATV does) so it eases dealing with email addresses whitelists and so on while, at the same time, retaining the same efficiency of BATV (ok, probably a better efficiency :D) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
