I don't think that I would move to a service that didn't do SPF, DKIM and DMARC. What I would do is keep your MX pointed at ASSP. Configure ASSP to connect to the service (thus putting ASSP and your control in front of the "service" and then point the service to your MailServer.
On Jan 10, 2013, at 2:00 PM, Hill, Brett wrote:
> My company is moving to a 3rd party email archiving service. Our MX
> records will be changed to point to that service. They will run their
> anti-spam checks on incoming email and then pass through the emails that
> pass the checks (sounds like a store and forward type service). Our
> outbound emails also go through them to get to the Internet. They have
> their ways of filtering out spam, but do not support SPF checking as
> part of their anti-spam arsenal and potentially some of the other nifty
> things ASSP 1.9x has. I'm wondering which settings I can change in ASSP
> to allow me to keep using it as an extra layer of defense. Or, is it
> best that I drop ASSP all together? I've been using ASSP since v1.0.12
> (going on 9 years). I've been spoiled, it's a great piece of software!
>
>
> Thanks,
> Brett
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122712
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
|