RE: example.com problem?
Wietse Venema [mailto:wie...@porcupine.org] wrote: Norm Mackey: The situation reached the point where the mail queue could not even be listed completely with postqueue without postqueue failing, and What was the failure? I suppose that after $daemon_timeout seconds (1800s default) the daemon that lists the queue is terminated for safety reasons. If there were other errors then I would like to know. If you don't want to deliver example.com, a transport map with example.com discard: will do the job (Postfix 2.2 or later), as will an access map rule. -- The failure was logged in /var/log/mail/errors as messages like: [r...@relay mail]# cat errors |grep open files|head -n 5 Jan 19 00:39:43 relay postfix/qmgr[26415]: fatal: socket: Too many open files Jan 19 00:40:48 relay postfix/qmgr[29208]: fatal: socket: Too many open files Jan 19 00:42:07 relay postfix/qmgr[29255]: fatal: socket: Too many open files Jan 19 00:43:25 relay postfix/qmgr[29328]: fatal: socket: Too many open files Jan 19 00:44:43 relay postfix/qmgr[29523]: fatal: socket: Too many open files Norm
Re: example.com problem?
Norm Mackey: The failure was logged in /var/log/mail/errors as messages like: [r...@relay mail]# cat errors |grep open files|head -n 5 Jan 19 00:39:43 relay postfix/qmgr[26415]: fatal: socket: Too many open files Your machine resources don't match the Postfix configuration. Either scale down Postfix (the process limits) or get a better machine. Running Postfix like this is like cramming a school class into a telephone booth, if you are old enough to remember what that is. Wietse
Re: example.com problem?
Norm Mackey: The situation reached the point where the mail queue could not even be listed completely with postqueue without postqueue failing, and What was the failure? I suppose that after $daemon_timeout seconds (1800s default) the daemon that lists the queue is terminated for safety reasons. If there were other errors then I would like to know. If you don't want to deliver example.com, a transport map with example.com discard: will do the job (Postfix 2.2 or later), as will an access map rule. Wietse
Re: example.com problem?
- Original Message From: Norm Mackey n...@enterprisewizard.com To: postfix-users@postfix.org Sent: Thursday, January 22, 2009 4:12:21 AM Subject: example.com problem? I had been under the impression that I should tell users to use the domain example.com (or example.org) as default settings in software being tested and developed, in order that the software not generate email which would be a problem for our own or other domains' SMTP servers. Jan 19 04:55:07 relay postfix/qmgr[27203]: warning: mail for example.com is using up 6001 of 6016 active queue entries Jan 19 04:55:07 relay postfix/qmgr[27203]: warning: you may need a separate master.cf transport for example.com Start of the connection timeouts slightly later in /var/log/mail/info: Jan 18 15:20:17 relay postfix/smtp[24790]: connect to example.com[208.77.188.166]: Connection timed out (port 25) Jan 18 15:20:17 relay postfix/smtp[24790]: 345F82544D7: to=, relay=none, delay=30, status=deferred (connect to example.com[208.77.188.166]: Connection timed out) Jan 18 15:20:18 relay postfix/smtp[24791]: connect to example.com[208.77.188.166]: Connection timed out (port 25) Jan 18 15:20:18 relay postfix/smtp[24791]: 0ECEE2544D8: to=, relay=none, delay=30, status=deferred (connect to example.com[208.77.188.166]: Connection timed out) Use a domain that doesn't exist or create your own DNS name like local.you. http://network-tools.com/default.asp?prog=networkhost=example.com
Re: example.com problem?
On Jan 21, 2009, at 10:12 PM, Norm Mackey wrote: I had been under the impression that I should tell users to use the domain example.com (or example.org) as default settings in software being tested and developed, in order that the software not generate email which would be a problem for our own or other domains' SMTP servers. This recently heavily stressed our SMTP server. That's why it should only be used as an example, not in practice. ;) Test accounts should generally be actual accounts that can be monitored during testing. I'd use smtpd_recipient_restrictions, and add a line to the map for check_recipient_access to discard anything to example.com. Your system would still accept these, but would just discard them instead of attempting delivery.
