[AusNOG] Controlling spam in IaaS environment

[Christian Heinrich]

Daniel,

If you insist on on-prem IaaS then at least configure SPF, DKIM and
DMARC on the mail server but it would be cheaper to implement SendGrid
in the long run.

On Thu, Dec 1, 2016 at 2:17 PM, Daniel Manzau <daniel.manzau at 3ca.com.au> wrote:
> Hi All,
>
>
> We're after a bit of advice as to what general best practice is in stopping
> (failing that, identifying) SPAM in IAAS/Hosting type environments.
>
>
> The way we see it there are two broad methods by which spammers can abuse
> this type of service:
>
>
> 1) Spammer creates a server which they then use a spam source until they get
> shut down and kicked. Let's call this the SPAMY Customer
>
> 2) Spammers exploit a legitimate customers existing server and then use that
> exploit to deliver spam. Let's call this the SPAMY Exploit.
>
>
> There are quite a few strategies that stop the SPAMY Customer, like blocking
> outbound port 25 by default in their service profile. However, these methods
> don't stop the SPAMY Exploit.
>
>
> Is the best approach to cover off both scenarios a commercial
> appliance/service and if so, does anyone have any recommendation on a good
> value service provider solution for an IaaS type offering?
>
>
> Thanks
> Daniel
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>



-- 
Regards,
Christian Heinrich

http://cmlh.id.au/contact