Hello shon, s> that did the trick. was wondering though...how would one know that s> if it isn't in the documentation? i don't really know postfix all s> that well...so i am at a disadvantage there. also, how could s> setting that local_recipient_maps affect other users?
Well... I found out how to do the local_receipient_maps from a Postfix web page, on spam filters... just a few weeks ago! I'd even asked here how to do it, with no responses. Please note that I *do* have the Postfix book by Blum (Sams Publishing), and it glosses over a LOT of parameters. local_receipient_maps is MENTIONED. The example given is to take the unix passwd file, which is the default in any case. s> my system is a shared production/test system. i know that is bad s> practice, but its all i have to work with. so my users are straight s> postfix/courier-imap users with maildir while i am testing dbmail s> and have to use the same postfix as i use in production. just s> thought i would clear up where i am coming from here. Our first system was brought up with two domains that had no users at the time. Once it settled a little, I added a couple other low-volume domains. Over Christmas 2001, we cut all but one domain over, and that domain was eventually switched using a separate server (different filtering requirements). It is possible to set up postfix to only do certain domains through dbmail - simply set the transport for the "test victims" to dbmail, while leaving the others to the default transport. The problem comes with running POP3 and IMAP, since the "normal" POP3 and IMAP daemons have to run at the normal ports. The solution is to tell dbmail-pop3d and dbmail-imapd to run at alternate ports during the testing phase. It is also possible to have different postfix servers running at different IPs within the same physical server, and have the dbmail daemons use the standard ports on the alternate IPs. This is something our new mail server will do... so I only have to have one physical box handling all the different combinations of spam filtering our clients want/need. It's important, I think, to have the Blum Postfix book, as a first reference. Blum gets verbose about what he feels are the "important" aspects of getting Postfix up and running "right", and he covers getting MySQL support compiled in... although his command line doesn't work on a Mandrake install, because of where MySQL's development stuff is loaded. Later this weekend, I'll dig out a copy of my master list of "dbmail and postfix", update it to include the local_receipient_maps, and post it again to the list. I'll also see if I have a copy of the information on getting Postgres support into Postfix - I didn't write it, and I didn't need it, and I don't always keep copies of such things... B-) Perhaps a Postfix HOW-TO could be added to the dbmail 1.01 distribution tarball? Hint, hint.... -- Jeff Brenton President, Engineered Software Products, Inc http://espi.com Questionable web page: http://dididahdahdidit.com Liberalism grants you the freedom to advocate any idea*. * Please see http://www.dididahdahdidit.com/except.php for a current list of exceptions
