TLS (SSL) AUTH not working

Discussion in 'General' started by Morons, Jan 25, 2007.

  1. Morons

    Morons Member

    Hi, I am re-publishing this as it was "hidden" amongst the backup posting. I have done further research on this and found that in most samples the lines
    Code:
    250-STARTTLS
    250-AUTH GSSAPI CRAM-MD5 LOGIN DIGEST-MD5 PLAIN
    250-AUTH=GSSAPI CRAM-MD5 LOGIN DIGEST-MD5 PLAIN
    250-ENHANCEDSTATUSCODES
    is correct however, it is the only difference I detect visually from the WORKING version as described below. :cool:

    I had an recent experience that my RAID 10 set-up on an DELL server [4years old] crashed 2/4 hard drives simultainious due to heat.
    I recovered fully except for the smtp auth login. I did however upgraded from Mandriva 2006->2007 and this sample is on the non-working server.
    Code:
    220 hera.domain.tld ESMTP Postfix (2.3.3) (Mandriva Linux)
    ehlo localhost
    250-hera.domain.tld
    250-PIPELINING
    250-SIZE 10240000
    250-ETRN
    250-STARTTLS
    250-AUTH GSSAPI CRAM-MD5 LOGIN DIGEST-MD5 PLAIN
    250-AUTH=GSSAPI CRAM-MD5 LOGIN DIGEST-MD5 PLAIN
    250-ENHANCEDSTATUSCODES
    250-8BITMIME
    250 DSN
    auth login
    334 VXNlcm5hbWU6
    anBi
    334 UGFzc3dvcmQ6
    Ymo3NzYtb3Jn
    535 5.7.0 Error: authentication failed: authentication failure
    
    On the other serve it works ! My question is the diffeence is in the lines 250-AUTH GSSAPI CRAM-MD5 LOGIN DIGEST-MD5 PLAIN vs 250-AUTH LOGIN PLAIN
    Code:
    telnet localhost 25
    Trying 127.0.0.1...
    Connected to beta.domain.tld (127.0.0.1).
    Escape character is '^]'.
    220 beta.domain.tld ESMTP Postfix (2.3.3) (Mandriva Linux)
    ehlo localhost
    250-beta.domain.tld
    250-PIPELINING
    250-SIZE 10240000
    250-VRFY
    250-ETRN
    250-STARTTLS
    250-AUTH LOGIN PLAIN
    250-AUTH=LOGIN PLAIN
    250-ENHANCEDSTATUSCODES
    250-8BITMIME
    250 DSN
    auth login
    334 VXNlcm5hbWU6
    anBi
    334 UGFzc3dvcmQ6
    Ymo3NzYtb3Jn
    235 2.0.0 Authentication successful
    The beta server is an plain newly setup box same as above but it works! Can Someone tell me were to look and what files to be edited / compared?
     
    Last edited: Jan 25, 2007
  2. falko

    falko Super Moderator ISPConfig Developer

  3. Morons

    Morons Member

    Done that before this posting, If I uninstall libsasl2-plug-crammd5 libsasl2-plug-digestmd5 libsasl2-plug-gssapi I do get the
    Code:
    250-AUTH LOGIN PLAIN
    250-AUTH=LOGIN PLAIN
    however it still does not authenticate proper., even re-created the cert! [Create the SSL certificate needed for TLS] as instructed on that page.
    I even went rpm -qa |grep [each of the fillowing] cyrus-sasl libsasl2 libsasl2-devel libsasl2-plug-plain libsasl2-plug-anonymous libsasl2-plug-crammd5 libsasl2-plug-digestmd5 libsasl2-plug-gssapi libsasl2-plug-login, rpm -e --nodeps tham and re-installed them.
    After all that effort I still can send / receive mail cept TLS stay broken :(
    Could it be some setting were the base64 encoding/decoding gets done is wrong? Maybe suggest some setting to enable additional debug logging somehow so I can log the errors / reasons for the failure, pleeeze!
     
  4. falko

    falko Super Moderator ISPConfig Developer

    Did you follow the tutorial as close as possible? Maybe you made a typo somewhere.
     
  5. falko

    falko Super Moderator ISPConfig Developer

    Problems should get logged to the mail log on your system.
     
  6. Morons

    Morons Member

    The only log per message (successfull) I get is
    Code:
    cat /var/log/mail/info |grep 02DEE334C02
    this isolate the total logI have per message number
    Code:
    Jan 30 11:35:31 hera postfix/smtpd[2814]: 02DEE334C02: client=unknown[ipnumber]
    Jan 30 11:35:34 hera postfix/cleanup[3168]: 02DEE334C02: message-id=<[email protected]>
    Jan 30 11:35:39 hera postfix/qmgr[4924]: 02DEE334C02: from=<[email protected]>, size=73907, nrcpt=1 (queue active)
    Jan 30 11:35:39 hera postfix/local[3247]: 02DEE334C02: to=<[email protected]>, orig_to=<[email protected]>, relay=local, delay=9.9, delays=9.9/0/0/0.06, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail -f-)
    Jan 30 11:35:39 hera postfix/qmgr[4924]: 02DEE334C02: removed
    As you can clearly see the mail enters procmail but no further logging is happening.
     
  7. martinfst

    martinfst ISPConfig Developer ISPConfig Developer

    If you want log files of Procmail, you need to add a logfile directive in your .procmailrc.

    At at the start of the .procmailrc for the specific user with problems something like
    Code:
    LOGFILE=/var/log/procmail.log
    Check the file after sending another testmail.
     

Share This Page