Conversation

Notices

  1. # 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 inbou

    Friday, 06-Jan-17 20:03:23 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W
    1. Every time a # user is unable to receive my # because # 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!?".

      Friday, 06-Jan-17 20:49:28 UTC from status.hackerposse.com
      1. Google ate it? Does it mean means the mail was lost without any error message from gmail's side?
        Recently I've had problems with my self hosted email service too, with a gmail friend not receiving a email and I got no error message.

        Sunday, 08-Jan-17 05:57:09 UTC from social.systemreboot.net
        1. Mostly # `just' hides things in a spam-bucket; if you've no other means of contacting the person, that's equivalent to silent discard.

          Tuesday, 10-Jan-17 03:59:34 UTC from status.hackerposse.com