ADMIN FAQ
IIS and ListManager
IIS frequently binds to all IP addresses on a machine by default, even when configured not to do so. Users who want the ListManager web server to coexist with IIS will need to configure IIS so it does not bind to all IP addresses on the machine. See the following
Microsoft IIS related links:
IIS binds to all IP addresses: http://support.microsoft.com/?kbid=259349
Disabling socket pooling: http://support.microsoft.com/kb/238131/EN-US/
Disabling socket pooling for IIS SMTP service: http://support.microsoft.com/?kbid=281760
Metabase method for disabling socket pooling has no effect: http://support.microsoft.com/default.aspx?scid=kb;EN-US;813368
Whitelist Complaint Handling
In an effort to fight spam while delivering opt-in messages, many email providers have implemented whitelists, or lists of senders who have agreed to their whitelist guidelines to ensure they will not be automatically filtered as spam. Typically, the organization wanting to be whitelisted must sign an agreement to remove subscribers who identify the sender's mail as spam and to set up a feedback loop.
The email provider then emails information about the complaint to the sender, so the recipient may be removed.
ListManager can automate the handling of these messages so that complaint notifications sent by the email provider to the specified address will:
Automatically delete any active mailings for the member
Unsubscribe the member
Ban that member from the list, so the member may not be re-added
Log the complaint, viewable in Reports: Members: Member Complaints and recorded in the lyrMemberComplaintLog table.
To create the feedback loop email address
The server administrator must create an autoresponder that processes the message as a complaint, and then inform the email provider that all complaints must be sent to that address.
Lyris, Inc. | 6401 Hollis Street, Suite 125 | Emeryville CA 94608 USA |
www.lyris.com
Toll free +1.800.768.2929 | International calls +1.510.844.1600å | Fax +1.510.844.1598
Page 857
