Best anti-spam program (imo) out there...
I most heartily disagree. I do not recommend it, and will never recommend
it, so long as the following prevails (taken from the site that you
linked):
| Q. What does the 'Enable bouncing of messages from this account' mean?
|
| A. If you don't want to use the bounce feature, you can disable it by
| unticking this box for each account. It is ticked to bounce by default.
Mr. Bolton needs to completely remove this abominable "bounce" feature,
which doesn't work, anyway. For one thing, using bounce violates most ISP
terms of service. Here is an actual MW bounce that I received from an
actual MW user; bouncing to an email address forged as the sender; the
spammer who sent the bounced message did not get it, but I did!
| Received: from 216.77.233.62 (HELO bellsouth.net) (216.77.233.62)
| by mta124.mail.scd.yahoo.com with SMTP; 11 Jun 2003 22:31:24 -0700 (PDT)
| Date: Thu, 12 Jun 2003 01:34:10 -0500
| From: Mail Delivery Subsystem <
[email protected]>
Notice that this was supposedly sent by "(e-mail address removed)"; but
was it? Really? Using Sam Spade on the source IP address:
| 10/25/05 22:59:28 dns 216.77.233.62
| nslookup 216.77.233.62
| Canonical name: adsl-77-233-62.rmo.bellsouth.net
| Addresses:
| 216.77.233.62
Not a Bellsouth SMTP server, as one would expect of a proper bounce, but an
ADSL customer. Just like I am an SBC Yahoo! DSL Service customer. This
bounce is clearly a forgery. Now, I actually sent the MW user an email, to
her supposedly non-existent email address, which the Bellsough MX accepted
(which BS MX servers don't do with non-existent email addresses!)
explaining the Bellsouth AUP/TOS to her. Bellsouth, SBC-Y, and even
Rogers-Y, have prohibitions against impersonating ISP officials; and
<
[email protected]>, or even <
[email protected]>, are ISP
officials. Now looking at your posting headers, I see this:
| NNTP-Posting-Host: cpe0011d8264165-cm0014e8b57082.cpe.net.cable.rogers.com 24.43.46.70
Sam Spade tells me this:
| 10/25/05 23:04:05 dns 24.43.46.70
| nslookup 24.43.46.70
| Canonical name: CPE0011d8264165-CM0014e8b57082.cpe.net.cable.rogers.com
| Addresses:
| 24.43.46.70
Not a Rogers SMTP server; the "cpe" in the rDNS name means, "Customer
Premises Equipment"; IOW, your cable modem.
Now, since you are posting from Rogers netspace, let us take a look here:
http://na.edit.client.yahoo.com/rogers/show_static?.form=eua
I see this:
| 4. | Use of the Services. Your use of the Services must comply with this Agreement,
| all applicable laws and all Rogers and Yahoo! policies. Without limitation,
| you may not use the Services (including the Equipment) to directly or indirectly:
|
| 1. ...
| 2. ...
| 12. impersonate any person or entity, including, but not limited to, a Rogers or
| Yahoo! official, forum leader, guide or host, or falsely state or otherwise
| misrepresent your affiliation with a person or entity;
The MailWasher bounce feature {spit} is on by default, and it does exactly
what Rogers prohibits. Now, what do you think will happen when somebody
like me comes along and sends a complaint to "abuse (at) rogers (dot) com",
as shown in the Sam Spade "whois" lookup for IP address 24.43.46.70. Or any
other ISP that I would report for abuse, for that matter. Have you ever
received a "TOS Notice" from your ISP? Do you want to receive a "TOS
Notice" from your ISP?
Definitely do not use the MailWasher bounce feature. Ever. But, until Mr.
Bolton removes that option completely, I just can't recommend the product.
Use something else; anything else.
SpamGourmet
SpamAssassin
POPFile
K9
Do not use MailWasher.
BTW, cross-posting to five disparate groups is abusive in its own right.
Because the sole group with any relevance at all to this application is the
MS Outlook Express group, I will do what you did not; set the
"Followup-To:" to put replies to my post in that group. Beyond that, I
going, just this once, ignore my news client warning about excessive
cross-posting. It would be far more appropriate to offer this kind of
information, bad as it is, in response to specific queries, in the group in
which the query was posted.