Re: mail-config?
[EMAIL PROTECTED] (Donovan Baarda) writes: Though I use uw-imapd instead of Courier. The general consensus is Courier is better, but I went with uw-imapd because it was lighter, and I had legacy non-Maildir mailboxes. Courier is nearly 1MB installed including ssl and support packages, compared to 350K for uw-imapd-ssl. Courier uses a seperate authdaemon and serverdaemon, whereas uw-imapd uses the normal inetd. Courier looked like overkill for my system. But how big are UW's c-client library files? I'm pretty sure that, including the protocol libraries, uw-imap ends up being larger than courier. -- Brian Nelson [EMAIL PROTECTED]
Re: mail-config?
On Fri, Aug 02, 2002 at 12:12:43AM -0400, Brian Nelson wrote: [EMAIL PROTECTED] (Donovan Baarda) writes: Though I use uw-imapd instead of Courier. The general consensus is Courier is better, but I went with uw-imapd because it was lighter, and I had legacy non-Maildir mailboxes. Courier is nearly 1MB installed including ssl and support packages, compared to 350K for uw-imapd-ssl. Courier uses a seperate authdaemon and serverdaemon, whereas uw-imapd uses the normal inetd. Courier looked like overkill for my system. But how big are UW's c-client library files? I'm pretty sure that, including the protocol libraries, uw-imap ends up being larger than courier. I was using the installed sizes as reported for the packages. In the case of uw-imapd, there were no dependancies that were not already installed on my system so I did not include them; libc-client-ssl2001, libc6, libpam0g, libssl0.9.6, openssl. For courier-imap-ssl, there were several packages that I would have to install just for courier support so these were included; courier-imap, courier-ssl, courier-base, courier-authdaemon. If you follow all the dependancies, courier-imap-ssl includes all the dependancies of uw-imapd except libc-client-ssl2001, which is 913kB... Hmm, looks like you are right... the only things on my system using libc-client-ssl2001 is uw-imapd-ssl and ipopd-ssl. If you look at a combined courier-pop-ssl+courier-imap-ssl vs ipopd-ssl+uw-imapd-ssl, they come out pretty much the same, with courier perhaps being slightly in front. However, I still feel a little uneasy about running a seperate authdaemon and serverdaemon just for pop/imap. -- -- ABO: finger [EMAIL PROTECTED] for more info, including pgp key --
Re: mail-config?
Hello! El jue, 01-08-2002 a las 22:44, Donovan Baarda escribió: ... courier-ssl, courier-base, courier-authdaemon. If you follow all the dependancies, courier-imap-ssl includes all the dependancies of uw-imapd except libc-client-ssl2001, which is 913kB... ... However, I still feel a little uneasy about running a seperate authdaemon and serverdaemon just for pop/imap. ... If you worry about used space and running lots of different software consider qmail and pop3 to get mail off to the local network. It does also work very well with dial-up lines, usind maildirsmtp. You get all parts from one provider and the programs are astonishing small. Best regards, Jorge-León
Re: mail-config?
Hi, For me a mix of qmail and fetchmail worked beautifully until I got a static (at which point fetchmail was no longer required). I did it all with one machine but if you really want you could use two (though I don't see the point). Fetchmail would retrieve the messages when connected and qmail would handle the delivery. All clients would then connect to that box and retrieve their mail. Hope this helps, Todd On Thu, 2002-08-01 at 16:02, [EMAIL PROTECTED] wrote: Hi Debian people. reading this list for a few weeks I want to put foreward this mail-question. What should I install to get mail to work? I have a small network: -1 debian gateway -2 debian boxes -4 Win98 PC (sorry, the kids are teached at school with word, excel etc.) At the moment one of the Win98 collects all the mail through the debian-gateway. What I want is that the gateway collects the mail from the ISP every time the dial-in connection gets up and every PC collect its mail from the gateway (running iptables) when they question the gateway for it. The gateway is NOT running as a DNS-server and uses NAT. What software needs to be installed on each machine? exim or postfix on the gateway? 1 debianbox runs kde, is this sufficient for collecting and sending mail? 1 debian box runs only bash/csh. What do I put here. What should be configured/changed on the WinPC's. In short. I don't ask how to configure exim/postfix/whatever but only what software to put where. Thank you all for your patients and help. Frank. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mail-config?
What should I install to get mail to work? I have a small network: -1 debian gateway -2 debian boxes -4 Win98 PC (sorry, the kids are teached at school with word, excel etc.) Frank. I'd suggest Postfix/Courier IMAP. If you have the mail hosted elsewhere on an POP or IMAP server then add fetchmail to get the mail and dump it into postfix. The clients should be able to handle logging into your imap to use their mail. If you have mail directed to you then you'll probably have to setup DNS/Postfix/IMAP. I'd also suggest procmail just so each user can do what they want with their own mail delivery. Cheers, -- Lance Levsen, Systems Administrator, PWGroup - Saskatoon
Re: mail-config?
On Thu, Aug 01, 2002 at 02:49:25PM -0600, Lance Levsen wrote: What should I install to get mail to work? I have a small network: -1 debian gateway -2 debian boxes -4 Win98 PC (sorry, the kids are teached at school with word, excel etc.) Frank. I'd suggest Postfix/Courier IMAP. If you have the mail hosted elsewhere on an POP or IMAP server then add fetchmail to get the mail and dump it into postfix. The clients should be able to handle logging into your imap to use their mail. ditto. Though I use uw-imapd instead of Courier. The general consensus is Courier is better, but I went with uw-imapd because it was lighter, and I had legacy non-Maildir mailboxes. Courier is nearly 1MB installed including ssl and support packages, compared to 350K for uw-imapd-ssl. Courier uses a seperate authdaemon and serverdaemon, whereas uw-imapd uses the normal inetd. Courier looked like overkill for my system. If I was starting from scratch, I'd probably go with Maildir and Courier because of it's glowing reports. If you have mail directed to you then you'll probably have to setup DNS/Postfix/IMAP. I'd also suggest procmail just so each user can do what they want with their own mail delivery. ditto. For DNS I'm using pdnsd, which is a light caching dns proxy with persistant cache contents so it can serve cached DNS contents from bootup without bringing up a link. It has good support for casual dialup, though I'm actually using it for a perm link. The other thing it does that is nice is it can serve up the contents of /etc/hosts via DNS, allowing you to very simply create your own private DNS system, ideal for local masq'ed networks. -- -- ABO: finger [EMAIL PROTECTED] for more info, including pgp key --
