Martin, Eric wrote:

[...] I own two domains, and I want to have email from those domains delivered to my server.

The first question is: will your provider allow incoming smtp to your address? If so, you can set up MX pointers to your server... unless it's dynamic. In which case, you could set up with one of the dynamic dns providers, and update it with a short TTL. In which case, everything shulud work, although some systems will reject (RBL) mail originating from your address simply because it IS dynamic. Back in Phoenix, I was set up (with Cox as my provider) with a server at the house directly accepting mail from outside. It was great fun, but due to the worm/virus outbreaks, and various threats from the community at large, they began blocking inbound smtp, and eventually outbound as well. While this was certainly aggravating at the time, and I was annoyed they didn't bother to NOTIFY me of this change, in hindsight it's probalby just as well. I wound up going with a $2/mo. offsite hosting outfit, and have to say my aggravation levels are greatly reduced (not to mention I can down my server and not worry about losing stuff... a real advantage while moving last summer.) It's also nice now that I'm experiencing the not-quite-so-steady power in my new home area. Mail for my domains goes to the hosted server (my MX), and I pull it down at regular (5 min.) intervals using fetchmail via POP3. I run postfix locally, but relay through my provider's (charter) smtp server for outbound to avoid sudden surprises if ToS changes. I've got accounts on the hosted server for my users (family), plus a "wildcard" that I can use to break things out locally via aliases. It's not as sexy as having incoming mail handled directly, but mail for my domains "is delivered to my server" for local reading via POP/IMAP, and I do have control over the local outbound (smtp). I don't have spammers knocking at my server constantly, and I have to admit I don't miss the headaches of an exposed server (though the learning was fun). I'm not sure if that's what you had in mind, but it does work well.

I have Postfix in mind, I've heard it's pretty easy but I'm obviously not set on it.

I used postfix throughout, and found it quite easy to set up and administer. Handling multiple domains locally was no big deal, jsut a matter of setting the "mydestination" option. Again, specifics may vary depending on what your provider allows/requires.

I'd also like to include spamassassin, and antivirus (clamav probaly...)

I do run spamassassin via local delivery, but obviously the stuff's made it onto my server by then. I don't run any MTA-level blocking, due to the setup described above. It does keep the crud out of my family's inboxen though (and quite deftly, I might add.) I also chain bogofilter and spamprobe, experimenting with variations on bayes. I'm on the spamassassin list, and there ways to get MTA-level integration, if you desire. I'm running several anti-virus (3 - bitdefender, f-prot and clamav) in line via procmail on delivery. Each detects some the others miss (depending on the hour.) Again, this could be integrated at a higher level. You might check out amavis or mailscanner. I've got anomy sanitizer as a 3rd level of defense, stripping off active content and defanging (web bugs and the like), for selected accounts. I set this up all as discrete steps, and had no real headaches. The documentation for each package (postfix, fetchmail, procmail, spamassassin, clamav) was sufficient. I run my own linux firewall, but I can understand why some folks prefer to by an appliance. I host my mail server off-site, but have done the "studly mail admin" bit as well. Just a question of trade-offs for a home/hobby system, and how much time you want to spend on it. - Bob

Pete Wason wrote:

[...] I've been planning on replacing sendmail (which I'm not using anyway) on my rh8 system with tcpserver/qmail, in an attempt to divorce myself from my vhost which I no longer use for vhosting, but still get all my email through (and pay $20/m for!).

I thought about going with a vhosting setup for "the control", but work keeps me busy enough as of late, so my lil' $2 mail/web hosting setup is fine for now. It sounds like you've got two options: 1. Move to something similar, but cheaper. Go with a cheap outfit that'll host SMTP/POP for you, and set that as the MX for your domain. 2. Set up a mail server at home (off your cable modem) and hope that your provider doesn't changes ToS on you when you're out of town for a week with no connectivity. :)

I'm running dynamic over cable using everydns, btw. --

I set up my domain with dyndns.org using their "customdns" a bit over 1 1/2 years ago, and have been very happy. I point www and MX at the hosting outfit with a typical TTL, and my dynamic addresses using a shorter TTL. If I'm changing providers or hosting outfits, I just need to remember to set the TTLs shorter prior to the cutover. I've done it twice now, and it's worked very well.

I assume you might have the same general advice for me...

In terms of hosting "important" stuff offsite, yeah. Again, really a matter of personal priorities. I am into network stuff, so wouldn't want to cop out and buy a Linksys router, but I have no problem shoving email stuff (which I don't find as sexy) to someone else to handle for me for a few bucks.

[Again, if there's anyone near Sutton who feels like stopping by and putting me out of my "misery", you're welcome to do so...]

I don't know qmail, but have heard good things about it. I use postfix myself, and it has no problems handling local requirements for my two domains, simply using fetchmail to poll my hosted mail via POP3. tcpserver looks interesting, but I don't understand how you envision using it. It will depend on what you decide to host offsite. My "real" presence is my hosted setup. I have a couple of dyndns entries for my home systems, with the linux router/firewall redirecting things internally. Do you still plan to have smtp/MX hosted offsite? - Bob

Chuck Homic wrote:

[...] I hate to be Mr. Obvious, but... tcpserver is how qmail listens on the network. tcpserver waits on port 25 and spawns qmail-smtpd when a connection is made.

Ah, OK. Like I said, "I don't know qmail!" :) So it's tcpwrappers with ability to redirect to other hosts as well, eh? - Bob