SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Does anyone have info in regards to installing Cyrus-IMAPd on Slackware?
I've been through all the HOWTOs, and all the FAQs I can find, and I'm having a hard time getting everything to play right on my Slack 12.2 system.
I get to the point where I am able to imtest accounts and get that to successfully pass, however I am still unable to connect to the service over port 143, and it reports that it is listening on that port.
Anyone have any advise about getting Cyrus-IMAPd to run on Slackware?
I have Cyrus IMAPD running on my Slackware home server for some 5 years now, and I simply love it. With the sieve daemon you get server-side email filtering for free.
I never wrote a proper SlackBuild or installation instructions for it though. Setting sendmail up to deliver emails to cyrus is not trivial either. Does the server receive emails yet?
If your server does not listen on port 143 then have you checked what is running on that port? As root run
Code:
netstat -panel | grep :143
I have the cyrus "master" process listening there.
Also, did you build the server with shadow support? If not, it will not be able to authenticate your account against Slackware's shadow database.
If you have them can you post your build commands (the configure command especially) and the content of /etc/cyrus.conf and /etc/imapd.conf ?
I have Cyrus IMAPD running on my Slackware home server for some 5 years now, and I simply love it. With the sieve daemon you get server-side email filtering for free.
I never wrote a proper SlackBuild or installation instructions for it though. Setting sendmail up to deliver emails to cyrus is not trivial either. Does the server receive emails yet?
If your server does not listen on port 143 then have you checked what is running on that port? As root run
Code:
netstat -panel | grep :143
I have the cyrus "master" process listening there.
Also, did you build the server with shadow support? If not, it will not be able to authenticate your account against Slackware's shadow database.
If you have them can you post your build commands (the configure command especially) and the content of /etc/cyrus.conf and /etc/imapd.conf ?
Eric
Sure, I'll post my build info when I get home later today, as well as the /etc/cyrus.conf and /etc/imapd.conf files.
Yes, the master process (cyrus master, and postfix master for that matter) was running. Running the netstat it showed that the cyrus master was listening on 143.
Postfix is delivering mail, after a quick reconfiguration of the master.cf.
I was able to initially telnet to the imap port, and it showed the proper connection string that you'd expect IMAPd to show. However, that only seemed to work once, after restarting the process. I would have to restart the process again, to be able to get that to show up again.
I guess I need to do even more troubleshooting on my end, I will try throwing the login commands and such, via telnet and see if it gives me an error. I simply tried to connect to it using a imap client, like thunderbird, and was getting errors trying to connect.
I will post relavent info when I get home and back on the system, and I'll try more troubleshooting by throwing in some imap commands via telnet and find out any error messages I'm getting.
Also, the other thing I was curious about if I was using the proper pwcheck_method as shadow, or should it be saslauthd? From what you said, it looks like it should be shadow.
Also, the other thing I was curious about if I was using the proper pwcheck_method as shadow, or should it be saslauthd? From what you said, it looks like it should be shadow.
Thanks for the info.
You are right. Slackware's saslauthd process uses shadow authentication. This is what my Cyrus IMAP server uses too; my /etc/imapd.conf file has these lines:
You are right. Slackware's saslauthd process uses shadow authentication. This is what my Cyrus IMAP server uses too; my /etc/imapd.conf file has these lines:
If the imtest program shows that your account can login, perhaps you have not yet created the account's mailbox?
Eric
Ok, here is everythiing relavent that I have configured as of right now. . . Please note that they may have looked like what your suggesting at one time, but I probably changed it trying to get it to work.
/etc/imapd.conf:
configdirectory: /var/imap
partition-default: /var/spool/imap
admins: cyrus root
srvtab: /var/imap/srvtab
allowanonymouslogin: no
sasl_passwd_check: shadow
allowplaintext: yes
sasl_mech_list: PLAIN LOGIN
/etc/cyrus.conf is pretty much just the normal.conf with the package, I just commented out the pop3 and pop3s
Ok, here is everythiing relavent that I have configured as of right now. . . Please note that they may have looked like what your suggesting at one time, but I probably changed it trying to get it to work.
/etc/imapd.conf:
configdirectory: /var/imap
partition-default: /var/spool/imap
admins: cyrus root
srvtab: /var/imap/srvtab
allowanonymouslogin: no
sasl_passwd_check: shadow
allowplaintext: yes
sasl_mech_list: PLAIN LOGIN
/etc/cyrus.conf is pretty much just the normal.conf with the package, I just commented out the pop3 and pop3s
Ok, I changed /etc/imapd.conf to look like:
configdirectory: /var/imap
partition-default: /var/spool/imap
admins: cyrus root
srvtab: /var/imap/srvtab
allowanonymouslogin: no
sasl_passwd_check: saslauthd
allowplaintext: yes
sasl_mech_list: PLAIN LOGIN SHADOW
When I telnet in to port 143, i type: login user1 <password>
and I get "login BAD Please login first". user1 exists in /etc/passwd (and /etc/shadow for that matter )
I also forgot to mention that I created (cm user.user1)
Any suggestions?
Last edited by MikeDawg; 12-30-2008 at 09:30 PM.
Reason: modified login statement -- Added info about mailbox being created.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.