Re: Free Newserver?
- From: Blinky the Shark <no.spam@xxxxxxxxxxx>
- Date: 9 Mar 2007 01:28:15 GMT
Paul Johnson wrote:
Crazy Horse wrote:
In article <1qpqkl2x7b8y9.dlg@xxxxxxxxxxxxxxxx>,
cjspambuffer@xxxxxxxxxxx says...
Hiya Boris.
In <news:1173283520.080887.178910@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> you
wrote:
And second, what free newserver would you suggest?http://www.motzarella.org/?language=en
I went to their website and found this under their "Terms of use" page,
in the (first) "Sender Address" section:
---------------------------------
# The e-mail addresses given in "From:", "Reply-To:", and "Sender:"
should be your own and should be valid (= should not bounce because of
invalidity).
# Using addresses and name space of other people without their consent
is prohibited.
# For the From: address the Top Level Domain (TLD) invalid may be used,
as in killefitz@xxxxxxxxxxxxxxxx See also RFC2606 and Usenet Best
Practice.
---------------------------------
Hopefully, I'm misinterpretting this, but it sounds to me like they're
saying I have to choose between, on the one hand, using their service
and publishing my real e-mail address, thereby rendering myself
vulnerable to SPAMmers
No, you aren't misinterpreting it. Munging avoids the problem instead of
effectively dealing with the problem.
The real problem is that your email provider is not giving you enough
control over what gets rejected at SMTP time. All good spam antispam
measures must do a few things to be considered effective in the real
world:
1) Minimize the number of false-positives generated. Any anti-spam
measure is not supposed to treat legitimate email as spam.
2) Minimize the number of false-negatives generated. Any anti-spam
measure is not supposed to treat spam as legitimate email.
3) Never place stumbling blocks in the way of users. No anti-spam
measure should ever require additional effort on the part of the
sender.
Munging email addresses in email and news posts fails on all three
points soundly.
1) Munging considers all email spam regardless of content or source.
2) Munging assumes anybody able to replace an email address is not a
spammer.
3) Munging is a potentially insurmountable stumbling block for end
users, especially if there is no way to unmunge the address in
question.
So, the correct solution to the problem you're trying to solve? Shop for
email service provider that gives you control over what content and
sources you're willing to accept from at SMTP time. Undesirable
content gets rejected at the mail server, you get everything else.
Bullshit. The best solution prevents the bandwidth costs of spam, and
since at least properly configured software won't even *try* to send to
TLD invalid, that's a better solution than begging for spam and then
filtering it once the bandwidth is already wasted. And *bouncing* spam
(which I know you didn't specifically mention) is the worst because it
doubles the wasted bandwidth and and sends mail to innocent pilfered
addresses.
--
Blinky RLU 297263
Killing all posts from Google Groups
The Usenet Improvement Project: http://blinkynet.net/comp/uip5.html
.
- Follow-Ups:
- Re: Free Newserver?
- From: »Q«
- Re: Free Newserver?
- From: Frank Slootweg
- Re: Free Newserver?
- From: Crazy Horse
- Re: Free Newserver?
- From: Gene E . Bloch
- Re: Free Newserver?
- References:
- Free Newserver?
- From: Boris
- Re: Free Newserver?
- From: Ponder
- Re: Free Newserver?
- From: Crazy Horse
- Re: Free Newserver?
- From: Paul Johnson
- Free Newserver?
- Prev by Date: Re: Free Newserver?
- Next by Date: Re: Free Newserver?
- Previous by thread: Re: Free Newserver?
- Next by thread: Re: Free Newserver?
- Index(es):
Relevant Pages
|