Re: Need recommendation for Postfix/dovecot implementation for 200,000 users

2011-10-24 Thread Stan Hoeppner
On 10/24/2011 9:30 PM, Poh Yong Hwang wrote: > Hi all, > > New to this mailing list here. > > I have a requirement to setup a mail system for 200,000 users and it needs > to be Postfix for SMTP and dovecot 2 for IMAP. > > May I know what is the best setup for such an implementation? Can postfix

Re: limit recipent per message

2011-10-24 Thread Kirill Bychkov
Please read the manual: http://www.postfix.org/postconf.5.html#default_destination_recipient_limit and http://www.postfix.org/TUNING_README.html chapter: Tuning the number of recipients per delivery On 24 October 2011 18:43, Ejaz wrote: > Hello, > > ** ** > > Is it possible by postfix to

Need recommendation for Postfix/dovecot implementation for 200,000 users

2011-10-24 Thread Poh Yong Hwang
Hi all, New to this mailing list here. I have a requirement to setup a mail system for 200,000 users and it needs to be Postfix for SMTP and dovecot 2 for IMAP. May I know what is the best setup for such an implementation? Can postfix be clustered? Thanks! Yongsan

Re: PATCH: Protocol error: postfix-2.3 vs. 2.9

2011-10-24 Thread Wietse Venema
g in undefined behavior. That will be the final fix for this problem. I'll cook up something later this week. Wietse > 20111024 > > Bugfix (introduced: Postfix 2.3): while the Postfix SMTP > client's protocol parser uses the last SMTP reply line as >

Re: rejecting mails to *.recipient@... for all but a few senders?

2011-10-24 Thread /dev/rob0
On Monday 24 October 2011 05:48:32 Julio Talaverano wrote: > I've got this rather complicated problem: You're in luck! There are similar examples in the documentation. > 1) a) I'd like to block mails to specific internal recipients > (e.g. *.r...@mycomp.com) but allow only one or more domains to

Re: Down To One Problem?

2011-10-24 Thread /dev/rob0
On Monday 24 October 2011 08:49:49 Jack Fredrikson wrote: > From: Noel Jones > > Looks as if the user f...@example.com doesn't accept mail. Is > > that supposed to be a valid user? Where is that domain listed > > in your postfix config? Where is the user listed? > > Now here you can help me di

Re: I've Got To Be Close...

2011-10-24 Thread Jack Fredrikson
From: Simon Brereton To: postfix users Sent: Monday, October 24, 2011 12:02 PM Subject: Re: I've Got To Be Close... > And this is probably better off discussed on the dovecot list now that > you seem to have gotten postfix sorted out. > > Although, since you exp

Re: I've Got To Be Close...

2011-10-24 Thread Simon Brereton
On 24 October 2011 11:20, Jack Fredrikson wrote: > Hi; > I'm still getting this (and *only* this) error: > Oct 24 08:18:01 myserver postfix/pipe[21761]: 5CC9F5790195: > to=, relay=dovecot, delay=0.66, delays=0.64/0/0/0.02, > dsn=4.3.0, status=deferred (temporary failure) Sounds like your file per

Re: I've Got To Be Close...

2011-10-24 Thread Jack Fredrikson
I forgot to add: /etc/postfix/vmailbox includes lines such as: f...@bar.com    bar.com/foo and I have run these commands: postmap /etc/postfix/vmailbox postfix reload TIA, Jack

I've Got To Be Close...

2011-10-24 Thread Jack Fredrikson
Hi; I'm still getting this (and *only* this) error: Oct 24 08:18:01 myserver postfix/pipe[21761]: 5CC9F5790195: to=, relay=dovecot, delay=0.66, delays=0.64/0/0/0.02, dsn=4.3.0, status=deferred (temporary failure) queue_directory = /var/spool/postfix myorigin = $mydomain command_directory = /usr/

limit recipent per message

2011-10-24 Thread Ejaz
Hello, Is it possible by postfix to send 100 recipient per message, also I would like to maximum limit of the recipient per message by the postfix. Would any please guide me in this, thanks in advance Regards, __ Mohammed Ejaz Sr,Systems Administrator -- Th

Re: Down To One Problem?

2011-10-24 Thread Jack Fredrikson
From: Noel Jones To: postfix-users@postfix.org Sent: Monday, October 24, 2011 1:23 AM Subject: Re: Down To One Problem? > It seems you fail to understand some basics, and you continue to mix > example commands from multiple unrelated solutions. I plead guilty.

Re: Down To One Problem?

2011-10-24 Thread Jack Fredrikson
From: john To: postfix-users@postfix.org Sent: Sunday, October 23, 2011 11:56 PM Subject: Re: Down To One Problem? > Might I suggest you take a look here Dovecot 2.0 documentation - How to which > has several extremely good Dovecot How-tos. Of particular > int

PATCH: Protocol error: postfix-2.3 vs. 2.9

2011-10-24 Thread Wietse Venema
t; (128.176.188.24) and server (mail.charite.de). We speak both English and > German.) This bug was fixed in Postfix 2.7 with the introduction of the smtp_reply_filter feature, but it was never recorded in the HISTORY file, and therefore it was never back-ported to earlier Postfix versions.

Protocol error: postfix-2.3 vs. 2.9

2011-10-24 Thread Ralf Hildebrandt
Uni-muenster.de tries to send mail to us: We're returning (using postscreen): 220-mail.charite.de ESMTP 421-4.3.2 All server ports are busy 421 4.3.2 Contact postmas...@charite.de (using a different email address!) for technical assistance. Please provide the following information in your prob

Postfix stable release 2.8.6, 2.7.7, 2.6.13, 2.5.16

2011-10-24 Thread Wietse Venema
[An on-line version of this announcement will be available at http://www.postfix.org/announcements/postfix-2.8.6.html] Postfix stable release 2.8.6, 2.7.7, 2.6.13 and 2.5.16 are available. These contain fixes that are also included with the Postfix 2.9 experimental release. * The Postfix SMTP

Re: alias all users in one domain to another domain

2011-10-24 Thread Chris Richards
On Mon, October 24, 2011 12:28 am, Noel Jones wrote: > On 10/23/2011 10:06 PM, Chris Richards wrote: >> My question is this: how do I setup to alias all of my users in domain A >> so that they also appear in domain B, and do so WITHOUT turning my >> server >> into a backscatter source? > > virtua

rejecting mails to *.recipient@... for all but a few senders?

2011-10-24 Thread Julio Talaverano
Hi, I've got this rather complicated problem: 1) a)  I'd like to block mails to specific internal recipients (e.g. *.r...@mycomp.com) but allow     only one or more domains to send to them.     b) blocking emails sent by these recipients (This is already in place using regexp header_chec