Hi all
I am wondering how different hosting providers are managing outgoing spam sent from their servers.
In other words; what do you do to limit or remedy this spam issue?
Many clients use the mail() command to sent contact form messages (many to their hotmail) (and ofcourse many are spam).
Wordpress (and others) use the mail() command to notify clients about a new (spam) message commented on a public topic. And so on..
Clients struggle very much to set up a working captcha. It is a hell to manage, and to follow up on them.
I have told many to stop using a contact form altogether or if really necessary set up their own (protected) RSS feed. They don't understand, and it is 'support heavy' to explain.
I have heard of providers disabling outgoing messages sent from websites towards external e-mail addresses.
They only allow these messages to be sent to a mailbox hosted inside their own network.
Maybe this is what I want to achieve, I don't know yet.
I also don't know how clients will accept this if this kind of limitation is implemented.
Using an e-mail address whitelist could be something if we can whitelist our own hosted domains.
Using an outgoing spamfilter is maybe not what I want to do, because its not watertight.
I am wondering how different hosting providers are managing outgoing spam sent from their servers.
In other words; what do you do to limit or remedy this spam issue?
Many clients use the mail() command to sent contact form messages (many to their hotmail) (and ofcourse many are spam).
Wordpress (and others) use the mail() command to notify clients about a new (spam) message commented on a public topic. And so on..
Clients struggle very much to set up a working captcha. It is a hell to manage, and to follow up on them.
I have told many to stop using a contact form altogether or if really necessary set up their own (protected) RSS feed. They don't understand, and it is 'support heavy' to explain.
I have heard of providers disabling outgoing messages sent from websites towards external e-mail addresses.
They only allow these messages to be sent to a mailbox hosted inside their own network.
Maybe this is what I want to achieve, I don't know yet.
I also don't know how clients will accept this if this kind of limitation is implemented.
Using an e-mail address whitelist could be something if we can whitelist our own hosted domains.
Using an outgoing spamfilter is maybe not what I want to do, because its not watertight.