SoylentNews is people
SoylentNews
from the And-nothing-of-value-was-lost dept.
lhsi writes:
"The BBC is reporting that starting in early March, Facebook is ending its @facebook.com e-mail system, due to a lack of use. E-mails sent to a users @facebook.com address will now be 'forwarded to the personal email address from which the member signed up for the site'.
If this is the e-mail address that is the personalised user URL followed by @facebook.com, does that mean that users will potentially be exposed to e-mail spam through it? The @facebook.com e-mails can be pieced together easily enough (and go to an 'Other' folder in the Facebook Messages area without notifying users so can currently be ignored), but actual e-mail addresses, including ones that could now have e-mails forwarded to, can be kept private. There is little information about this at the moment, even on the Facebook newsroom."
(Score: 5, Interesting) by Sir Garlon on Wednesday February 26 2014, @01:57PM
When it comes to receiving mail, I agree with you. However, I was running a nonprofit web site back around 2004-2005 and it had an old-school mailto: link to contact the administrator. Spammers apparently started using that address in their forged sender headers. The domain got added to blacklists and before I knew it, mail sent to that domain wasn't getting delivered. I never did go to the hassle of trying to get it un-blacklisted even though I still control the domain.
So I would say it is fine to have a gmail.com or comcast.net address that is public, but if you have your own domain, you might want to be a little circumspect about making a live email address public.
[Sir Garlon] is the marvellest knight that is now living, for he destroyeth many good knights, for he goeth invisible.
(Score: 3, Interesting) by mechanicjay on Wednesday February 26 2014, @04:08PM
Mail filtering and spam detection has gotten far more sophisticated in the last 10 years. Pretty much no-one trusts the from headers for anything. It's as good as a return address label on piece of physical mail. At this point trust is established at the server level through trusted and authenticated relays, and source is determined the envelope/received headers which points back to the actual origin of the message.
The only time I've ever had a mail server black listed is due to a compromised account, which was being used to spew spam out as fast as the solaris box could pump it out or when it was mis-configured as an open-relay with similar results. That *server* became blacklisted, but not the domain as whole.
I've been running my own mail server and domain for over 10 years, and have never had a blacklisting issue.
My VMS box beat up your Windows box.