![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Mon, 2 Feb 2004, Mark J. Dulcey wrote: > Well, I decided to take matters into my own hands and rebuild the imap > server package (the standard one supplied by SuSE, which is UW IMAP, not > courier or cyrus). I started with the SuSE SRPM, made the changes to > allow cleartext password login on non-encrypted connections, and > installed it. This imap uses the standard mailbox file format, so it has > the usual file locking limitations. (Mostly, it means that if you have > an IMAP client open somewhere, and you also try to run a shell on the > mail server and run Pine, Pine won't be able to expunge deleted messages > from the mailbox.) > > To keep it from being a huge security hole, I modified the xinetd > configuration for imap and pop3 (also handled by the same package). > Unencrypted imap and pop3 are only allowed from hosts on my own LAN, > including the mail server itself - that means that squirrelmail works > from anywhere, and all the usual clients work from here. If you're > outside the house, you have to use an encrypted connection (or use > squirrelmail to read your mail) - that limits your choice of clients, > but you can still get in. Next step will be to put the squirrelmail on > an https: virtual host to take care of that potential hole. > > I can send people the updated RPMs for imap and the changes to the > xinetd configuration if anyone wants them. Could you send me a copy of this? Thanks. -- DDDD DK KD The best way to get an answer on the internet isn't to ask a question, DKK D but to post an incorrect answer. DK KD DDDD
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |