On 5/6/2011 1:53 PM, Jack wrote:
Is there anything I can do to process that a little quicker and not choke
the box to death?
In lie of seeing the information requested in the debug readme, I'll
make an educated guess that the server in question is receiving mail
from internet hosts, your backup MX, and other internal hosts all to the
same smtpd, the default smtpd in master.cf, where all main.cf
smtp_foo_restrictions are in effect. If this is the case, simply
creating another smtpd listener in master.cf which overrides all
unnecessary filters will likely fix your problem.
For instance, I use an 'internal' submission smtpd (without auth) for
internal hosts submitting mail, eliminating all the main.cf antispam
filters on the normal smtpd:
10125 inet n - - - - smtpd
-o smtpd_client_restrictions=
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o receive_override_options=no_unknown_recipient_checks,
no_address_mappings,no_header_body_checks
All internal hosts are manually configured to relay their mail to this
host on TCP 10125. Internal hosts can include desktop MUAs as well as
other Postfix servers, such as a backup MX, or you can a one listener
just for your backup MX and one for desktop MUAs, each with different
sets of restrictions, depending on your needs.
You should be running the same anti spam and antivirus filters on your
backup MX that you are on this host (assuming it's your primary MX) for
obvious reasons. If not implement such. Then you can use the method
above to eliminate your cleanup problem.
--
Stan
