Current time: 11-15-2024, 06:58 PM Hello There, Guest! (LoginRegister)


Post Reply 
Auth Problems Sasl + Courier IMAP/POP
Author Message
starfoxx Offline
Junior Member
*

Posts: 15
Joined: Jun 2009
Reputation: 0
Post: #1
Auth Problems Sasl + Courier IMAP/POP
Hi,

first i want say sorry for my bad english :-)

System from etch to lenny upgrade per dist_upgrade
VHCS 2.7.xx to ispCP 1.0.0.0
Use Upgrade-Howto from your page here

My Problem:
I cannot auth per sasl in postfix and courier imap/pop
what files must exists in which paths?

Thanks a lot.

Greetz starfoxx
06-08-2009 08:38 PM
Find all posts by this user Quote this message in a reply
BeNe Offline
Moderator
*****
Moderators

Posts: 5,899
Joined: Jan 2007
Reputation: 68
Post: #2
RE: Auth Problems Sasl + Courier IMAP/POP
Please post your Mail logs!

Greez BeNe
06-08-2009 08:46 PM
Visit this user's website Find all posts by this user Quote this message in a reply
starfoxx Offline
Junior Member
*

Posts: 15
Joined: Jun 2009
Reputation: 0
Post: #3
RE: Auth Problems Sasl + Courier IMAP/POP
Hi,

mail.log:

Jun 8 12:55:52 debian postfix/smtpd[16854]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:52 debian postfix/smtpd[16854]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:52 debian postfix/smtpd[16862]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:52 debian postfix/smtpd[16862]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:52 debian postfix/smtpd[16860]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:52 debian postfix/smtpd[16860]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:53 debian postfix/smtpd[16861]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:53 debian postfix/smtpd[16861]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:53 debian postfix/smtpd[16863]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:53 debian postfix/smtpd[16863]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:53 debian postfix/smtpd[16854]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16862]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16860]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16861]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16863]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16854]: connect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16862]: connect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16860]: connect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16861]: connect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16863]: connect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16854]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:53 debian postfix/smtpd[16854]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:53 debian postfix/smtpd[16862]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:53 debian postfix/smtpd[16862]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:53 debian postfix/smtpd[16860]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:53 debian postfix/smtpd[16860]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:53 debian postfix/smtpd[16861]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:53 debian postfix/smtpd[16861]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:53 debian postfix/smtpd[16863]: warning: SASL authentication failure: no secret in database
Jun 8 12:55:53 debian postfix/smtpd[16863]: warning: xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]: SASL DIGEST-MD5 authentication failed: authentication failure
Jun 8 12:55:53 debian postfix/smtpd[16854]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16862]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16860]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16861]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]
Jun 8 12:55:53 debian postfix/smtpd[16863]: disconnect from xxxxxxx.dip.t-dialin.net[xxx.xxx.xxx.xxx]

---------------------------------------------

Jun 8 12:58:50 debian couriertcpd: Connection, ip=[::ffff:xxx.xxx.xxx.xxx]
Jun 8 12:58:50 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], command=CAPABILITY
Jun 8 12:58:55 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], command=AUTHENTICATE
Jun 8 12:58:55 debian couriertcpd: LOGIN FAILED, method=LOGIN, ip=[::ffff:xxx.xxx.xxx.xxx]
Jun 8 12:59:00 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], command=LOGIN
Jun 8 12:59:00 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], username=admin@xxxxx.de
Jun 8 12:59:00 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], password=xxxxxxxxxx
Jun 8 12:59:00 debian couriertcpd: LOGIN FAILED, user=admin@xxxxxx.de, ip=[::ffff:xxx.xxx.xxx.xxx]
Jun 8 12:59:12 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], command=AUTHENTICATE
Jun 8 12:59:12 debian couriertcpd: LOGIN FAILED, method=LOGIN, ip=[::ffff:xxx.xxx.xxx.xxx]
Jun 8 12:59:17 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], command=LOGIN
Jun 8 12:59:17 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], username=admin@xxxxxx.de
Jun 8 12:59:17 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], password=xxxxxxxxxx
Jun 8 12:59:17 debian couriertcpd: LOGIN FAILED, user=admin@xxxxxx.de, ip=[::ffff:xxx.xxx.xxx.xxx]
Jun 8 12:59:27 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], command=LOGOUT
Jun 8 12:59:27 debian couriertcpd: LOGOUT, ip=[::ffff:xxx.xxx.xxx.xxx], rcvd=210, sent=566
Jun 8 12:59:29 debian couriertcpd: Connection, ip=[::ffff:xxx.xxx.xxx.xxx]
Jun 8 12:59:29 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], command=CAPABILITY
Jun 8 12:59:32 debian couriertcpd: LOGIN: ip=[::ffff:xxx.xxx.xxx.xxx], command=AUTHENTICATE
Jun 8 12:59:32 debian couriertcpd: LOGIN FAILED, method=LOGIN, ip=[::ffff:xxx.xxx.xxx.xxx]


MFG
starfoxx
(This post was last modified: 06-08-2009 09:05 PM by starfoxx.)
06-08-2009 08:57 PM
Find all posts by this user Quote this message in a reply
starfoxx Offline
Junior Member
*

Posts: 15
Joined: Jun 2009
Reputation: 0
Post: #4
RE: Auth Problems Sasl + Courier IMAP/POP
Hi,

in /etc/postfix/sasl/smtpd.conf it writes:

pwcheck_method: saslauthd auxprop
auxprop_plugin: sql
mech_list: PLAIN LOGIN cram-md5 digest-md5
allow_plaintext: true
sql_engine: mysql
sql_hostnames: localhost
sql_user: xxxxx
sql_passwd: xxxxx
sql_database: ispcp
sql_select: select mail_pass from mail_users where mail_addr=.%r. and mail_acc='%u'
sql_verbose: yes
log_level: 7

Is this right?

and where must the sasldb2 file save. down the postfix chroot?

Greetz
starfoxx
06-08-2009 10:24 PM
Find all posts by this user Quote this message in a reply
starfoxx Offline
Junior Member
*

Posts: 15
Joined: Jun 2009
Reputation: 0
Post: #5
RE: Auth Problems Sasl + Courier IMAP/POP
Hi,

so, i get back the backupfile userdb and kill smtpd.conf. restarted the services pop and imap and it works. The sasldb2 file copyed from backup in /etc and postfix chroot - dir. Now it works. How long? :-( I think when my reseller add a new domain, the system will hang.

Greetz
starfoxx
06-09-2009 03:58 AM
Find all posts by this user Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)