List Info

Thread: How many processes & no responce on telnet port 25




How many processes & no responce on telnet port 25
user name
2006-12-19 05:03:54
>You are getting ahead of me.  I don't understand
everything you are telling
>me so I am providing my main.cf so you can see what I
have there.
>
>Again I am assuming the master and main files have to
agree to some extent.
>I have never adjusted the master.cf for anything other
than one or two
>things at the initial setup.  Everything has been done
in the main.cf
>
>
>readme_directory =
/usr/share/doc/packages/postfix/README_FILES
>inet_protocols = all
>biff = no
>mail_spool_directory = /var/mail
>canonical_maps = hash:/etc/postfix/canonical
>virtual_alias_maps = hash:/etc/postfix/virtual
>virtual_alias_domains = hash:/etc/postfix/virtual
>relocated_maps = hash:/etc/postfix/relocated
>transport_maps = hash:/etc/postfix/transport
>sender_canonical_maps =
hash:/etc/postfix/sender_canonical
>masquerade_exceptions = root
>masquerade_classes = envelope_sender, header_sender,
header_recipient
>myhostname = gateway1.smart-mail.net
>program_directory = /usr/lib/postfix
>inet_interfaces = all
>masquerade_domains =
>mydestination = $myhostname, localhost.$mydomain
>defer_transports =
>mynetworks_style = subnet
>disable_dns_lookups = no
>relayhost =
>mailbox_command =
>mailbox_transport =
>strict_8bitmime = no
>disable_mime_output_conversion = no
>smtpd_sender_restrictions = hash:/etc/postfix/access
>smtpd_client_restrictions =
>#### smtpd helo require changed to yes
>smtpd_helo_required = yes
>smtpd_helo_restrictions =
>#### smtpd strict rfc changed to yes
>strict_rfc821_envelopes = yes
>smtpd_recipient_restrictions =
>  permit_mynetworks,
>  reject_unauth_destination,
>  reject_unauth_pipelining,
>  reject_non_fqdn_sender,
>  reject_unknown_sender_domain,
>  reject_invalid_hostname,
>  reject_non_fqdn_hostname,
>  check_policy_service inet:127.0.0.1:10023
>smtp_sasl_auth_enable = no
>smtpd_sasl_auth_enable = no
>smtpd_use_tls = no
>smtp_use_tls = no
>alias_maps = hash:/etc/aliases
>mailbox_size_limit = 0
>### Message Size Limit 15 meg = 21504000  10 Meg =
14336000 20 Meg =
>28672000
>message_size_limit = 21504000
>relay_domains = hash:/etc/postfix/transport
>
>
>smtp-amavis_destination_concurrency_limit = 20
>
>relay_recipient_maps =
hash:/etc/postfix/relay_recipients
>
>unknown_local_recipient_reject_code = 550
>
>########################################################
##
>####  Added 9/04/06 per standard IMGate config file
######
>local_destination_concurrency_limit = 2
>default_destination_concurrency_limit = 100
>smtp_always_send_ehlo = yes
>smtpd_hard_error_limit = 2
>

This setting in master.cf will work fine with your config.
It will be an 
improvement. I suggest using it:

127.0.0.1:10025 inet    n    -    n    -    -    smtpd
    -o content_filter=
    -o smtpd_restriction_classes=
    -o smtpd_delay_reject=no
    -o smtpd_client_restrictions=permit_mynetworks,reject
    -o smtpd_helo_restrictions=
    -o smtpd_sender_restrictions=
    -o smtpd_recipient_restrictions=permit_mynetworks,reject
    -o smtpd_data_restrictions=reject_unauth_pipelining
    -o smtpd_end_of_data_restrictions=
    -o mynetworks=127.0.0.0/8
    -o smtpd_error_sleep_time=0
    -o smtpd_soft_error_limit=1001
    -o smtpd_hard_error_limit=1000
    -o smtpd_client_connection_count_limit=0
    -o smtpd_client_connection_rate_limit=0
    -o smtpd_milters=
    -o local_header_rewrite_clients=
    -o local_recipient_maps=
    -o relay_recipient_maps=
    -o 
receive_override_options=no_header_body_checks,no_unknown_re
cipient_checks

Thousands of people use this.

>transport_maps = hash:/etc/postfix/transport
>relay_domains = hash:/etc/postfix/transport

People will tell you to use two separate files for this.

transport_maps = hash:/etc/postfix/transport
relay_domains = hash:/etc/postfix/relay_domains

These have separate functions, and should have separate
files.

Gary V

____________________________________________________________
_____
Get live scores and news about your team: Add the Live.com
Football Page 
www.live.com/?addtemplate=football&icid=T001MSN30A0701

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
How many processes & no responce on telnet port 25
user name
2006-12-19 15:24:54
> >Again I am assuming the master and main files have
to agree to some 
>extent.

Actually, they often don't agree, and for good reason. Each
of some 400 or 
so Postfix settings has a default value. Often the reason
you place items in 
main.cf is so you can override the default value. The
settings in main.cf 
are global. If you have a particular daemon or transport in
master.cf that 
for some reason needs to override the current value of some
setting, you use 
the '-o' setting to override the current value. Therefore,
what you are 
doing in master.cf may be in conflict with main.cf. The
point being these 
two files are not meant to 'match'.

Here is an example.

In main.cf you have:
smtpd_recipient_restrictions =
  permit_mynetworks,
  reject_unauth_destination,
  reject_unauth_pipelining,
  reject_non_fqdn_sender,
  reject_unknown_sender_domain,
  reject_invalid_hostname,
  reject_non_fqdn_hostname,
  check_policy_service inet:127.0.0.1:10023

You have a daemon listening on port 25 (smtp) that accepts
mail from the 
outside world:
smtp inet    n    -    n    -    -    smtpd

You also have a daemon listening for connections on port
10025. As I said, 
this is the port where amavisd-maia sends the mail when it
is done 
processing it. Mail that came in to port 25 (and
subsequently may get sent 
to Maia) has already been through the gauntlet that exists
in the settings 
of your smtpd_recipient_restrictions restriction stage
(configured in 
main.cf). For mail that Maia has already processed there is
no good reason 
to perform the majority of these checks more than once and
there are some 
good reasons why they should not be performed more than
once. Therefore, by 
redefining smtpd_recipient_restrictions (by overriding the
current global 
setting), we can skip many of the tests that have already
been performed 
(but we limit this to mail sent to port 10025).

127.0.0.1:10025 inet n   -   n   -   -   smtpd
     -o content_filter=
     -o
smtpd_recipient_restrictions=permit_mynetworks,reject

Gary V

____________________________________________________________
_____
Get free, personalized online radio with MSN Radio powered
by Pandora 
http://rad
io.msn.com/?icid=T002MSN03A07001

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
How many processes & no responce on telnet port 25
user name
2006-12-21 15:04:11
I installed the setting you suggested Monday night and
within a short while
I was getting log timeouts when telneting to the server.  I
did read the
artice

http://www.ijs.si/software/amavisd/README.postfix.txt

and there was included in the instructions a line to add to
the main.cf

content_filter=smtp-amavis:[127.0.0.1]:10024

I added the line and the timeouts seem to go down
temporarily but during the
day when traffic is up I was still getting timeouts same or
worse than I was
before.  

Qshape deferred shows 0  and active shows 17 in the 5 min
band

Ps -e | grep -c smtpd
77
Ps -e | grep -c smtp
107

The timeouts seem worst when the smtp connections are above
100

I will post some log info


New master.cf

# service type  private unpriv  chroot  wakeup  maxproc
command + args
#               (yes)   (yes)   (yes)   (never) (100)
#
============================================================
==============
smtp      inet  n       -       n       -       200      
smtpd -o
content_filter=smtp-amavis:[127.0.0.1]:10024
smtp-amavis unix -	-	n	-	20  	smtp
    -o smtp_data_done_timeout=1200
    -o smtp_send_xforward_command=yes
    -o disable_dns_lookups=yes
pickup    fifo  n       -       n       60      1      
pickup
cleanup   unix  n       -       n       -       0      
cleanup
qmgr      fifo  n       -       n       300     1       qmgr
rewrite   unix  -       -       n       -       -      
trivial-rewrite
bounce    unix  -       -       n       -       0      
bounce
defer     unix  -       -       n       -       0      
bounce
trace     unix  -       -       n       -       0      
bounce
verify    unix  -       -       n       -       1      
verify
flush     unix  n       -       n       1000?   0      
flush
proxymap  unix  -       -       n       -       -      
proxymap
smtp      unix  -       -       n       -       -       smtp
showq     unix  n       -       n       -       -      
showq
error     unix  -       -       n       -       -      
error
discard   unix  -       -       n       -       -      
discard
local     unix  -       n       n       -       -      
local
virtual   unix  -       n       n       -       -      
virtual
lmtp      unix  -       -       n       -       -       lmtp
anvil     unix  -       -       n       -       1      
anvil
127.0.0.1:10025 inet	n	-	n	-	-	smtpd 
	-o content_filter=
 	-o smtpd_restriction_classes=
    	-o smtpd_delay_reject=no
    	-o smtpd_client_restrictions=permit_mynetworks,reject
    	-o smtpd_helo_restrictions=
    	-o smtpd_sender_restrictions=
    	-o
smtpd_recipient_restrictions=permit_mynetworks,reject
    	-o smtpd_data_restrictions=reject_unauth_pipelining
    	-o smtpd_end_of_data_restrictions=
    	-o mynetworks=127.0.0.0/8
    	-o smtpd_error_sleep_time=0
    	-o smtpd_soft_error_limit=1001
    	-o smtpd_hard_error_limit=1000
    	-o smtpd_client_connection_count_limit=0
    	-o smtpd_client_connection_rate_limit=0
    	-o smtpd_milters=
    	-o local_header_rewrite_clients=
    	-o local_recipient_maps=
    	-o relay_recipient_maps=
    	-o
receive_override_options=no_header_body_checks,no_unknown_re
cipient_checks
scache	  unix	-	-	n	-	1	scache
maildrop  unix  -       n       n       -       -       pipe
  flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d
$
cyrus	  unix	-	n	n	-	-	pipe
  user=cyrus argv=/usr/lib/cyrus/bin/deliver -e -r $
-m $
$
uucp	  unix	-	n	n	-	-	pipe
  flags=Fqhu user=uucp argv=uux -r -n -z -a$sender -
$nexthop!rmail
($recipient)
ifmail    unix  -       n       n       -       -       pipe
  flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop
($recipient)
bsmtp     unix  -       n       n       -       -       pipe
  flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender
$nexthop
$recipient
procmail  unix  -       n       n       -       -       pipe
  flags=R user=nobody argv=/usr/bin/procmail -t -m
/etc/procmailrc $
$






-----Original Message-----
From: maia-users-bouncesrenaissoft.com
[mailto:maia-users-bouncesrenaissoft.com] On Behalf
Of Gary V
Sent: Tuesday, December 19, 2006 9:25 AM
To: maia-usersrenaissoft.com
Subject: Re: [Maia-users] How many processes & no
responce on telnet port 25

> >Again I am assuming the master and main files have
to agree to some 
>extent.

Actually, they often don't agree, and for good reason. Each
of some 400 or 
so Postfix settings has a default value. Often the reason
you place items in

main.cf is so you can override the default value. The
settings in main.cf 
are global. If you have a particular daemon or transport in
master.cf that 
for some reason needs to override the current value of some
setting, you use

the '-o' setting to override the current value. Therefore,
what you are 
doing in master.cf may be in conflict with main.cf. The
point being these 
two files are not meant to 'match'.

Here is an example.

In main.cf you have:
smtpd_recipient_restrictions =
  permit_mynetworks,
  reject_unauth_destination,
  reject_unauth_pipelining,
  reject_non_fqdn_sender,
  reject_unknown_sender_domain,
  reject_invalid_hostname,
  reject_non_fqdn_hostname,
  check_policy_service inet:127.0.0.1:10023

You have a daemon listening on port 25 (smtp) that accepts
mail from the 
outside world:
smtp inet    n    -    n    -    -    smtpd

You also have a daemon listening for connections on port
10025. As I said, 
this is the port where amavisd-maia sends the mail when it
is done 
processing it. Mail that came in to port 25 (and
subsequently may get sent 
to Maia) has already been through the gauntlet that exists
in the settings 
of your smtpd_recipient_restrictions restriction stage
(configured in 
main.cf). For mail that Maia has already processed there is
no good reason 
to perform the majority of these checks more than once and
there are some 
good reasons why they should not be performed more than
once. Therefore, by 
redefining smtpd_recipient_restrictions (by overriding the
current global 
setting), we can skip many of the tests that have already
been performed 
(but we limit this to mail sent to port 10025).

127.0.0.1:10025 inet n   -   n   -   -   smtpd
     -o content_filter=
     -o
smtpd_recipient_restrictions=permit_mynetworks,reject

Gary V

____________________________________________________________
_____
Get free, personalized online radio with MSN Radio powered
by Pandora 
http://rad
io.msn.com/?icid=T002MSN03A07001

_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

---
[This E-mail scanned for viruses by Declude EVA]


_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
[1-3]

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