"Rocky" wrote:
> It has been a long time since I've received a legitimate e-mail with
> one of my yahoo e-mail addresses.
So if all e-mails are spam through your Yahoo accounts, why do you still
have them? Why are you spewing out your Yahoo e-mail address to
everyone that asks?
If you want to keep the Yahoo accounts but just keep them in reserve and
not use them then don't poll them to get that spam through them.
However, a free Yahoo Mail account will expire if left idle.
Configuring it to forward e-mails doesn't alter the account being idle.
Idle is measured as to how long between logins. You need to login once
in awhile to keep the free account from expiring. But that doesn't mean
you have to accept any e-mails at that account. Define a filter that
looks for some string being absent in the Subject header and deletes an
e-mail. Then define another filter that looks for the string to be in
the Subject header and, if present, deletes the e-mail. Either the
string will or won't be in the Subject, no other choices, so one of the
filters will fire to delete the received e-mail. Deleted items get
purged about once a week so your account won't fill up (but then you
don't care since you're not actually using the account).
Learn to use aliases (not forwarding services) to hide your true e-mail
address. You can start by reading around at
spamgourmet.com.
Sneakemail is good, too, except they decided to stop providing a limited
free service a few years ago. There's SpamMotel but I don't care for
them. If you have a Yahoo Plus account then you can use it to define
aliases (but there might be limits, like how many you can define whereas
SpamGourmet is unlimited and self-expiring unless you specify
otherwise). Give a self-expiring alias to someone you definitely don't
trust, like someplace that requires you to register to login to get some
coupons you want. Use aliases with just about everyone that asks you
for an e-mail address. Make sure you give a UNIQUE alias to each
recipient so you can track who abuses an alias with spam. You can let
the alias expire, renew it, or kill it if it gets abused. I don't care
how well known is the recipient. It could be IBM, Sears, Intel, or
whomever. First give them an alias. After 6 months, or longer, when
you don't see the alias get abused then decide if you want to update
your account with them to give your true e-mail address. Using aliases
is a lot easier than having to create new temporary free e-mail accounts
at Hotmail, Yahoo, Gmail, or wherever. Plus with SpamGourmet, you can
create them on-the-fly without having to visit your SpamGourmet account
to create them.
> Before, when my e-mail was on AT&T's Server there was a way to return
> an e-mail to all the SPAMERS but I don't see how to do that now.
Yeah. What it did was send your bogus NDR (non-delivery report) to an
innocent the spammer pretended was their e-mail address. Once the
e-mail session between sending and receiving e-mail servers is over,
there is no proof as to the sender. The receiving server knows who
connected to it (the sending server) and can tell it at that time if it
rejects the e-mail. After that, there is NOTHING in the e-mail that
guarantees who was the sender. That means you or your e-mail provider,
after delivery into your mailbox, won't know for sure who sent that
e-mail. You or it relies on fields identifying the sender which the
sender inserted into that e-mail. That's like relying on a con artist
to tell you his real name. Uh huh.
Earthlink had the same bogus bounce feature. I don't know if they still
provide that option since a few of us participants at SpamCop got
Earthlink reported on that blacklist for their deliberately known
misdirected backscatter. As I recall, it had to be enabled by their
customers in their accounts and it was the LAST method used to handle
spam because it was the sloppiest method.
If I ever get your blind and misdirected backscatter (fake bounces), I
will report you to the public blacklists and to your e-mail provider as
a spam source. You and others like you sending fake bounces are as bad
as the spammers (not in volume but in action).
> What I am thinking of doing is forwarding the e-mail to a bogus e-mail
> address and then that should bounce it back too.
Why would you want the bounces to come back to you? If the e-mail
account doesn't exist, and with a properly configuring receiving e-mail
server, it will check if the username has an account with that server.
The receiving mail server will then reject the e-mail transaction. That
means YOUR sending server gets the rejection and YOU will get the NDR.
If the receiving mail server is misconfigured to accept all e-mails and
then, sometime AFTER the e-mail session it had with the sending mail
server, decides if it can deliver the e-mail. If it is then
undeliverable, all it has are the return-path header that the *sender*
put in their e-mail. So the bounce goes back to where the *sender*
claimed was their e-mail address. That's how spammers can use
misconfigured mail servers to bounce their spam from bogus
(non-existent) accounts out to where the spammer claimed was their
e-mail address which is really the secondary victim targeted by the
spammer or simply to another invalid e-mail address so the bounce will
itself get rejected.
Stop trying to generate backscatter. It is considered spam and
reportable to your e-mail provider, to your ISP, and to the public
blacklists for your fake bounces that hit innocents. You obviously
don't know how the e-mail system works. Your fake bounces won't hit any
spammer. Your fake bounces may, though, hit innocents where then *YOU*
are the spammer.
Also of note is that if you ever did manage to hit a spammer, why would
you think that would hurt them? Gee, let's see, they're sending e-mails
to unknown e-mail addresses. They don't know for sure that the e-mail
addresses are valid. But, gee, you're totally willing to tell the
spammer that yours is valid. Which do you think is most important to a
spammer: sending millions of their turds to unknown e-mail addresses or
having those boobs that do get their spam identify to the spammer that
they hit a valid e-mail address? Spammers very much want to get lists
of e-mail addresses that have proven legitimate. And you're going to
help them update their active/valid list. Uh huh, real smart.
Here's a canned reply I wrote up awhile ago:
The bounce feature in any e-mail client is stupid and irresponsible
primarily because ignorant users will actually believe the software
author is providing an appropriate feature and that it will somehow
avoid further spam. Spammers do not use their own e-mail address.
Instead they use a bogus one (which may be a valid e-mail address for
some user) or they use one that they've already stolen and is often
included in the recipient list of e-mail addresses. Spammers change
their e-mails every time they spew so blocking on the one they used last
time won't eliminate getting their crap when they next spew. Spammers
rely on the ignorance of e-mail users that believe using blacklists
and/or bouncing by the sender's claimed e-mail address has any effect on
reducing received spam.
- Blocking by the sender's e-mail will NOT eliminate spam in your
mailbox. The spammer's e-mail address changes at their will.
- Bouncing based on the return-path headers in an e-mail will NEVER hit
the spammer. Only boobs think the spammer will identify themself.
YOU are not connected during the mail session between the sending and
receiving mail servers so you have absolutely no means to guarantee of
knowing from the return-path headers (e.g., From or Reply-To) as to who
sent you a spam mail. The sender can put anything they want in there.
Even mail servers that first accept a message, end the mail session with
the sending mail host, and then check afterward if the e-mail address is
valid or not and then try to send a *new* message back to the sender
will get it wrong. If a valid IP address of the sender is included in a
Received header, that does NOT provide you with an e-mail address to
which you can bounce back their spam. You cannot rely on the
return-path headers to guarantee identifying the true sender. These
bounces are sent blind!
The spammer isn't going to identify themself to receive that bounce. Now
consider that only aren't you the receiving mail server but you are even
further removed from the mail session between the sending and receiving
mail hosts. There is nothing in your e-mail client that can absolutely
guarantee who is the sender of the spam you got in your Inbox, so
bouncing it anywhere means wasting bandwidth for you to send the bounce,
disk space and bandwidtch by your mail server to attempt to deliver your
bounce, disk space and CPU cycles for the receiving mail host to accept
your bogus bounce mail, and some innocent getting slapped with your
misdirected bounce (which, by the way, can be reported to blacklists as
backscatter and get you blacklisted).
Think about it for all of 10 seconds, if even that long. Would you like
to be the victim of a "mail bombing" because some spammer usurped your
e-mail address, sends out a million copies of their crap with you
identified as the sender, and then all those boobs using e-mail clients
with a bounce option end up filling your mailbox with all their
misdirected bounces?
Any e-mail client that provides a bounce option are irresponsible
software authors. Ignorant users sending misdirected bounces are
irresponsible e-mail users. Have a read at:
http://spamlinks.net/prevent-secure-backscatter-fake.htm
http://spamlinks.net/prevent-secure-backscatter.htm
Warning: If you send me backscatter, like misdirected bounces which to
me are unsolicited and hence spam, I will report you to blacklists, like
at SpamCop, for your irresponsible and ignorant use of flawed anti-spam
schemes. If you punish me with your backscatter, I will punish you! I'm
not the only one with this attitude. There are plenty of spam reporters
out there and they will report you, too. It is not up to the rest of us
to placate your sensitivity for your spam problem by being your victim.
Get a responsible anti-spam solution.