List Info

Thread: Multiple hosts - where to run sieve?
Multiple hosts - where to run sieve?
user name
 2007-12-19 06:05:31 
Hi,

I think about multiple hosts in a (big) mail environment.

Host A:   dbmail-imap and dbmail-pop3
Host B:   postfix and dbmail-lmtp    (only for user, sends
mails to 
"outside")
Host C:   postfix (with spam and virus checks) and
dbmail-lmtp   (no 
user,  receives mails from "outside")
Host D:  MySQL Server

I assume, sieve has to run on each host running postfix?

Merry Xmas,
Uwe
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail
Re: Multiple hosts - where to run sieve?
country flaguser name
Netherlands		 2007-12-21 09:46:46 

  


  

    


I'm curious: Why do you designate A,B and C a function? In my opinion setting them all up in the same configuration would be way easier maintenance wise and gives you something very nice in return: redundancy. 



Also, machines can be used to their full potential and planning is much easier. If the load is too high structurally, you can easily setup another box. A separate MySQL would always be my choice, at least for dbmail data storage. I'd replicate the data relevant for postfix (domains, aliases, spam settings) to the other machines, not for reason of speed but for stability. At least mail can be queued or bounced when you cannot connect to your MySQL server.



You could for example use round-robin dns (rrdns) to split the load on pop/smtp and different mx records with the same priority for inbound smtp.




In case of emergency you can have a machine take over the IP address of a defective machine, and a virtually no-downtime setup can be reached. If you want to do that give every machine 2 IP's to start with, one for management, one for services.



As others have pointed out running sieve mail filteres is done on delivery to dbmail, timsieved can be ran near your pop/imap daemon. It's purpose is accepting changes in sievescripts from the users mail application and enter it into the db. It won't take a huge load 



As to avoiding scanning locally sent mail: I can't imagine why you'd want to do that. If you are providing an outgoing mailserver for users, I strongly suggest filtering it. Malware on a users computer could use your outgoing server as well. You don't want to get blacklisted now, do you? 

The only good reason (imo) for not wanting to scan outgoing mail is if you have an application that sends out big amounts of mail, that you *know* isn't spam (or you know is spam, but you don't care  )



Good luck!

Greetings, Casper
















On Wed, 2007-12-19 at 13:05 +0100, Uwe Kiewel wrote:



Hi,

I think about multiple hosts in a (big) mail environment.

Host A:   dbmail-imap and dbmail-pop3
Host B:   postfix and dbmail-lmtp    (only for user, sends mails to 
"outside")
Host C:   postfix (with spam and virus checks) and dbmail-lmtp   (no 
user,  receives mails from "outside")
Host D:  MySQL Server


I assume, sieve has to run on each host running postfix?


Merry Xmas,
Uwe
_______________________________________________
DBmail mailing list
 DBmaildbmail.org">DBmaildbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail





  

  
  
   
     
    






 [1-2]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )