On 4/22/2010 6:19 PM, webmas...@aus-city.com wrote:

Seems its plesk and not logging everything in the logs. It uses its own
logging for mail, I could not find my successful login (below). The
saslauthd is not running, but plesk must start use another process to do
this, but its is running:

Logs are important for solving problems and tracing what happened to mail. If you can't find logs, ask on a plesk support forum.

Without proper logging, it's far more difficult to diagnose problems and offer correct solutions.


But it is running and verifies (I did this on a remote server)

telnet xxx 587
Trying xxx...
Connected to xxx.
Escape character is '^]'.
220 xxx ESMTP Postfix
ehlo xxx.
250-xxx
250-PIPELINING
250-SIZE 20480000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH DIGEST-MD5 CRAM-MD5 PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
mail from: <xxx>
250 2.1.0 Ok
quit
221 2.0.0 Bye
Connection closed by foreign host.

This shows that postfix is listening and offering AUTH on port 587, but not much else. It would be more interesting to try to authenticate as described in SASL_README (warning: don't post base64 encoded username/password to the list; they are trivially decoded.)


I will have to check out my client as its only local to him alone. Also
as I did say he runs multiple OS on the same machine and one works
perfectly.

Lastly digging in my logs, I found this:

Apr 23 04:23:28 server postfix/smtpd[24755]: connect from
unknown[xx.xx.xx.xx]
Apr 23 04:23:28 server postfix/smtpd[25116]: warning: 127.0.0.1: address
not listed for hostname localhost
Apr 23 04:23:28 server postfix/smtpd[25116]: connect from
unknown[127.0.0.1]

Any idea why? Its listed in the /etc/hosts file:

::1 localhost localhost.localdomain localhost6.localdomain6 localhost6
127.0.0.1 xx.xx.xx.xx xx.xx.xx server localhost.localdomain localhost


Maybe check your /etc/nsswitch.conf? This has no relation to any other problems you may be having.

  -- Noel Jones

Reply via email to