Pop3d Authentication Error Input/output Error Ldap
Contents |
this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ imapd: authentication error: Input/output error Hi, I have setup freebsd no error in imap command received by server. 6.2 with postfix, courier-imap with mysql backend, but everytime i try
Courier Imap Log File
to login via squirrelmail or roundcube, i get the following error in my maillog file Feb authdaemon: s_connect() failed: no such file or directory 13 22:39:30 zz imapd: LOGIN FAILED, user=[hidden email], ip=[127.0.0.1] Feb 13 22:39:30 zz imapd: authentication error: Input/output error I need some help, please ;) ------------------------------------------------------------------------- Take Surveys. Earn
Imapd: Authentication Error: No Such File Or Directory
Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________ Courier-imap mailing list [hidden email] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap Andy Shellam (Mailing Lists) Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content courier imap authentication as Inappropriate ♦ ♦ Re: imapd: authentication error: Input/output error Ebbe Hjorth wrote: > Hi, > > I have setup freebsd 6.2 with postfix, courier-imap with mysql backend, > but everytime i try to login via squirrelmail or roundcube, i get the > following error in my maillog file > > Feb 13 22:39:30 zz imapd: LOGIN FAILED, user=[hidden email], ip=[127.0.0.1] Feb > 13 22:39:30 zz imapd: authentication error: Input/output error > > I need some help, please ;) > Whenever I've seen this, it's been a problem with the authentication daemon talking to the database (in your case, MySQL.) Turn up the debugging options in the authentication daemon config file, restart the daemon, and use the "authtest" program to check before you try and login to Courier IMAP. That will log any MySQL-related errors. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through
in Sign up Sign up Linode ForumLinode Community Forums FAQ Search Members Register Login [ Anonymous ] imapd-ssl: authentication error: Input/output error Post new topic Reply to topic Linode
Courier Log Sheet Template
Forum » Linux Community Forums » Email/SMTP Related Forum Print view Previous
Courier Authdaemon
topic | Next topic Author Message fifo Post subject: imapd-ssl: authentication error: Input/output errorPostPosted: Thu Sep 29, 2005 9:57 pm authdaemond: fail, all modules rejected Offline Senior Member Joined: Thu Sep 29, 2005 9:52 pm Posts: 79 Website: http://www.hectorg.net Location: Miami, Florida I followed the HOWTO Email system for the home netwok and get this "imapd-ssl: authentication error: Input/output http://courier-mail-server.10983.n7.nabble.com/imapd-authentication-error-Input-output-error-td14588.html error" in my mail.err file everytime I try to log in. I have tried looking over the web on this forum but nothing I have seen works. I have double and tripple checked everything that I thought would cause this but im still stumped. Sep 29 19:38:17 xxx imapd-ssl: LOGIN FAILED, user=xxx, ip=[::ffff:127.0.0.1] Sep 29 19:38:17 xxx imapd-ssl: authentication error: Input/output error Top Profile Reply with quote https://forum.linode.com/viewtopic.php?t=1888 pclissold Post subject: PostPosted: Fri Sep 30, 2005 4:10 am Offline Senior Member Joined: Fri Oct 24, 2003 3:51 pm Posts: 969 Location: Netherlands The authentication scheme for Courier IMAP has changeds for version 4 and it's a bit of a muddle. Check this link for info on a possible fix, even if you're not using Gentoo and/or you're not upgrading but doing a fresh install. _________________/ Peter Top Profile Reply with quote fifo Post subject: PostPosted: Fri Sep 30, 2005 5:34 pm Offline Senior Member Joined: Thu Sep 29, 2005 9:52 pm Posts: 79 Website: http://www.hectorg.net Location: Miami, Florida Hey thanks that was the problem!!! Top Profile Reply with quote Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 yearSort by AuthorPost timeSubject AscendingDescending Post new topic Reply to topic Linode Forum » Linux Community Forums » Email/SMTP Related Forum Who is online Users browsing this forum: No registered users and 2 guests You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forum Search for: Jump to: Select a forum ------------------ Linode.com Rela
how to use courier's debugging features to pinpoint the problem. 1. Turn on debugging For courier-imap, you need to set one of the following values in /usr/local/etc/authdaemonrc: DEBUG_LOGIN=1 # turn on authentication debugging DEBUG_LOGIN=2 # turn on authentication debugging AND show passwords This setting is located at the very http://www.courier-mta.org/authlib/README.authdebug.html end of the configuration file. After changing this setting, restart the authentication daemon by running the "authdaemond stop" and "authdaemond start" commands. At this point, all debugging output goes to syslog at level 'debug', which is normally not shown. You will probably need to change your /etc/syslog.conf file to be able to see these messages. If you have an existing entry which says "mail.info" (which means facility 'mail', level 'info' or higher) then authentication error you can just change this to "mail.debug". Alternatively you can add a new entry like this: *.debug /var/log/debug Don't forget to create this file, and to send a HUP signal to syslogd to make it re-read its configuration: # touch /var/log/debug # killall -1 syslogd If you don't want to mess around with your syslog configuration, you can also start authdaemond manually, and log its output to a file: /usr/local/libexec/courier-authlib/authdaemond >filename 2>&1 no such file 2. Issue a manual login You can use the authtest command to verify authentication, or go ahead and install Courier-IMAP. For courier-imap, you will get much better information by not using a mail client and manually logging in using 'telnet'. The transcript of this telnet session may give useful information as to what is going on. If you are going to report a problem to the mailing list, you should certainly include this transcript as well as the corresponding debugging output. -- to debug POP3 -- # telnet x.x.x.x 110 user USERNAME pass PASSWORD stat quit -- to debug IMAP -- # telnet x.x.x.x 143 a login USERNAME PASSWORD a examine inbox a logout -- to debug POP3 over SSL -- # openssl s_client -connect x.x.x.x:995 (then use same commands as POP3 example) -- to debug IMAP over SSL -- # openssl s_client -connect x.x.x.x:993 (then use same commands as IMAP example) This isn't an option for sqwebmail of course - just login through the web interface and check the authentication debug log which is generated. 3. Interpret the debug output First, a brief explanation of courier's authentication system. There are a number of standalone authentication modules. An authentication module exists for every authentication method. Each authentication module is installed as a shared library. When authdaemo