On 4/16/2015 6:32 AM, a jalela wrote:
> Hello
> 
> We have setup postfix using smtp_bind_address with 100 ips having
> below configuration
> 
> #--------------------------------------------
> 
> #ip=10.11.17.13 host=multi328.postfix.example.com
> <http://multi328.postfix.example.com>
> 
> 10.11.17.13:25 <http://10.11.17.13:25>      inet  n       -       n
>       -      500       smtpd
>         -o content_filter=dksign:[127.0.0.1]:10027
>         -o myhostname=multi328.postfix.example.com
> <http://multi328.postfix.example.com>
>         -o syslog_name=multi328
> 
> multi328             unix  -       -       n       -     500      smtp
>         -o smtp_bind_address=10.11.17.13
>         -o smtp_helo_name=multi328.postfix.example.com
> <http://multi328.postfix.example.com>
>         -o syslog_name=multi328
>         -o transport_maps=hash:/etc/postfix/rlt/transport328
> #--------------------------------------------
> 

You may be better served by using multiple postfix instances.  See:
http://www.postfix.org/MULTI_INSTANCE_README.html


> 
> below given questions are  regards to smtp_bind_address with 100 Ips
> 
> 
> (1)  how can we set different  queue for each  virtual
> smtp_bind_address ?

Each postfix instance has one queue. However, different transports
are scheduled independently, so congestion in one transport won't
affect other transports (until the queue is overfilled).

> 
> (2)  we don't need to use DKIM/DKIMPROXY or OPENDKIM or any other
> milter for signing mails .is there any other way to sign mail
> without using milter in postfix ?

Postfix DKIM support is through documented interfaces; either a
milter or a proxy.


> 
> (3)  postfix can open maximum 1000 out  connection  how can i
> distribute 10 connection to each virtual postfix mta ?

Get a load balancer.

> 
> (4)  we are using system having specs with 32 GB RAM, 24 core
> processor,  SSD with 6GBPS sata port  and centos6 64bit for mta
> (postfix). ulimit -n 102400 and ulimit -u 10240  but postfix can not
> use complete  resources "default_process_limit = 5000" is added in
> main.cf <http://main.cf>.
> 
>  let me know what changes require for utilizing complete resources
> and which help in make system faster and better for mail

Analyze the system to see where the bottleneck is.

> 
> (5)  don't want to use  sender_transport or random-transport.pl
> <http://random-transport.pl>  with smtp_bind_address. how  can we
> distributes mails based on helo or ehlo

Not implemented.

> 
> (6)  how can i add header tag "X-postfix-BounceCategory: reason"
>  for NDR mails.

Not implemented.

> 
> (7)  mail stats tool for each virtual postfix mta and multiple
> server,  kindly suggest us
> 
> (8)  Is there any puppet module present for  smtp_bind_address ?
> 
> (9)  how  can we set smtp_header_checks based on mail sender address ?

If you use a sender dependent transport, you can define the
smtp_header_checks in that transport.

> 
> (10) Can we print specific header parameters like (from
> ,subject,client-ID,sender,To) in single line format  into log file
> (maillog)?

Logging is not configurable.

> 
> (11) Please tell me which other parameters we can use with
> smtp_bind_address

If you're asking what other parameters you can set in a master.cf
smtp transport, see:
http://www.postfix.org/smtp.8.html

> 
> (12) how to change maillog format .like below single line log
> 
> Apr  8 07:14:58 multi1 multi328/smtp[27657]:
> 3lMNL92vNJz1r2cR:warning: header Subject: welcome to postfix from
> client1.application.com
> <http://client1.application.com>[10.10.10.10];
> from=<heidio.43e163.2de1...@multi53.postfix.example.com
> <mailto:heidio.43e163.2de1...@multi53.postfix.example.com>>,
> to=<a...@aol.com <mailto:a...@aol.com>>, proto=SMTP,
> relay=mailin-01.mx.aol.com
> <http://mailin-01.mx.aol.com>[64.12.91.195]:25, delay=1.6,
> delays=0.18/0.03/0.25/1.1, dsn=2.0.0, status=sent (250 2.0.0 Ok:
> queued as 0140C70000093)

This information is logged by different postfix processes.  You'll
need an external log processing tool to combine the existing
information.


You may be better served by using multiple postfix instances.  See:
http://www.postfix.org/MULTI_INSTANCE_README.html



  -- Noel Jones

Reply via email to