Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re^2: RFC: Email 2.0: Segmail

by superfrink (Curate)
on Sep 24, 2005 at 17:32 UTC ( [id://494785] : note . print w/replies, xml ) Need Help??


in reply to Re: RFC: Email 2.0: Segmail
in thread RFC: Email 2.0: Segmail

Whatever scheme someone thinks up will have to be adopted by enough domains before it starts to be effective. That doesn't mean it's not a good idea. Just that it's going to take a while so be ready to stick with the project. :)

Recently my domain has been getting bounce messages to non-existant accounts. The reason is that spam is currently being sent with forged From addresses that are just some random name @ mydomain.

I have had SPF setup in my DNS for a while now. I like it because it's pretty simple to setup. I don't have any issues where I try to send from different ISPs when I'm not road, etc.

I have learned that many domains do not use SPF. AOL, Gmail, Hotmail are some that do but many others don't. I've been emailing the whois contacts for each domain that bounces spam to me to tell them about SPF.

(Side note if your WHOIS contact information doesn't work I think you should lose your domain.)

Replies are listed 'Best First'.
Re^3: RFC: Email 2.0: Segmail
by tomazos (Deacon) on Sep 24, 2005 at 18:04 UTC
    That is not true superfrink. The Segmail system works effectively even if only one person takes it up. It is backwards-compatible with current email infrastructure. It does not matter how many other people use it. That is the point.

    -Andrew.


    Andrew Tomazos  |  andrew@tomazos.com  |  www.tomazos.com