Error within my mail.log

Discussion in 'Server Operation' started by Hans, Nov 24, 2006.

Thread Status:
Not open for further replies.
  1. Hans

    Hans Moderator Moderator

    Within my /etc/mail.log i see that there are some errors like this:

    Nov 23 02:38:48 server1 courierpop3login: LOGIN, user=username, ip=[::ffff:89.205.148.108]
    Nov 23 02:38:51 server1 postfix/smtpd[2626]: unable to get private key from '/etc/postfix/ssl/smtpd.key'
    Nov 23 02:38:51 server1 postfix/smtpd[2626]: 2626:error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch:x509_cmp.c:389:
    Nov 23 02:38:51 server1 postfix/smtpd[2626]: TLS engine: cannot load RSA cert/key data

    The error occurs only with 1 user.
    What could be the reason that this error occurs and how can i overcome/solve this?
     
  2. Mathias

    Mathias New Member

    Hi Hans

    You can remove this bug by updating your smtpd.key :)

    It stands in the guides here at HowToForge, how you update your key.

    Best Regards
    Mathias
     
  3. Hans

    Hans Moderator Moderator

    @Mathias,

    I did not know about this bug.
    After some googleing, i found out that the error message is a little bit misleading and not serious.
    Anyway, I've created the new certificates/keys using the commands:

    cd /etc/postfix/ssl/
    openssl genrsa -des3 -rand /etc/hosts -out smtpd.key 1024
    chmod 600 smtpd.key
    openssl req -new -key smtpd.key -out smtpd.csr
    openssl x509 -req -days 3650 -in smtpd.csr -signkey smtpd.key -out smtpd.crt
    openssl rsa -in smtpd.key -out smtpd.key.unencrypted
    mv -f smtpd.key.unencrypted smtpd.key
    openssl req -new -x509 -extensions v3_ca -keyout cakey.pem -out cacert.pem -days 3650

    I will verify my mail.log again to see if the problem is solved.

    Thanks for your reply.
     
    Last edited: Nov 25, 2006
  4. Hans

    Hans Moderator Moderator

    Solution worked!

    The solution mentioned by Mathias helped me.
    There are no errors anymore.

    Thanks again! :)

    This thread can be closed now.
     
Thread Status:
Not open for further replies.

Share This Page