Deb
01-20-2006, 02:04 PM
Due to the way RBLs (realtime blackhole lists) and other large networks are blocking IPs to prevent spam, the most compelling of which being issues with AOL as noted in this thread (http://www.aota.net/forums/showthread.php?t=20784), FutureQuest has moved the handling of ezmlm-idx generated email back to the Community Servers.
This change enables RBLs to list/block the IP of the specific account that generated the messages rather than the IPs of the entire server that sends out high volume mail for a large number of clients. E.g. when a client sends a large amount of mailing list messages to AOL users, and providing AOL chooses to blacklist that sender, AOL will now blacklist the IP of that client's sending domain rather than the IP of FutureQuest's entire high volume mail server.
This change also enables individual site owners to request whitelisting from AOL (http://postmaster.aol.com/tools/whitelist_guides.html), if needed. However, you should note that choosing to do so, and the responsibility of maintaining such an agreement would be between you and AOL. FutureQuest in no way accepts any responsibility in the area of advising for, against, or supporting such an agreement.
Important Note:
It is the responsibility of the site owners, that choose to send email to any other network (e.g. another host, AOL, Hotmail, etc) to ensure that their messages do not break any of the rules of the receiving network. The blocking of a single IP by another provider will require the site owner using that IP to take any action possible to remove that block.
For those that remember why ezmlm-idx bulk email messages were moved to high volume mail servers, and are concerned about email issues as a result of moving ezmlm-idx handling back to the community servers, there have been a few important changes since that time. Of note:
1: Qmail now uses the domain's assigned IP for sending email. This means all email from any single domain, including messages sent with ezmlm-idx, show that domain's IP address as opposed to the community server's IP address.
2: All ezmlm-idx mailing list messages will still be handled in a completely separate email queue. This prevents any potential backlog of ezmlm-idx bulk mailings from affecting normal email delivery.
3: FutureQuest has made many advances and improvements within the Qmail delivery process and those optimizations have made the processing of bulk email handling more resource friendly in a community server environment.
For the record, FutureQuest still feels that having ezmlm-idx email handled on servers separated from the community servers is the superior solution. Nevertheless, we have been forced to restructure how Qmail delivers mailing lists to satisfy the demands of the much harsher spam fighting tactics created by larger providers. By making this change we have greatly decreased the risk of having your mailings blacklisted due to the mailing habits of another client.
FutureQuest, Inc.
http://www.FutureQuest.net
This change enables RBLs to list/block the IP of the specific account that generated the messages rather than the IPs of the entire server that sends out high volume mail for a large number of clients. E.g. when a client sends a large amount of mailing list messages to AOL users, and providing AOL chooses to blacklist that sender, AOL will now blacklist the IP of that client's sending domain rather than the IP of FutureQuest's entire high volume mail server.
This change also enables individual site owners to request whitelisting from AOL (http://postmaster.aol.com/tools/whitelist_guides.html), if needed. However, you should note that choosing to do so, and the responsibility of maintaining such an agreement would be between you and AOL. FutureQuest in no way accepts any responsibility in the area of advising for, against, or supporting such an agreement.
Important Note:
It is the responsibility of the site owners, that choose to send email to any other network (e.g. another host, AOL, Hotmail, etc) to ensure that their messages do not break any of the rules of the receiving network. The blocking of a single IP by another provider will require the site owner using that IP to take any action possible to remove that block.
For those that remember why ezmlm-idx bulk email messages were moved to high volume mail servers, and are concerned about email issues as a result of moving ezmlm-idx handling back to the community servers, there have been a few important changes since that time. Of note:
1: Qmail now uses the domain's assigned IP for sending email. This means all email from any single domain, including messages sent with ezmlm-idx, show that domain's IP address as opposed to the community server's IP address.
2: All ezmlm-idx mailing list messages will still be handled in a completely separate email queue. This prevents any potential backlog of ezmlm-idx bulk mailings from affecting normal email delivery.
3: FutureQuest has made many advances and improvements within the Qmail delivery process and those optimizations have made the processing of bulk email handling more resource friendly in a community server environment.
For the record, FutureQuest still feels that having ezmlm-idx email handled on servers separated from the community servers is the superior solution. Nevertheless, we have been forced to restructure how Qmail delivers mailing lists to satisfy the demands of the much harsher spam fighting tactics created by larger providers. By making this change we have greatly decreased the risk of having your mailings blacklisted due to the mailing habits of another client.
FutureQuest, Inc.
http://www.FutureQuest.net