You could probably whip something together with Postfix and Perl or shell.ĭont make these addresses mailboxes on your regular, existing mail server, unless you really know what youre doing. If youve got a unix geek and youre in the right environment for it, set up a separate server just to receive an house these reports. If you send any significant volume (maybe even if not), youll accidentally be telling the world to crush your own mail server with reports. The fields allow you to specify a forensic notification address and aggregate reporting address, respectively.) What Kirill is saying, and rightly so, is dont configure these notification addresses to be mailboxes at your tiny little Exchange server that cant handle any sort of significant email load. The are fields where you specify an address to receive emailed reports relating to DMARC issues. In the DMARC record specification, there are fields called RUF and RUA. You never know whether a receiver out there has a screwy implementation, or some phisher will launch an attack.Ĭonsider hosting these addresses with a third party - try not to DDOS your own corporate email. SendGrids Kirill Popov left a most helpful and timely comment on my previous DMARC record-related post. With multiple big mail services beginning to publish restrictive DMARC policies in 2014, people started to take notice of both DMARC and DKIM in 2015. Of those top five posts, the only one not directly related to DMARC or DKIM still related to something that DMARC and DKIM work together to help address - email forgery.ĭoes that mean 2015 was the year of DMARC Maybe 2016 will end up being the real year of DMARC as more and more mail providers implement a DMARC policy. Lots of folks were curious to learn how Google Groups handled headers in this new world order, after ISPs began to implement preject DMARC policies. I guess Im not the only one who was wondering how to sign mailing list mail with DKIM authentication. I didnt think much about this one at the time, but it makes sense in the context of DMARCs effectively requiring that mailing list mail must be handled differently. It highlighted how bad guys can watch for and purchase recently expired domains and are then practically given the keys to the kingdom when it comes to whatever that domain might have hosted or managed previously, whether it be email users or command and control for a botnet army.īased on page views, heres what was most popular on Spam Resource throughout 2015. I attach, for comparison, the headers of the same letters, but after you correct the problem. Judging by the headlines, the problem that is associated with the mysterious X-Magic about which I couldnt find any information online. Here the official titles of two identical letters sent from one box, but with different clients (Outlook and Thunderbird 2016).
0 kommentar(er)
