

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
4 messages in net.sourceforge.lists.courier-usersRE: [courier-users] vpopmail+courier+...| From | Sent On | Attachments |
|---|---|---|
| list | May 23, 2005 7:40 am | |
| Shane Metler | May 23, 2005 8:18 am | |
| list | May 23, 2005 10:00 am | |
| Tim Hunter | May 23, 2005 10:18 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | RE: [courier-users] vpopmail+courier+mysql (problem with authdaemond: mysqlserver has gone away) | Actions... |
|---|---|---|
| From: | Shane Metler (sha...@shanemetler.com) | |
| Date: | May 23, 2005 8:18:04 am | |
| List: | net.sourceforge.lists.courier-users | |
Hi there,
I had the same issue with intermittent "vmysql: sql error[3]: MySQL server has gone away" errors.
For me this was caused by Courier-authlib creating persistent connections to the MySQL DB.
After the persistent connection is created, Courier-authlib assumes it is still valid and tries to use it, but sometimes the MySQL DB has closed that persistent connection.
Check your MySQL settings for the connection timeouts (default is 8 hours I believe).
If the MySQL DB is timing out those persistent connections, or you are restarting the MySQL DB, you will get that error for the first login handled by Courier-authlib. Once Courier-authlib reestablishes the persistent connection, then everything should run as normal.
Shane
-----Original Message----- From: cour...@lists.sourceforge.net [mailto:cour...@lists.sourceforge.net] On Behalf Of list Sent: Monday, May 23, 2005 1:45 AM To: cour...@lists.sourceforge.net Subject: [courier-users] vpopmail+courier+mysql (problem with authdaemond: mysqlserver has gone away)
My setup:
Courier-imap 4.0.2 Courier-authlib 0.55 PHP 5.0.4 Apache 1.3.33 Squirrelmail 1.4.4 and I tried 1.5.0 Compatibility plugin secure_login plugin Vpopmail 5.4.10 MySQL 4.1.12 Slackware Linux 10.1 All software was installed from source.
The problem, which I have not seen anyone else state EXACTLY, is that squirrelmail refuses to authenticate. Pop3 and smtp both work perfectly fine via a pop3 email client, vpopmail is interfacing with mysql just fine and I can check my mail using an email client. But, as soon as I try to login with squirrelmail (and I even tried using sqwebmail) authentication fails.
I always get the same errors in my maillog:
mail1 imapd: Connection, ip=[::ffff:127.0.0.1] mail1 imapd: LOGIN FAILED, user=****, ip=[::ffff:127.0.0.1] mail1 httpd: Squirrelmail login failed for Username : ****, Password : $$$$ mail1 imapd: Disconnected, ip=[::ffff:127.0.0.1], time=5
(username and password were replaced by me, they were correct)
However, sometimes along with that I get this very familiar error:
mail1 authdaemond: vmysql: sql error[3]: MySQL server has gone away
Which I'm sure most of you have seen before in a few circumstances. As I
stated before, vpopmail works with mysql just fine, and I'm triple and quadruple checked my squirrelmail username and password that is being used to access the mysql database. I can't find any information that helps me
with this, I've searched and searched...please give me an easy answer.
If you need more info, or anything clarified, please let me know...this is driving me crazy! ;)
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________ courier-users mailing list cour...@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users







