[Dovecot] dovecot sendmail mysql no inbox error
hi guys,
we are experiencing this particular problem with one of the webmail server we manage. the server is using dovecot as pop3 and imap server while sendmail is being used as mta. when this user tries to login via telnet, this is what i've got:
$ telnet localhost pop3
Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK dovecot ready. user user1 +OK pass password +OK Logged in. -ERR No INBOX for user. Connection closed by foreign host.
when i looked at the maillog i saw this:
Apr 25 20:52:32 samplemail pop3(samplemail): File isn't in mbox format: /var/mail/samplemail Apr 25 20:52:32 samplemail pop3(samplemail): File isn't in mbox format: /var/mail/samplemail Apr 25 20:52:32 samplemail pop3(samplemail): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2007-04-25 20:52:32]
tried google but not much of help, they just suggested to update or replace dovecot. i already update dovecot and made some changes to default_mail_env parameter, still the same result.
dovecot version is 0.99 on a fedora 4 box
any idea?
tried google but not much of help, they just suggested to update or replace dovecot. i already update dovecot and made some changes to default_mail_env parameter, still the same result.
dovecot version is 0.99 on a fedora 4 box
any idea?
You said you tried to update - to what version? If 1.0.0 (the NEW, actual 1.0 release just released this month), did you read the update instructions? There were some major config file changes, so it is not an update that you can perform blindly.
--
Best regards,
Charles
On 4/26/07, Charles Marcus <CMarcus@media-brokers.com> wrote:
tried google but not much of help, they just suggested to update or replace dovecot. i already update dovecot and made some changes to default_mail_env parameter, still the same result.
dovecot version is 0.99 on a fedora 4 box
any idea?
You said you tried to update - to what version? If 1.0.0 (the NEW, actual 1.0 release just released this month), did you read the update instructions? There were some major config file changes, so it is not an update that you can perform blindly.
i updated via yum update dovecot command, i think it is still version 0.99 .
tried google but not much of help, they just suggested to update or replace dovecot. i already update dovecot and made some changes to default_mail_env parameter, still the same result.
dovecot version is 0.99 on a fedora 4 box
any idea?
You said you tried to update - to what version? If 1.0.0 (the NEW, actual 1.0 release just released this month), did you read the update instructions? There were some major config file changes, so it is not an update that you can perform blindly.
i updated via yum update dovecot command, i think it is still version 0.99
0.99 is no longer supported. I recommend seeing if you can find an RPM for 1.0.0 for Fedora4 (someone on this list can probably point you to one) or build one of your own (sorry, can't help you there)) but you'll also need to be aware of the changes, so be sure to read the upgrade instructions/release notes:
http://wiki.dovecot.org/UpgradingDovecot
--
Best regards,
Charles
On 4/27/07, Charles Marcus <CMarcus@media-brokers.com> wrote:
tried google but not much of help, they just suggested to update or replace dovecot. i already update dovecot and made some changes to default_mail_env parameter, still the same result.
dovecot version is 0.99 on a fedora 4 box
any idea?
You said you tried to update - to what version? If 1.0.0 (the NEW, actual 1.0 release just released this month), did you read the update instructions? There were some major config file changes, so it is not an update that you can perform blindly.
i updated via yum update dovecot command, i think it is still version 0.99
0.99 is no longer supported. I recommend seeing if you can find an RPM for 1.0.0 for Fedora4 (someone on this list can probably point you to one) or build one of your own (sorry, can't help you there)) but you'll also need to be aware of the changes, so be sure to read the upgrade instructions/release notes:
http://wiki.dovecot.org/UpgradingDovecot
--
Best regards,
Charles
finally i was able to determine the root cause of the problem, it was due to the user corrupted mbox, the solution was to delete the 1st two lines of the /var/mail/username file, restarted dovecot and whoala, i can now telnet successfully.
finally i was able to determine the root cause of the problem, it was due to the user corrupted mbox, the solution was to delete the 1st two lines of the /var/mail/username file, restarted dovecot and whoala, i can now telnet successfully.
This is a well-known bug in the 0.99 series...
It is still highly recommended that you upgrade to 1.0.0 if possible...
--
Best regards,
Charles
On 4/29/07, Charles Marcus <CMarcus@media-brokers.com> wrote:
finally i was able to determine the root cause of the problem, it was due to the user corrupted mbox, the solution was to delete the 1st two lines of the /var/mail/username file, restarted dovecot and whoala, i can now telnet successfully.
This is a well-known bug in the 0.99 series...
It is still highly recommended that you upgrade to 1.0.0 if possible...
--
yes, partly true, but i think no matter what imap/pop server you use as long as it is in mbox, it will get corrupted.
finally i was able to determine the root cause of the problem, it was due to the user corrupted mbox, the solution was to delete the 1st two lines of the /var/mail/username file, restarted dovecot and whoala, i can now telnet successfully.
This is a well-known bug in the 0.99 series...
It is still highly recommended that you upgrade to 1.0.0 if possible...
yes, partly true,
What 'part'? Both statements I made are true. This *is* a well known bug in the 0.99 series, and you *should* upgrade to 1.0.0 if possible.
but i think no matter what imap/pop server you use as long as it is in mbox, it will get corrupted.
I'm not a fan of mbox, but I hardly think that this is a true statement in general, but I guess I could be wrong.
All I know is, when we were using 0.99, it happened a *lot*... meaning, at least once every other day I had to fix an mbox for someone...
--
Best regards,
Charles
participants (2)
-
Charles Marcus
-
jan gestre