* Bjorn Mork <[email protected]>: > i have tried to answer your queris, (Please correct, if I am wrong in > understanding your question...) > > We do have multiple IBM Blade server with 2.4 Xeon + 16GB + NAS over iSCSI > protocol...... > > How many blades will be involved for such load....???
I would have to speculate and I won't because it would be bad advice. Instead setup a test machine and use the Postfix tools smtp-sink and smtp-source and the benchmark program "mstone" to simulate your usage profile. Find out within which limits you can run your setup safely (calculate about 30% extra load on top) on one machine and then find out how many machines you will need to serve your overall load. > Can you please suggest its logical architecture ??? I, personally, think running a pair of identical Postfix machines that can failover each other is a good thing. Those machines are backed up with another pair of fallback servers. Their job is to take and deliver any message that could not be delivered at first attempt from the primary pair. > > - What will be incoming traffic (average/peak)? > > > *its a assumption, that during peak hours avg 60k-70k pop session > expected... Just for the books: Postfix is not a POP server. POP access has a different load consumption profile than a SMTP server. Do you have any figures how many messages your users send via SMTP when they pick up message via POP? > * > > > * *- What will be outgoing traffic (average/peak)? > > > *May be same or can have more value than pop sessions.... > * > > > > - What mail management will/needs to be done? > > > *normal management like postfixadmin type...* > > > > - Anti-Spam? > > > *MailScanner + Spamassassin > * > > > - Anti-Virus? > > > * MailScanner + ClamAV > * I don't use MailScanner in combination with Postfix and I don't know how that combination performs and/or scales. It might be hard to get advice on this on the Postfix mailing list because running MailScanner with Postfix is not blessed - AFAIK MailScanner bypasses Postfix queue management and uses Postfix internal API, which might change without notice leaving your system unusable after an update. > > - Other Policies? > > > *mostly default values, but major reqirement is quotas , few > accounts with 2 GB and few with 100 GB.....* You probably want a mechanism that can tell a recpients quota _during_ the SMTP session and rejects the message immediately if a mailbox is over quota, instead of accepting the message, trying to deliver it, failing and bouncing it. That would eat to many ressources when you need to watch out you don't waste 'em. > > - server side mailbox filtering > > > *I think you are taking about squiral / courier mail.... ???* I am thinking procmail, maildrop, deliver, sieve-rules etc. > > - What's the average mailbox size? > > > *few accounts with 2GB and few with more space like 100GB.....* That will have an impact on POP and IMAP sessions, but should not be a problem for SMTP. It will be a challenge for backup though... > > - What mailbox type will you use? > > > *maildir /var/spool/mail/* If you use dovecot take a look at the dbox format. It should give you a performance boost on POP/IMAP. > > - NFS or local disks? > > > *NAS is available with us over iSCSI protocol......* > > > > - Which RAID level? > > > *RAID-1 , for OS + Application level , because planning to > store /var/www/html and /var/spool/mail on NAS* What's your failover strategy? p...@rick -- All technical questions asked privately will be automatically answered on the list and archived for public access unless privacy is explicitely required and justified. saslfinger (debugging SMTP AUTH): <http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>
