Alexandre Laroche

@avoidik : Can you draw your Exchange architecture (Edge and Hub server, spam filtring, etc.) and what your email traffic is configure to do (who reveice from external, from internal,...

The real problem isn't the incoming or outgoing emails. A email server just forward email if it isn't the final destination. The problem is that permit sender isn't correctly manage...

Powershell : ``` # Don't receive from anonymous if it's an authoritative domain Get-ReceiveConnector “My Internet ReceiveConnector” | Get-ADPermission -user “NT AUTHORITY\Anonymous Logon” | where {$_.ExtendedRights -like “ms-exch-smtp-accept-authoritative-domain-sender”} | Remove-ADPermission...

@Pro : The DKIM agent should sign ALL emails that the routing service receive. The routing service use Outgoing connectors. His job is to take the message and send it...

@Pro: Just remove the right (access) to receive email from anonymous to your external connector for your authoritative domains (domains, you have configure in exchange). It's the job of the...

@ablanken : Your concern can be address in the follow ways : Create a account in your Exchange environnement and grant appropriate rights. For external email filtering services (Gapps, Exchange...

http://www.codeproject.com/Articles/3781/Test-Driven-Development-in-NET

We should start by implement test on each function. After that to implement tests on the whole application. If some class depend on other we should use mock as decribe...

I don't agree with you that implement DomainKeys isn't worth the time. I already know that DKIM is the successor of DomainKeys. Unfortunately, DomainKeys is still use in some anti-spam...

The proposed solution for the app.config is very great. It's a great idea to activate DKIM and DomainKeys by domain. It's also add the possibility to disable a domain configuration....