Rad! This is awesome. Thanks! Ya'll just chopped my system load by 19.5 times :-)
Now if I can get that new MX record propagated without Network Solutions destroying the zone again... we discovered that their creepy '60-days-since-a-change' policy about transferring domains (to, say, Joker.com, who has NEVER screwed me over in 3 years dealing with them) is set up to combat customers abandoning their incompetence... Do I deal with our ISP's badly-run BIND servers, or do I roll the dice and hope NSI does not obliterate all nameserver entries for our domain when I try to promote my djbdns-run primary nameserver to the helm? Grrrr.... do other people have problems *this* bad with NSI? You guys rule, BTW. DBmail was an elegant solution to a difficult problem and I'd have had to hack up something horrible in Perl if it hadn't existed. Now I can concentrate on integrating notification of new mail with phpbb, cc-to-email for chat logs from the board, etc. I'll make patches/add-ons for other people who might be running DBmail on a community site available as often as I am able to write them :-) Quoth Jesse Norell: > > > dbmail-adduser f [EMAIL PROTECTED] '!cat > /dev/null' > > > > Anyways, if I didn't want to re-map /etc/postfix/transport to only > > accept dbmail incoming for certain users, could I somehow alias > > [EMAIL PROTECTED] to /dev/null from within dbmail? My > > /etc/postfix/transport file is about to have another 1000 lines added to > > it otherwise :) > > > -- > Jesse Norell > jesse (at) kci.net > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail -- "It's just a job. Grass grows, birds fly, waves pound the sand. I just beat people up." --Muhammad Ali
