Topic: [SOLVED] Connected_to_127.0.0.1_but_greeting_failed./Remote_host_said:_451_Coul

[cactus]

This morning my server suddenly stopped sending mail through the external mailserver of my provider although I did not change anything the last few weeks on my server.

I already verified if my account and password were still valid by login in to their webmail interface and my account still seems to be working.

My server is configured to do SMTP auth proxying (as has always been the case). In the qmail/current log file I see the following information:

Code: [Select]

@400000004935807824f16b9c status: local 0/10 remote 0/20
@40000000493580ff24b9fc34 starting delivery 8: msg 557063 to remote username@obfuscated.domain
@40000000493580ff24c27fe4 status: local 0/10 remote 1/20
@40000000493580ff3b2092e4 delivery 8: deferral: Connected_to_127.0.0.1_but_greeting_failed./Remote_host_said:_451_Could_not_auth_to_mail_server/
@40000000493580ff3b20ecbc status: local 0/10 remote 0/20/
I have already tried setting smtp-auth-proxy's Debug property to enabled in the configuration database and restarted the service like this:

Code: [Select]

db configuration setprop smtp-auth-proxy Debug enabled
signal-event email-update
My smtpd-auth-proxy configuration database entry now looks like this (credentials blanked out):

Code: [Select]

[root@homer ~]# db configuration show smtp-auth-proxy
smtp-auth-proxy=service
    Debug=enabled
    Passwd=*********
    Userid=*********
    status=enabled
[root@homer ~]#
But after that at least the qmail/current log is not giving me more detail than before.
Is there a way to find out what is causing this problem for instance by increasing (other) loglevels? And how would I do so on SME Server 7.4? Are there any other logfiles I need to have a look at?

[CharlieBrady]

This morning my server suddenly stopped sending mail through the external mailserver of my provider although I did not change anything the last few weeks on my server.

You'll probably need to speak to your ISP.

The Debug log for the smtp auth proxy is in /var/log/smtp_auth_proxy/current (IIRC).

[cactus]

You'll probably need to speak to your ISP.

I already thought so, but they are not the most cooperative as they do not cater for such services. So the more 'evidence' I have to use against them the easier it will be, hopefully.

The Debug log for the smtp auth proxy is in /var/log/smtp_auth_proxy/current (IIRC).

OK, I will have a look at that file. Thanks!

[Stefano]

@40000000493580ff3b2092e4 delivery 8: deferral: Connected_to_127.0.0.1_but_greeting_failed./Remote_host_said:_451_Could_not_auth_to_mail_server/

In my experience this is a isp problem.. if your credentials are valid, the only reason for such a failure is something wrong on isp side

my 2€c

Ciao
Stefano

[CharlieBrady]

In my experience this is a isp problem.. if your credentials are valid, the only reason for such a failure is something wrong on isp side

I agree.

See bug 4544 - ISP's mail server claims to support chap-md5 but doesn't actually support it.

[cactus]

I already thought so, but they are not the most cooperative as they do not cater for such services. So the more 'evidence' I have to use against them the easier it will be, hopefully.

They seem to have silently dropped the need for authentication, after disabling smtp-auth-proxy mail started flowing again. How I like ISPs