Re: [swinog] Mail server - Unix
Jeroen Massar wrote: dns was not really questioned, but I would prefer djbdns (+patches, again) or bind. Patches, patches, patches. Bind9 is fine (and actually what I usually use) but pdnsnds are simply faster, thus for scalability I would go for those, then again it depends on ones needs. Given the potentially high DNS traffic (all those xBL lookups), a dedicated caching DNS resolver may make sense. Additionally, you should consider running a local rbldnsd for mirrored zones (proxying from the resolver to rbldnsd). - amavis + clamav Spamassassin using milter inline in postfix Seem both to be just 'the standard antivir and antispam' solution There is afaik nothing better, especially in combo with: Detection rates of ClamAV are pretty low. If you want to advertise virus protection as a feature, you may want to integrate at least one additional scanner. -- Matthias -- http://www.dnswl.org/ - Protect against false positives ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] Mail server - Unix
Hello! Just wanted to ask what setup you use or recommend for large scale sites (~10k users, some hundreds of imap(s), smtp, webmail connections, about 5-10 mails incoming and outgoing per second): - what smtpd? why? - what mail retrieval solution for which protocol? - if you offer webmail, what do you use? - it should be *nix software, preferable FOSS (free and open source software) - Which Antispam / Antivirus protection do you use? And what is the success rate? I'm personally deep into qmail+patches+patches+patches of patches plus courier and dovecot. The problem with qmail is that you need either a big patchset or a once patched setup and reuse that. Plus qmail really has some not-so-nice bugs. On the other hand, there seems to be no MTA out there, that can be configured so easy like qmail (ever created a mail addr with cp .qmail-template .qmail-domain-user with another MTA?). Oh, btw, froehliche Weihnachten Nico -- ``...if there's one thing about Linux users, they're do-ers, not whiners.'' (A quotation of Andy Patrizio I completely agree with) signature.asc Description: Digital signature ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Mail server - Unix
Nico -telmich- Schottelius wrote: Hello! Just wanted to ask what setup you use or recommend for large scale sites (~10k users, some hundreds of imap(s), smtp, webmail connections, about 5-10 mails incoming and outgoing per second): - what smtpd? why? - what mail retrieval solution for which protocol? - if you offer webmail, what do you use? - it should be *nix software, preferable FOSS (free and open source software) - Which Antispam / Antivirus protection do you use? And what is the success rate? I'm personally deep into qmail+patches+patches+patches of patches plus courier and dovecot. The problem with qmail is that you need either a big patchset or a once patched setup and reuse that. Plus qmail really has some not-so-nice bugs. On the other hand, there seems to be no MTA out there, that can be configured so easy like qmail (ever created a mail addr with cp .qmail-template .qmail-domain-user with another MTA?). That all depends on what you are used to. The mini-isp setup: - Debian unstable - nsd or pdns as authoritive dns - pdns as a recursing dns - postfix for SMTP + optional STARTTLS + Submission - amavis + clamav Spamassassin using milter inline in postfix - http://saupdates.openprotect.com/ to update SA. - dovecot for IMAP-SSL - squirrelmail or Horde IMP as a webmail frontend or when living on the alpha side: hula (hula-project.org) To make it all configureable one can go for a MySQL backend or write scripts which can generate the configs. MySQL (or other SQL backend) is prolly the way to go though. Yet again, it all depends on what you need and what you are used to... Greets, Jeroen signature.asc Description: OpenPGP digital signature ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Mail server - Unix
we've been operating ISPMan+openldap+postfix+Cyrus+horde, but then moved our services to Plesk. Having looked back, I'd still go again with Plesk. It saves a lot of time, and normally a sysadmin's working time is more expensive than the software license. It has its limitations and unconveniences, but in general it's a great product. A strong advice is to put a greylisting server in front of it on a separate machine (might be a virtual machine). Besides, I studied together in the same University with Sw-Soft's core team ;-) regards, stan --- Nico -telmich- Schottelius [EMAIL PROTECTED] wrote: Hello! Just wanted to ask what setup you use or recommend for large scale sites (~10k users, some hundreds of imap(s), smtp, webmail connections, about 5-10 mails incoming and outgoing per second): ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Mail server - Unix
Nico, For domain toaster of that size, qmail-ldap is a nice solution, but software seems to be orphaned now, as soon as some major SMTP enhancements come in I am afraid qmail will slowly die out. As some have already mentioned, the Maildir format used by Qmail is suboptimal for handling large boxes, expecially with IMAP, I would strongly advise to use IMAP daemon which features caching mechanisms, such as Cyrus IMAP. Cyrus is great plus you get Sieve server side filtering but it is a challenge to get it working with Qmail, especially with virtual boxes. If you go with some non-caching IMAP daemon like courier, then it might make sence to setup IMAP Proxy too which would keep alife the IMAP connections for let`s say 2 min and reuse it for same user, so new IMAP processes do not have to be spawned and mailboxes rescanned every time web mail refreshes. Of course this hogs memory but is useful sometimes, especially if users have thousands of mails. Frontend: Squirrelmail. By far most powerful web based MUA out there IMHO. Also very easy to ehnance, we wrote a LDAP control panel to it for example, so users can setup aliases, forwarders and away messages themselves. (Contact me offlist if you want it, I can send it to you). Cheers Kirill -- Kirill Ponazdyr Technical Director Codeangels Solutions GmbH Tel: +41 (0)43 844 90 10 Fax: +41 (0)43 844 90 12 http://www.codeangels.ch http://www.codeangels.com Hello! Just wanted to ask what setup you use or recommend for large scale sites (~10k users, some hundreds of imap(s), smtp, webmail connections, about 5-10 mails incoming and outgoing per second): - what smtpd? why? - what mail retrieval solution for which protocol? - if you offer webmail, what do you use? - it should be *nix software, preferable FOSS (free and open source software) - Which Antispam / Antivirus protection do you use? And what is the success rate? I'm personally deep into qmail+patches+patches+patches of patches plus courier and dovecot. The problem with qmail is that you need either a big patchset or a once patched setup and reuse that. Plus qmail really has some not-so-nice bugs. On the other hand, there seems to be no MTA out there, that can be configured so easy like qmail (ever created a mail addr with cp .qmail-template .qmail-domain-user with another MTA?). Oh, btw, froehliche Weihnachten Nico -- ``...if there's one thing about Linux users, they're do-ers, not whiners.'' (A quotation of Andy Patrizio I completely agree with) ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
