David Milholen wrote: > So, should I upgrade my whole package? or just the qmail part?
That depends on how critical the server is. The development packages are generally very stable, but there is still a (slightly) higher risk of running into a problem with them than with the stable ones. If you're upgrading from stable, I would do the whole toaster. I think that EE's planning on rolling the devel packages over to stable w/in the next week or so. He might have a better recommendation. > Maybe it will give me a leg up to install the large server patch. > I really think i need it because I have the one customer that has a legit > business for sending about 6000 msgs at one time. I'm not familiar with the large server patch. Anyone care to elaborate? > I am even thinking of setting up another dedicated qmail server for > failover purposes. That's always a good idea for a critical server. You can see http://wiki.qmailtoaster.com/index.php/QMT_Failover_replication_Setup for one way to do this. I'm presently working on an automated failover setup that uses heartbeat. >> David Milholen wrote: >>> I emptied my blacklists file and all is well but may have issues with >>> spam >>> like I did not before:( >>> >> You might try the loose blacklist from the (latest, 0.2.3-1.3.5) >> qmailtoaster-plus package. It's been working nicely for me for several >> weeks >> now (thanks to Vince). >> >> It appears that your send problem is RBL related. The qmail-toaster >> package >> in development (beginning with version 1.3.8 if I'm not mistaken) has a >> separate MSA (qmail-smtp) instance running on port 587 (the submission >> port) >> for sending emails. This should fix your problem permanently. >> >> -- >> -Eric 'shubes' >> -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
