greetings, (thanks to sandy for helping me to the point of getting the mail in and not loosing any post during the transition) as i am still in the process of getting my mail system configured, one of the reasons why i havent finalized my postfix configuration is because is my current priority is to get imap to work with postfix. ive tried imap-cyrus but deduced it was a bit too much as each time i create a user account, i would have to create a separate mailbox on cyrus, imap-courrier uses MailDir which is not my current option untill i get my hardware upgraded as MailDir is I/O intensive on the harddrive. so im trying to use the basic imap package. my prob is that after isntalling the package, i enabled the imap and pop under xinetd and then tried to telnet to port 110 and manually test functionality unfortunatelly the attempt fails as you can see bellow, any ideas why? btw this is the same with the imap port 143 telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK POP3 localhost 2004.89 server ready user XXXXXX -ERR Unknown AUTHORIZATION state command regards RP -- ___________________________ If computers were made in heaven, would they be perfect? ___________________________
RutePoint wrote:
greetings,
(thanks to sandy for helping me to the point of getting the mail in and not loosing any post during the transition)
as i am still in the process of getting my mail system configured, one of the reasons why i havent finalized my postfix configuration is because is my current priority is to get imap to work with postfix.
ive tried imap-cyrus but deduced it was a bit too much as each time i create a user account, i would have to create a separate mailbox on cyrus,
Cyrus is using a proprietary version of maildir, but it works pretty efficient.
imap-courrier uses MailDir which is not my current option untill i get my hardware upgraded as MailDir is I/O intensive on the harddrive.
so im trying to use the basic imap package. my prob is that after isntalling the package, i enabled the imap and pop under xinetd and then tried to telnet to port 110 and manually test functionality
Please post /etc/imapd.conf, especially the settings allowanonymouslogin: no defaultdomain: sasl_pwcheck_method: sasl_mech_list: Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
greetz
i wish there was some sort of imapd conf under etc, the only conf i see is
under xinetd.d
On 1/6/06, Sandy Drobic
RutePoint wrote:
greetings,
(thanks to sandy for helping me to the point of getting the mail in and not loosing any post during the transition)
as i am still in the process of getting my mail system configured, one of the reasons why i havent finalized my postfix configuration is because is my current priority is to get imap to work with postfix.
ive tried imap-cyrus but deduced it was a bit too much as each time i create a user account, i would have to create a separate mailbox on cyrus,
Cyrus is using a proprietary version of maildir, but it works pretty efficient.
imap-courrier uses MailDir which is not my current option untill i get my hardware upgraded as MailDir is I/O intensive on the harddrive.
so im trying to use the basic imap package. my prob is that after isntalling the package, i enabled the imap and pop under xinetd and then tried to telnet to port 110 and manually test functionality
Please post /etc/imapd.conf, especially the settings allowanonymouslogin: no defaultdomain: sasl_pwcheck_method: sasl_mech_list:
Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Regards -RP- ___________________________ If computers were made in heaven, would they be perfect? ___________________________
RutePoint wrote:
greetz
i wish there was some sort of imapd conf under etc, the only conf i see is under xinetd.d
Strange, you should have an /etc/imapd.conf file. Have you tried to set up imap in yast? Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
i selected the package from yast,
made sure that there werent any other imap or pop packages
then i had the imap installed,
after installing
i can find links
fom /etc/rimapd to /usr/sbin/imapd
from rpop3d -> /usr/sbin/ipopd
and when i look under
/usr/share/doc/packages/imap
i can find only these files
CONTENTS CPYRIGHT FAQ.txt README README.SuSE RELNOTES bugs.txt
drivers.txt imaprc.txt md5.txt naming.txt
in other words i missing more than one file, can the package be broken??
On 1/6/06, Sandy Drobic
RutePoint wrote:
greetz
i wish there was some sort of imapd conf under etc, the only conf i see is under xinetd.d
Strange, you should have an /etc/imapd.conf file. Have you tried to set up imap in yast? Sandy
-- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Regards -RP- ___________________________ If computers were made in heaven, would they be perfect? ___________________________
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-01-06 at 12:42 +0100, Sandy Drobic wrote:
i wish there was some sort of imapd conf under etc, the only conf i see is under xinetd.d
Strange, you should have an /etc/imapd.conf file. Have you tried to set up imap in yast?
No, that file does not exist for wu-imap, aka plain imap in SuSE. There is no need to configure it, it is "plug and play" :-p - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDvl+etTMYHG2NR9URAvvxAJ9gNamesuXsYs6JnAJup9jRBu017gCfWw7y HI2sEuodKlOn+2ZAPwJnSIs= =zkvL -----END PGP SIGNATURE-----
ok, since i will be facing compatibility and maintenance obstacles, i guess i have no option but to convert to MailDir format and use imap-courrier my question is, if i want to implement this in suse, what are the things i have to note, this is what i can think of, 1-create a MailDir under /etc/skel so that new accounts would autmatically get the maildir directory to reposit the incoming mail 2-onfigure postfix to use MailDir now the open questions are, how can i convert existing mails to maildir? and in general what are the various things i need to note to successfully migrate to MailDir format? -RP-
ok, since i will be facing compatibility and maintenance obstacles, i guess i have no option but to convert to MailDir format and use imap-courrier my question is, if i want to implement this in suse, what are the things i have to note,
Well not to disuade you but I just upgraded an old Debian system I was running which was using qmail, imap, spamd, clamav, dmail, procmail and squirrelmail for web access. This is just a home system for our own needs, but it lets me play. Getting all that stuff configured and working properly was a royal pain in the butt, but it did, and of course anytime I needed to update a version of things it was tying it all together that was the intensive process. I just upgraded to OpenSuse 10, the stock imapd, postfix, spamd, procmail, squirrelmail, and the antivirus scanner. I did not have to worry about maildir/mbox/spooldir or any of those somewhat "religious" views. I just had to create my own certificate, and tell the clients to use SSL, and setup squirrelmail to do the same. It was much much easier. My procmail recipes were about the same, and I got rid of having to deal with dmail to put in the right format after being processed by procmail. I would highly recommend going with the stock imapd and just enabling SSL and generating your own certificate to use it. If this is going over the internet then you are now encrypting stuff, definitely a good thing, and if this is on a private network then you probably have some control over the userbase. Just my two cents. Michael
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-01-06 at 14:43 +0200, RutePoint wrote:
since i will be facing compatibility and maintenance obstacles, i guess i have no option but to convert to MailDir format and use imap-courrier my question is, if i want to implement this in suse, what are the things i have to note,
The standard imapd package in SuSE works fine with no configuration at all for systems users, ie, those with a local account. You have, of course, to issue certificates as explained, because it is considered insecure to use plaintext password over non encrypted links. SuSE has removed that posibility since 8.2 - but if you insist, you can recompile the rpm with the appropiate option. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDvon5tTMYHG2NR9URAkarAKCTr0BpbW/gE7hBh4jR6zNg0TS4OQCdGpp8 eaMYCwOauUaJiTc6D22pS+k= =XtFL -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-01-06 at 12:46 +0200, RutePoint wrote:
so im trying to use the basic imap package. my prob is that after isntalling the package, i enabled the imap and pop under xinetd and then tried to telnet to port 110 and manually test functionality
unfortunatelly the attempt fails as you can see bellow, any ideas why? btw this is the same with the imap port 143
Yeap. Known and documented thing: | As of SuSE Linux 8.2, the IMAP mail daemon no longer allows plain text | passwords for unencrypted sessions. Plain text passwords are only | allowed in SSL-encrypted sessions. So instead you have to connect to ports: pop3s 995/tcp imaps 993/tcp Read /usr/share/doc/packages/imap/README.SuSE, and then continue with the article " Enabling SSL Sessions with the IMAP Mail Daemon" in the SuSE SDB. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDvlvztTMYHG2NR9URAj1CAJ40HZUWStx3hldndvBu6gy4cgPJUgCeM2a0 ecscCOjUf2/HRDBmmNfAgPY= =4qFi -----END PGP SIGNATURE-----
RutePoint wrote:
greetings,
(thanks to sandy for helping me to the point of getting the mail in and not loosing any post during the transition)
as i am still in the process of getting my mail system configured, one of the reasons why i havent finalized my postfix configuration is because is my current priority is to get imap to work with postfix.
ive tried imap-cyrus but deduced it was a bit too much as each time i create a user account, i would have to create a separate mailbox on cyrus,
imap-courrier uses MailDir which is not my current option untill i get my hardware upgraded as MailDir is I/O intensive on the harddrive.
so im trying to use the basic imap package. my prob is that after isntalling the package, i enabled the imap and pop under xinetd and then tried to telnet to port 110 and manually test functionality
unfortunatelly the attempt fails as you can see bellow, any ideas why? btw this is the same with the imap port 143
telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK POP3 localhost 2004.89 server ready user XXXXXX -ERR Unknown AUTHORIZATION state command
This issue has been on the list for some time. For several releases now Suse now, the uw-imapd had been compiled to only accept secure connections using SSL on port 993 (imap) and port 995 (pop3). Fortunately this is not too difficult, this article helped me immensely http://www.davidkrider.com/suse_8.2.php. See the part about setting up imap. I used the "right way" option. You will have to edit etc/xinetd.d/imap, paying particular attention to the "imaps" and/or "pop3s " if you want pop3. Works great, although I'm working on setting up cyrus on my new email server. Mostly to satisfy my own curiosity and see how another imap server works. You can also set up squirrelmail which I quite like for those ocasions where you don't have access to one of your own ocmputers, but any machine with internet and a web browser. Jim Flanagan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-01-08 at 12:55 -0600, Jim Flanagan wrote:
You will have to edit etc/xinetd.d/imap, paying particular attention to the "imaps" and/or "pop3s " if you want pop3.
Yast did that par very well for me, it has a xinet editor. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDwXgztTMYHG2NR9URAh6iAKCVcidt+pOD2z7Oa5zM2SCQMSjQCQCgixyX 0ga8J5SMJj6H7P2cpK+qqqo= =uk9H -----END PGP SIGNATURE-----
This issue has been on the list for some time. For several releases now Suse now, the uw-imapd had been compiled to only accept secure connections using SSL on port 993 (imap) and port 995 (pop3). Just for the record, it changed in 8.2, and it actually wasn't SuSE that changed it but uw-imap. I know since I recompiled the rpm (so all my users wouldn't need to change when i upgraded from 8.0), and during the build you must accept the risk or something like that, it actually
Jim Flanagan wrote: prompted for user input in the build process because they considered the build option to allow plain text passwords a security issue. Therefore, it wasn't a change in SuSE but a change in the program (for the better). I recently upgraded from 8.2 to 9.3, and now decided all my users needed to use pop3s. It is better, more secure, and if there is a security fix, I can just install instead of rebuild the rpm. -- Joe Morris Registered Linux user 231871
participants (6)
-
Carlos E. R. -
Jim Flanagan -
Joe Morris (NTM) -
michaell＠theletourneaus.net -
RutePoint -
Sandy Drobic