Installing Cyrus-imapd on Slackware
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? Thanks in advance. |
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 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 |
Quote:
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. Thanks for the info. |
Quote:
Code:
sasl_pwcheck_method: saslauthd Eric |
Quote:
/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 /usr/lib/sasl2/smtpd.conf: # Global Parameters log_level: 3 pwcheck_method:saslauthd mech_list:login plain mech_list: PLAIN LOGIN a netstat -tnlp provides: tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 11858/master |
Quote:
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? |
Quote:
Code:
sasl_passwd_check: shadow That may be worthwhile changing. Eric |
Quote:
configdirectory: /var/imap partition-default: /var/spool/imap admins: cyrus root srvtab: /var/imap/srvtab sasl_pwcheck_method: saslauthd allowanonymouslogin: no sasl_passwd_check: saslauthd allowplaintext: yes sasl_mech_list: PLAIN LOGIN SHADOW Do you mind showing me your whole /etc/imapd.conf file? |
Quote:
Code:
configdirectory: /var/lib/imap |
Man, I have been working on this off an on now, for the past 3 months, and I still can't seem to get it working right.
I would like to graciously implore you to get a slackbuild built for this, and if you can thrown up to the folks at slackbuild.org . . . I don't know why I can't overcome this stupid obstacle. Any help would be appreciated. |
Quote:
He is the folks at slackbuilds.org |
Quote:
|
|
All times are GMT -5. The time now is 11:56 PM. |