Email Authentication: Difference between revisions
No edit summary |
mNo edit summary |
||
Line 7: | Line 7: | ||
{| border="1" | {| border="1" | ||
|+ | |+ Major US Commercial Banks | ||
! Name !! Has an SPF record | ! Name !! Has an SPF record | ||
|- | |- | ||
Line 38: | Line 38: | ||
|} | |} | ||
{| border="1" | {| border="1" | ||
|+ Australian Commercial Banks | |+ Major Australian Commercial Banks | ||
! Name !! Has an SPF record | ! Name !! Has an SPF record | ||
|- | |- | ||
Line 64: | Line 64: | ||
|bgcolor="red"| No | |bgcolor="red"| No | ||
|} | |} | ||
Here's some tech companies I decided to take a look at. | |||
{| border="1" | |||
|+ Select 'technology' companies | |||
! Name !! Has an SPF record | |||
|- | |||
| [http://www.apple.com Apple] | |||
|bgcolor="green"| Yes | |||
|- | |||
| [http://yahoo.com Yahoo!] | |||
|bgcolor="red"| No | |||
|- | |||
| [http://google.com Google] | |||
|bgcolor="green"| Yes | |||
|- | |||
| [http://thoughtworks.com ThoughtWorks] | |||
|bgcolor="red"| No | |||
|- | |||
| [http://microsoft.com Microsoft] | |||
|bgcolor="green"| Yes | |||
|- | |||
| [http://www.messagelabs.com Message Labs] | |||
|bgcolor="red"| No | |||
|- | |||
| [http://oreilly.com O'Reilly Media] | |||
|bgcolor="green"| Yes | |||
|- | |||
| [http://ibm.com IBM] | |||
|bgcolor="green"| Yes | |||
|- | |||
| [http://accenture.com Accenture] | |||
|bgcolor="green"| Yes | |||
|- | |||
| [http://www.eds.com Electronic Data Systems] | |||
|bgcolor="red"| No | |||
|- | |||
|} | |||
== References == | |||
# http://uhaweb.hartford.edu/COHN/largest_commercial_banks.htm | |||
# http://mxtoolbox.com/spf.aspx |
Revision as of 05:29, 13 July 2007
The battle against email spam has long been an interest of mine. Recently, I've had a couple of situations making me look into the current state of spam detection and avoidance. Specifially:
- ThoughtWorks contracted MessageLabs to filter all inbound email. More and more companies are setting up spam filters, but fewer companies and looking into how to prevent their own email from getting filtered.
- A new project at an Australian Bank is sending email to clients. Nothing has been done to see how we can send email and help reduce phishing, or how customers can verify that an email was actually send by the bank.
There are several technologies which help spam filters fitler spam. This includes DomainsKeys, SPF, and SenderID. SPF is probably the easiest to implement, so I thought I'd check to see which major banks are using it. Here's the results:
Name | Has an SPF record |
---|---|
Bank of America Corp. | Yes |
Citigroup | Yes |
Chase | Yes |
National City Corp | No |
JPMorgan | Yes |
Wachovia | Yes |
Wells Fargo | Yes |
US Bank | Yes |
SunTrust Banks | No |
Name | Has an SPF record |
---|---|
ANZ | No |
Commonwealth Bank | No |
HSBC Australia | Yes |
Macquarie | No |
National Australia Bank | No |
WestPac | No |
St. George | No |
Here's some tech companies I decided to take a look at.
Name | Has an SPF record |
---|---|
Apple | Yes |
Yahoo! | No |
Yes | |
ThoughtWorks | No |
Microsoft | Yes |
Message Labs | No |
O'Reilly Media | Yes |
IBM | Yes |
Accenture | Yes |
Electronic Data Systems | No |