full-disclosure - Implications of outsourcing email

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <ad.3711c089.2d0632b7@aol.com>
From: MaxPageant at aol.com (MaxPageant@....com)
Subject: Implications of outsourcing email

Check out response.microsoft.com identifying Postfuture (www.postfuture.com) 
as the company sending transactional emails (order receipts, .NET 
confirmations) for Microsoft.

Don't know if you all know how MX records work in email, but it's possible 
for an email service provider to configure their mail server to send emails 
through their client's domain.  This makes emails you receive look like they came 
directly from the company/brand rather than their outsourcing email vendor. 
The benefit for all of us for this is it helps to authenticate opt-in messages 
as coming from the sending company rather than a fraudulent spammer trying to 
get your email.

Question: Why don't more companies do this to authenticate their commercial 
opt-in email????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20031208/866cd382/attachment.html