FS#16677 - [courier-mta] (webmaild) can not read Maildir folders

Attached to Project: Community Packages
Opened by cesar (urulab) - Thursday, 15 October 2009, 20:50 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 24 September 2010, 04:18 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Tobias Kieslich (tobias)
Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

After upgrading courier-mta and courier-authlib, the webmaild daemon, no allow access to folders 'Inbox', 'Sent', etc.

The other options, "preferences", "create message", etc, run fine. I' Ve tested en 2 Archlinux machines one in i686 kernel 2.6.27.37-1-lts an other in x86_64 kernel 2.6.31.4-1

Browser error:
Cache-Control: no-store Pragma: no-cache Content-Type: text/html;
charset=us-ascii
Can't create cache file

Syslog mail.log
Oct 15 15:47:07 myhost sqwebmaild: LOGIN, user=test, ip=[127.0.0.1]
Oct 15 15:47:09 myhost sqwebmaild: fop_read_meta: ./tmp/1255628829.M371527P26214_sqwebmail-db.myhost: unexpected file type or format
Oct 15 15:47:09 myhost sqwebmaild: ./tmp/1255628829.M371527P26214_sqwebmail-db.myhost: Invalid type 5 specified
Oct 15 15:47:09 myhost sqwebmaild: Can't create cache file |./tmp/1255628829.M371527P26214_sqwebmail-db.myhost|: No such file or directory


I believe the error is related to Berkeley db-4.8 functions, see makealiases command.

Only rebuild courier-mta suite with '--with-db=gdbm' flag instead of '--with-db=db' and now returning to work well.

Thanks in advance.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Friday, 24 September 2010, 04:18 GMT
Reason for closing:  Fixed
Comment by Glenn Matthys (RedShift) - Friday, 16 October 2009, 06:31 GMT
Those files in /tmp are probably cache, have you tried removing those cache files first?
Comment by Glenn Matthys (RedShift) - Friday, 16 October 2009, 10:13 GMT
Comment by cesar (urulab) - Friday, 16 October 2009, 10:28 GMT
Yes, after remove /tmp/courier*, I run:

[root@myhost ~]# makealiases

fop_read_meta: /tmp/courier.yJuvta: unexpected file type or format
/tmp/courier.yJuvta: Invalid type 5 specified
aliascombine: ERR: Success
fop_read_meta: /tmp/courier.zJueqa: unexpected file type or format
/tmp/courier.zJueqa: Invalid type 5 specified
makealiases: ERR: No such file or directory

The /etc/courier/aliasdir/ and /etc/courier/aliases/system have the default package content.
But if I again build courier-mta with gdbm this problem do not exist.

greetings.
Comment by Nezmer (Nezmer) - Wednesday, 30 December 2009, 16:03 GMT
I can confirm that makealiases is broken and that cesar's solution works.
Comment by Mark Constable (markc) - Monday, 17 May 2010, 02:15 GMT
I notice this package is still built with --with-db=db and I am getting the same error and I can also confirm that --with=gdbm fixes this problem.

The apache dependency is not good as I don't use it, nor ldap, however my first attempt at rebuilding the package kills mysql logins with a "imapd-ssl: authentication error: Input/output error". So I managed to fix the aliases problem but now I can't login at all. This is what happens when I try to rebuild the system wide aliases 6 months after this error was first reported...

root@u1 /etc/courier makealiases
fop_read_meta: /tmp/courier.9IejPk: unexpected file type or format
/tmp/courier.9IejPk: Invalid type 5 specified
aliascombine: ERR: Success
fop_read_meta: /tmp/courier.8IK8Vk: unexpected file type or format
/tmp/courier.8IK8Vk: Invalid type 5 specified
makealiases: ERR: No such file or directory
Comment by Mick Howe (Cheifchimp) - Tuesday, 18 May 2010, 00:40 GMT
would it be possible to update the package in the repo to include cesar's solution PLEASE

Loading...