> Except for list mail. With list mail, my custom Declude header shows > "X-CUSTOM-TO = [EMAIL PROTECTED]"
That's because Declude is scanning the message on the way in to IMAILSRV, i.e. before the list explosion. And wisely so, since otherwise each identical list chunk would be scanned separately. I'm not aware of a workaround for the order-of-operations part of the problem. But even if you did get around this part, inserting a per-recipient header would itself be impossible without compromising list security, as each user in a list chunk would be able to see all the other addresses in that chunk. --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc. e-mail: [EMAIL PROTECTED] SpamAssassin plugs into Declude! http://www.mailmage.com/products/software/freeutils/SPAMC32/download/release/ Defuse Dictionary Attacks: Turn Exchange Addresses into IMail Aliases! http://www.mailmage.com/products/software/freeutils/exchange2aliases/download/release/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
