Gleb Smirnoff wrote:
Hi.
For last two days I was trying to make Cyrus Imapd 2.2.1.b to work
on FreeBSD. I have fresh ports collection, and Cyrus Imapd 2.2.1.b
installed from ports with db3 support.
Here are contents of imapd.conf (everything else is left default):
configdirectory: /var/imap
d
On Thu, Sep 04, 2003 at 02:37:58PM -0400, Scott Adkins wrote:
S> Does the directory for that user physically exist? If it is in the default
S> partition, then check /var/spool/imap/user/test and see if it is there.
S> Maybe something happened that the entries got populated in the mailboxes.db
S> f
Does the directory for that user physically exist? If it is in the default
partition, then check /var/spool/imap/user/test and see if it is there.
Maybe something happened that the entries got populated in the mailboxes.db
file, but the directory didn't get created or something...
Scott
--On Thur
On Thu, Sep 04, 2003 at 11:44:34AM -0400, Scott Adkins wrote:
S> I will attach the patch to this email. It applies directly to imap/lmtpd.c
S> and only 2 lines get changed. See if that helps describe the failure msgs
S> a bit better.
Thanks for the patch. However, it doesn't made situation clear
I had this problem initially when moving to 2.2.1b. The problem was that
the users were actually over quota and that was it. Rob committed some
code to CVS for the next version to make the append_check() errors display
a more verbose message about why it failed... When I applied the patch,
it bec
Hi.
For last two days I was trying to make Cyrus Imapd 2.2.1.b to work
on FreeBSD. I have fresh ports collection, and Cyrus Imapd 2.2.1.b
installed from ports with db3 support.
Here are contents of imapd.conf (everything else is left default):
configdirectory: /var/imap
defaultpartition: defau
