The VERP address actually decodes to binary, and not a correct email

address. Is there a log somewhere where I can find out what the real

original VERP address was? Does Mercury figure these things out on its

own?

The original message has these data in the  Errors-to: line and if you are archiving all of your mail this line will be the original RCPT TO: address.  In addition, the MercuryE/C log will also show this address as originally sent.  Should be able to do a case insensitive string search to match the lower case string to a U/L case string.

Does Mercury figure these things out on its

own?

I do not know but if you are blocking the bad addresses you'll know soon enough if it does.  ;-)

Based on my assumption about the construction of VERP addresses, it would seem to me that mail servers which force lower-case addresses are going to be problematic.

For example, I'm watching our Mercury server blast through a 1000-member mailing, and the SMTP module is logging a few bounces. Some of the replies are coming from mail servers which seem to "lower case" the entire header.

Example:

T 20090317 125146 49bf9985 helo gateway.bouncedomain.com
T 20090317 125146 49bf9985 mail from:<postmaster@gateway.bouncedomain.com>
T 20090317 125146 49bf9985 rcpt to:<verp.zhbsaxrazgf2zw5wb3j0bglicmfyes5jb20=.102@envisionware.com>

The VERP address actually decodes to binary, and not a correct email address. Is there a log somewhere where I can find out what the real original VERP address was? Does Mercury figure these things out on its own?