Mailing List Archive

Anti-spam policy
Hi,

I see some spam e-mails delivered to my customers via my MX which is a
backup for them... it seems that for some reason, they trust me more than
the average Internet SMTP client.

So I am wondering what should be good practice against spam. Should I:
1) leave it like that and let the customer decide on his anti-spam policy
2) apply some anti-spam on my MX; at the risk of rejecting valid e-mail?

V

PS: hoping there is still somebody listening to this list...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/inet-ops/attachments/20031016/09a6fbbd/attachment.htm
Anti-spam policy [ In reply to ]
On Thursday, October 16, 2003, at 06:39 AM, Vincent De Keyzer wrote:

> Hi,
> ?
> I see some spam e-mails delivered?to my customers via my MX which is a
> backup for them... it seems that for some reason, they trust me more
> than the average Internet SMTP client.
> ?
> So I am wondering what should be good practice against spam. Should I:
> 1) leave it like that and let the customer decide on his anti-spam
> policy
> 2) apply some anti-spam on my MX; at the risk of rejecting valid
> e-mail?
> ?
> V
> ?
> PS: hoping there is still somebody listening to this list...
> ?
> _______________________________________________
> inet-ops mailing list
> inet-ops@puck.nether.net
> https://puck.nether.net/mailman/listinfo/inet-ops


It's a common spammer tactic for this very reason. I can't give you a
good answer though, other than just use one MX and make sure it doesn't
fail.