GMail now using DomainKeys
Posted by Michael Stanclift on 18 October 2004 - 07:00 · 22 comments & 2691 views
About the Author
Full name: Michael Stanclift
Forum name: Marshalus
Contact: via forum PM
Submissions: Normal · Headline
Full name: Michael Stanclift
Forum name: Marshalus
Contact: via forum PM
Submissions: Normal · Headline
Slashdot It!
Submit to reddit
Submit to blinklist
Bookmark on del.icio.us
Add to furl
Share on Facebook
Add to Windows Live
Add to Google- Advertisement
-
-
#1 Posted by maulia on 18 Oct 2004 - 07:02
- Is there a simplified-version of the explanation on how this technology can actually reduce SPAM?
-
#2 Posted by eckocx on 18 Oct 2004 - 07:09
- No more spam YAY o/
-
#3 Posted by Sn1p3t on 18 Oct 2004 - 07:09
- Another contender for Sender-ID.
Hopefully they can work together, or everyone moves to one standard.
-
#4 Posted by maiios on 18 Oct 2004 - 07:10
- Finally something other than Microsofts standard. Maybe this one will be more widely adopted.
-
(2 replies)
#5 Posted by Ideas Man on 18 Oct 2004 - 07:12
- Just because Microsoft did it, doesn't auotmatically mean it's crap, doesn't work or anything like that, take Outlook 2003's spam filter, it's excellent. Maybe the Microsoft solution is better, but we won't know for a while because some fags decided against it, they feel that helping themselves is better than helping the world.
-
#5.1 Posted by Sn1p3t on 18 Oct 2004 - 07:17
- I agree with you. The only problem with Sender-ID is that it conflicts with the GPL. If that is changed, then you'll see a lot more ISPs going to it. It remains to be seen what Microsoft will do.
-
#5.2 Posted by tapo on 18 Oct 2004 - 16:14
- The problem with SenderID:
1. Microsoft has a patent on it, thus making it conflict with the GPL. This also causes the problem that Microsoft can ask for royalties at any time. People do not like patented "standards". See here for Debian's take on the issue: http://www.debian.org/News/2004/20040904
2. Sender Policy Framework (SPF) by Pobox.com is already widely adopted, works just as well and does not have a patent on it.
3. SenderID is based off of SPF, and does not seem to offer any major advantage over it.
-
(4 replies)
#6 Posted by martijn on 18 Oct 2004 - 07:16
- News source is obviously slashdot (first paragraph), why not name it?
-
#6.2 Posted by Marshalus on 18 Oct 2004 - 07:34
- Uh maybe because I didn't look at Slashdot. And it isn't from SD, it's from a blog.
I messed up on the links, now fixed. -
#6.4 Posted by Danigoldman on 19 Oct 2004 - 14:14
- News source is obviously slashdot (first paragraph), why not name it?
Actually Netwizard was the one who submitted this story to slashdot.
-
#7 Posted by tiwaris on 18 Oct 2004 - 08:34
- Google is definitly the leader.
-
#8 Posted by lil_psc on 18 Oct 2004 - 08:44
- jus to show how far google is ahead on web technology
-
(1 reply)
#9 Posted by WindowsNT on 18 Oct 2004 - 09:05
- I run my own e-mail server using MS Exchange. downloads mail from my domain providers POP3 server and ssends via the Windows/Exchange SMTP Server.
I wonder how i can impliment somthing like this in the the future as this is the way e-mail is heading. -
#9.1 Posted by Magallanes on 18 Oct 2004 - 11:11
- for free?
no way.
-
(1 reply)
#10 Posted by koocha on 18 Oct 2004 - 11:24
- I'd still like a gmail invitation if someone has one spare. Please?
-
#11 Posted by memNOC on 18 Oct 2004 - 12:28
- leave it to Google to finally do some thinking about this, and take a smart approach towards fighting spam.
they have some insanely creative people there. they're surely the company to watch out for (as it hasn't been obvious for some time now).
-
(1 reply)
#12 Posted by moua on 18 Oct 2004 - 14:48
- >nslookup
>set q=txt
>gmail.com
gmail.com text =
"v=spf1 a:mproxy.gmail.com a:rproxy.gmail.com ?all"
-
#13 Posted by Jugalator on 18 Oct 2004 - 16:32
- A great part about this is that the original sender is preserved even when forwarding the mail, which it weren't with that SPF suggestion that was turned down.
According to a post at IETF's MAIL-SIG list by John Levine; Google has begun to sign outgoing email from Gmail with Yahoo's DomainKeys signatures. This is the first large provider of email that is actually doing so (not even Yahoo has started that yet).
DomainKeys is a technology for verifying both the domain of each email sender and the integrity of the messages sent (i.e,. that they were not altered during transit). And, once the domain can be verified, it can be compared to the domain used by the sender in the From: field of the message to detect forgeries. If it's a forgery, then it's spam or fraud, and it can be dropped without impact to the user. If it's not a forgery, then the domain is known, and a persistent reputation profile can be established for that sending domain that can be tied into anti-spam policy systems, shared between service providers, and even exposed to the user.
It should be interesting to see how other providers will react. Gmail helped rework the standard Inbox size with 1GB of storage. Perhaps they'll provide a jump start to other providers to adopt similar efforts to cut down on SPAM.
The e-mail appears in your normal Inbox folder, and the file is attached as an e-mail attachment. GMail Drive periodically checks your mail account (using the GMail search function) to see if new files have arrived and to rebuild the directory structures.
But basically GMail Drive acts as any other hard-drive installed on your computer.
You can copy files to and from the GMail Drive folder simply by using drag'n'drop like you're used to with the normal Explorer folders.
Because the GMail files will clutter up your Inbox folder, you may wish to create a filter in GMail to automatically move the files (prefixed with the GMAILFS letters) to your archived mail folder.
Please note that GMail Drive is still an experimental tool. There's still a number of limitations of the file-system (such as total filename size must be less than 40 characters), and it doesn't make full use of the secure internet protocols available.