Bug 131336 - cyrus imapd doesn't work "out of the box"
Summary: cyrus imapd doesn't work "out of the box"
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: Final
Hardware: x86 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Carsten Hoeger
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-28 16:50 UTC by Martin Jost
Modified: 2005-11-07 13:32 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Jost 2005-10-28 16:50:20 UTC
Notes:
Some of the problems should IHMO been solved by changing/adding to the way imapd gets installed.
Others should maybe be documented.
Others are maybe just the fate of those trying to get it to work...
I hope my list is consistent. I'm afraid, that it doesn't cover all possible setups.

- Package selection:
  selecting 'cyrus-imapd" doesn't got me very far. I also had to add some of the
  cyrus-sasl-packages:
  cyrus-sasl-crammd5
  cyrus-sasl
  cyrus-sasl-digestmd5
  maybe others (too)
  and the perl modules for cyradm:
  perl-Authen-SASL-Cyrus-0.12-2
  perl-Cyrus-IMAP-2.2.12-13

- post install actions
  - The entries for "fud" and "lmtp" in /etc/services where missing
  - /usr/share/doc/packages/cyrus-imapd/tools/mkimap needs to be run to create 
    files and directories
  - Now imapd could be started, but imtest failed with  
    "fatal error: can't write proc file"
    The reason where wrong permissions on /var/spool/imap and below
    (Should be owned by cyrus:mail)
    ditto for /var/spool/imap/user and below

- Later on, one needs a IMAP-Password. (documentation issue ?)
  This needs to be set by /usr/sbin/saslpasswd2
  (for at least 'cyrus' (the admin) and all users wanting to log in to imapd.)
  The resulting file /etc/sasldb2 needs to be readable by user "cyrus".

[
Now I have a "small" problem left:
imapd can be started by hand, but it isn't started at system boot:
godot:~ # ll /etc/rc.d/rc5.d/*imap*
lrwxrwxrwx  1 root root 8 Oct 25 09:30 /etc/rc.d/rc5.d/K07imapd -> ../cyrus
lrwxrwxrwx  1 root root 8 Oct 25 22:16 /etc/rc.d/rc5.d/S09imapd -> ../cyrus

By hand:
/etc/rc.d/rc5.d/S09imapd start
Starting IMAP/POP3 service (cyrus-imapd)                          done

But not at system boot
No message on console using "splash=verbose", no entries in boot log.
]
Comment 2 Forgotten User ZhJd0F0L3x 2005-10-28 17:12:48 UTC
reassigning to maintainer.
Comment 5 Carsten Hoeger 2005-11-03 12:53:00 UTC
You seemed to somehow mess up your system.
cyrus-imapd is NOT started using an init script named imap, but it's name is cyrus.

Please have a look at /usr/share/doc/packages/cyrus-imapd/README.SuSE
and /etc/sysconfig/postfix (POSTFIX_MDA)
and /usr/share/doc/packages/cyrus-imapd/doc/index.html
and http://acs-wiki.andrew.cmu.edu/twiki/bin/view/Cyrus/WebHome

for more details.
Comment 6 Martin Jost 2005-11-03 19:53:32 UTC
Yes and that solved my last problem (the one in [...])
But still I think the points before this one are valid problems - aren't they ?
Comment 7 Carsten Hoeger 2005-11-07 13:32:05 UTC
When you want to use cyrus-imapd, or other software, that uses sasl, you have to install the needed sasl plugins (cyrus-sasl itself is part of the base system and therefor always installed). The perl-Cyrus-* packages are automatically selected and installed when you install cyrus-imapd.

And yes, one can whole books around cyrus-sasl and cyrus-imapd, I agree.
I'm not sure how I can help you here.

So basically I agree with you (missing/rare documentation), but this current bug is about "something not working", which is not the case, so I closed it.