Hanks again, Here's my qmailctl stat:
[EMAIL PROTECTED] ~]# qmailctl stat imap4: up (pid 1799) 24640 seconds imap4-ssl: up (pid 1824) 24640 seconds pop3: up (pid 1806) 24640 seconds pop3-ssl: up (pid 1797) 24640 seconds send: up (pid 5209) 23679 seconds smtp: up (pid 4921) 23796 seconds spamd: up (pid 1816) 24640 seconds imap4/log: up (pid 1812) 24640 seconds imap4-ssl/log: up (pid 1809) 24640 seconds pop3/log: up (pid 1808) 24640 seconds pop3-ssl/log: up (pid 1798) 24640 seconds send/log: up (pid 1810) 24640 seconds smtp/log: up (pid 1805) 24640 seconds spamd/log: up (pid 1807) 24640 seconds Does this show everything is up? I added the extra stuff to the tcp.smtp file and did the rebuild command and it all went ok but a tail -f on the current log doesn't look much different... Is there a place I can see what services I should have running and if not how I can get them running? Thanks Si <<<getting far too close to beer time now>> > -----Original Message----- > From: Jake Vickers [mailto:[EMAIL PROTECTED] > Sent: 23 December 2005 14:51 > To: [email protected] > Subject: Re: [qmailtoaster] Backup MX > > Simon Jones wrote: > > >Here's the rpm query: > > > >[EMAIL PROTECTED] ~]# rpm -qa | grep toaster > >| sort > > > > > > > Hmm. All the packages seem like they're there, are they all running? > (qmailctl stat). If they are, you may want to change your > tcp.smtp file to read like the example i sent you. Right now > you're not scanning emails for spam/viruses without the > simscan portion. You're also not limiting the recipients by > not having the chkuser options in there. > Obviously you don't HAVE to use them. > > >As for the backup mx: > > > >The problem is that since the backup server will always > accept mail for > >any domains listed in its accepted relay file (so it WILL > relay if the > >primary goes down) I only want it to relay under these > circumstances - > >reason being that the backup can be used as a spam gateway for > >dictionary attacks even if the primary is online, the relay > server does > >not know if [EMAIL PROTECTED] is a valid address, only the primary > >knows this because that is where the account is specified. > > > > > Okay, I understand a little better now. The short answer is > that unless you move to a cluster-type setup there's no easy > way to do this. I've begun looking into modifying the > Toaster package to a "cluster-toaster" > package, but this is a spare-time thing for me so it will be a while. > What I have done on my systems, (1 main MX, 1 or 2 backup > MX's depending on the domain) is this: > Set the queuelifetime of 10800 in the main MX (3 hours), and > backup MX's have a queuelifetime of the 7200 (2 hours). > Backup MX checks to see if Main MX is alive (bash script) > every 45 seconds. If it is, continue as normal. If it's NOT, > then the backup MX's change their queuelifetime to 259200 (3 > days) and reload qmail for the change to take. This makes the > backup MX's hold the emails for 3 days while I get the main > back up and running. > This serves 2 purposes - it keeps my queuelifetimes low in > normal operation, so mail bounces are processed in a timely > manner (letting the users know they misspelled a name or > whatever within 3 hours), and gets the spam that is stuck in > queue out in a timely manner. If the main MX goes down, it > takes action to hold the emails for 3 days which gives me > plenty of time to either get the main server back online (or > rebuilt) or log into them and change the queuelifetime to a > longer period of time if it's needed. > Sure, spam gets stuck in the queue (my backup servers stay at > a constant 50-60 messages in the queue), but they get dumped > out in a timely manner > (2 hours). In the event the main MX is down, I'm not > concerned with spam at that time, honestly. The impact of the > backup MX trying to deliver those messages to the main MX is > minuscule, so I don't worry about it. > The only real way to get around it would be to go with a > clustering system, like the one Bill Shupp outlined > (http://shupp.org/maps/ispcluster.html) > Hope that helps some. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > --- > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.371 / Virus Database: 267.14.5/212 - Release > Date: 23/12/2005 > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
