Loading ...
Sorry, an error occurred while loading the content.

295075Re: email from comcast.net is bouncing

Expand Messages
  • Grant
    Aug 30, 2013
    • 0 Attachment
      >> Aug 26 21:21:35 [postfix/tlsproxy] CONNECT from [209.85.219.51]:41193
      >> Aug 26 21:21:36 [postfix/postscreen] NOQUEUE: reject: RCPT from
      >> [209.85.219.51]:41193: 450 4.3.2 Service currently unavailable;
      >> from=<MASKED@...>, to=<MASKED@...>, proto=ESMTP,
      >> helo=<mail-oa0-f51.google.com>
      >> Aug 26 21:21:36 [postfix/tlsproxy] DISCONNECT [209.85.219.51]:41193
      > ...
      >> postscreen_bare_newline_enable = yes
      >> postscreen_non_smtp_command_enable = yes
      >> postscreen_pipelining_enable = yes
      >
      > As documented, the above settings will cause Postfix to reject mail
      > with 4XX:
      >
      > http://www.postfix.org/POSTSCREEN_README.html#after_220

      Yes but the issue is that the whitelist doesn't seem to be working.

      >> postscreen_dnsbl_sites = zen.spamhaus.org list.dnswl.org*-1
      >> postscreen_dnsbl_whitelist_threshold = -1
      >
      > This feature requires Postfix 2.11 snapshot 20130512 or later.
      > You can find out which version you have with:
      >
      > postconf mail_version

      # postconf mail_version
      mail_version = 2.11-20130818

      >> Aug 23 06:35:11 [postfix/smtp] 72A0E5C801E: conversation with
      >> mx1.comcast.net[68.87.26.147] timed out while receiving the initial
      >> server greeting
      >> Aug 23 09:04:03 [postfix/smtp] 80A8A5C801E: lost connection with
      >> mx1.comcast.net[68.87.26.147] while receiving the initial server
      >> greeting
      >
      > These warnings are from your Postfix SMTP client.

      Do they necessarily indicate a problem with my postfix or could they
      be due to a problem with the server on the other end?

      - Grant
    • Show all 23 messages in this topic