Topic: Mail being Rejected from Gmail / Hotmail

[shawnbishop]

Good Day

I have a situation where my main server, serving about 300 users is rejecting email from Google, or users using Google Apps with the following error


Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 500 500 Syntax error (no parameters allowed) (state 9).


The error, in the /var/log/qpsmtpd/current file is as follows


Hi mail-iw0-f180.google.com [209.85.214.180]
@400000004e1c511d130a1b7c 6137 250-PIPELINING
@400000004e1c511d130a2f04 6137 250-8BITMIME
@400000004e1c511d130a428c 6137 250-SIZE 20000000
@400000004e1c511d130a5614 6137 250 STARTTLS
@400000004e1c511d2630831c 6137 dispatching STARTTLS
@400000004e1c511d2634d87c 6137 logging::logterse plugin (deny): ` 209.85.214.180   mail-iw0-f180.google.com   mail-iw0-f180.google.com      tls   901   Syntax error (no parameters allowed)   msg denied before queued
@400000004e1c511d2634f3d4 6137 500 Syntax error (no parameters allowed)
@400000004e1c511d39cbad5c 6137 dispatching QUIT


I am also attaching the qpsmtpd output configuration


root@mail qpsmtpd]# config show qpsmtpd
qpsmtpd=service
    Authentication=enabled
    Bcc=disabled
    BccMode=cc
    BccUser=maillog
    DNSBL=disabled
    LogLevel=6
    MaxScannerSize=25000000
    RBLList=zen.spamhaus.org:whois.rfc-ignorant.org:dnsbl.njabl.org
    RHSBL=disabled
    RequireResolvableFromHost=yes
    SBLList=bogusmx.rfc-ignorant.org:multi.surbl.org:black.uribl.com:rhsbl.sorbs.net:bulk.rhs.mailpolice.com:fraud.rhs.mailpolice.com:porn.rhs.mailpolice.com:adult.rhs.mailpolice.com:ex.dnsbl.org
    TlsBeforeAuth=0
    access=public
    qplogsumm=disabled
    status=enabled


Is anybody else having this problem??

Shawn

[CharlieBrady]

I have a situation where my main server, serving about 300 users is rejecting email from Google, or users using Google Apps with the following error

Perhaps you missed this when you posted:


Don't report problems here - Please report bugs and potential bugs in the bug tracker

[shawnbishop]

Good day Charlie

I am not sure where you are going with your statement??, it isnt a potential bug..The server has been working for over 4 years, and yesterday starting presenting
those errors in the error logs and qpsmtp/current logs

I understand that a bug must be reported in the bug tracker, if every issue encountered was reported in the bug tracker, well then the forum would be useless..

I asked if anybody else had seen the errors, especially the below error

"tls   901   Syntax error (no parameters allowed)   msg denied before queued"

[mmccarn]

Is anybody else having this problem??

I've had trouble with tls on my home SME ever since it was introduced.  I haven't opened any bugs on this because the cause is my fault (since my other SME servers aren't having any trouble).

On my problem SME server I have manually disabled TLS support using Charlie's notes from http://bugs.contribs.org/show_bug.cgi?id=6123#c5

You may benefit from disabling "tls before auth" as described in the wiki: http://wiki.contribs.org/Email#SMTP_Authentication_TLS_before_Auth_disable_.26_enable

[CharlieBrady]

I am not sure where you are going with your statement??, it isnt a potential bug.

I'll call BS on that.

Does it really matter whether anyone else is seeing the problem, when you are losing mail?

[cactus]

I understand that a bug must be reported in the bug tracker

Then please do so and report the bug number or a link for future readers.

if every issue encountered was reported in the bug tracker, well then the forum would be useless..

For every category we try to use the proper tools, please help us improve SME Server and use the tools that are preferred and provided. Problems or abnormal functionality causing problems should be reported in the bug tracker, advice or questions on configuration and stuff like that can and should be asked and answered in the forum.