Here is the postconf -n
[r...@mail postfix]# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
disable_vrfy_command = yes
hopcount_limit = 500
html_directory = no
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
maximal_queue_lifetime = 5h
newaliases_path = /usr/bin/newaliases.postfix
notify_classes = donotreply
readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES
sample_directory = /usr/share/doc/postfix-2.3.3/samples
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
unknown_local_recipient_reject_code = 550
Thanks.
--- On Mon, 8/17/09, Barney Desmond <barneydesm...@gmail.com> wrote:
> From: Barney Desmond <barneydesm...@gmail.com>
> Subject: Re: postfix performance
> To: postfix-users@postfix.org
> Date: Monday, August 17, 2009, 3:49 PM
> 2009/8/18 Evan Platt <e...@espphotography.com>:
> > At 10:30 AM 8/17/2009, you wrote:
> >> I just make the test and the performance was not
> good. Outgoing 1K email
> >> was around 568 seconds.
> >>
> >> Any insight is appreciated.
> >
> > Although this will likely be out of my area of being
> able to help you,
> > someone else here probably can, but you'll want to
> post relevent logs and
> > postconf -n output.
> >
> > But 568 secoonds, my guess is there's something
> configured MAJORLY wrong.
>
> Indeed, we need `postconf -n` to spot any glaring config
> errors, and
> log entries to see the problem actually happening. A
> description of
> how you send this mailout would also be good. Obviously we
> don't want
> a full log for all 1000 messages, but a representative
> sample would be
> good. As a minimum, we should be able to track at least a
> few messages
> from start to finish.
>
