Post by RetirednoguiltPost by Cosmo KramerPost by FrankMrs Frank has been getting emails with Comcast address to do something
" ---------- Original Message ----------
Date: 08/28/2024 12:14 PM EDT
Subject: Synchronize Your Mail service
Dear User,
We recently changed our service network. Due to your service newtork we
will like you to comply to the new terms and agreement to avoid closure
of account.
ACCEPT AND AGREE"
I told her it was probably fake but she had to call Comcast to get it
from them.
The best antispam method I've found is to use an email address that is
extremely difficult for the spammers and scammers to guess.
I got the same e-mail recently. The give-away for me was that it landed
in the inbox of an e-mail account I'd never provided to Comcast. I
expect them to contact me in keeping with the contact information I've
provided to them in my profile.
The sender of an e-mail can put whatever they want in the To header.
That is a client-added header. When the client sends an e-mail, it
builds an aggregate list of recipients from the To, CC, and BCC headers
to use in a list of RCPT-TO commands it sends to the server. However,
spammers will use clients that compile whatever RCPT-TO commands the
spammer wants without regard to what are in the To, CC, and BCC fields.
Some (few) e-mail providers will check the From header in a sent e-mail
matches on the account through which the e-mail gets sent. Spammers
don't use those since they want to hide. No SMTP server validates the
list of RCPT-TO commands it received from the client matches on the To,
CC, and BCC headers which were added by the client, and sent within the
DATA command.
For example, a spammer could specify just 1 recipient in the To header,
but their client could issue umpteen RCPT-TO to a slew of recipients.
None of the recipients will see the list of RCPT-TO commands the sending
server got from the client, so the recipient doesn't know to how many
recipients a message was received. The recipient may not even be
specified in the To or CC headers the recipient sees. E-mail was built
on a trust model, and why it is easily abused.