Conversation
Notices
-
#Spamhaus isn't actually blocking you. Your recipients are relying on Spamhaus to determine what they (your recipients) will allow into their mail server. So the fault lies with your recipients, who have chosen a third-party that mis-identifies your mail server or IP address as spam, and then your recipients compound the error by letting that third-party actually block their inbound mail instead of just tagging it. Sadly, your recipients will never realize which items the third-party is censoring, because they'll never receive those items to classify them for themselves. !SysAdmin
-
Every time a #GMail user is unable to receive my #email because #Google inexplicably ate it, and someone suggests I should give up on !selfhost'ing and just let Google manage *my* mail too, I can only think "are you insane!? Then *I* wouldn't be able to receive e-mail either! Why would I want that!?".