Am 05.05.2010 03:04, schrieb Jim Flanagan:

On Tue, May 4, 2010 at 4:07 AM, Sandy Drobic wrote:

...

Am 04.05.2010 01:00, schrieb Jim Flanagan:

...

On Mon, May 3, 2010 at 4:02 PM, Sandy Drobic wrote:

...

On 2010.05.03 20:05, Jim Flanagan wrote:

...

If that doesn't solve the problem try to do it step by step:

Simply comment out the smtps lines and restart Postfix. Does it work now?

Yes it does! I followed all your steps one by one, and finally at the end, by commenting out only the smtps line in master.cf, postfix started and I've got a flood of emails coming in from my backupmx. That did the trick.

Well, that is a bit strange. Just using the port number instead of the service name should have done the trick already. I suspect that you have a syntax error on top of a /etc/services problem in your smtps line. Generally, in your /etc/services you should have such a line: grep smtps /etc/services smtps 465/tcp # smtp ssl old version One problem that popped up on my system was, that an update of VMWare Server 1 set the permissions on /etc/services to 640 or so, thus denying access to postfix smtpd server which is not running as root. That resulted in similar errors as the one you quoted. What are the permissions on your /etc/services? Apart from the missing white space at the beginning of the second (continuation) line of your smtps definition you should not have a problem if Postfix can access your /etc/services file and the smtps line is included in your /etc/services.

Is there anything I need to do now to that file, or am I safe to leave it as is with that line commented out?

As quoted, the port 465 is not used for mail routing in any way. Only port 25 is used by remote servers to transfer mail to your system. Squirrelmail has a setting that can use the smtps port, and I know that Lotus Domino can use the port, but normally you can safely deactivate the port.

...

One more remark concerning your smtp line: You have restricted the smtp port to 10 processes. The reasonable default is 100. Unless you plan to use Amavisd-new as a pre queue filter (content_filter is after queue filter) you should set the default 100. The smtpd process doesn't take a lot of resources. I would definitely recommend it.

On this point, in comparing my old master.cf to the new one, the old one had the value set at only 2. I guess the update changed the value to 10? I do use amavis-new running (since the original setup). What would be a good value to use in this case?

The default settings provided by Opensuse are not meant for a regular mailserver. Some parameters must be changed for that. One of those is the number of smtpd processes. Normally you should go with a 100 smtpd processes that should cover most cases. The memory footprint of a smtpd process is rather small, a bit bigger on 64 bit systems, but still uses only a few kb. A hundred smtpd processes only take a few MB. The real memory hog is the content_filter. If you run amavisd-new as a content_filter then the filtering is happening after you already accepted the mail. This is the normal usage and you can set hundreds of smtpd processes without choking even a small system. The number of smtpd processes have to cover the maximum number of simultaneous connections to your server. Connections are made by external servers that try to submit mails to your system, clients that try to submit mails to relay via your server (if you don't use the submission port for those clients), and internal processes like amavisd-new, when the mail is sent back to Postfix after checking. 10 is rather small in such a case. If you suffer from a spam wave all 10 processes will probably be used by spambots and no processes are left for normal servers to submit mails. If you use amavisd-new as a proxy server then you should set the number of smtpd processes to match the number of amavisd-new processes. But in your case this is inadvisable, since you have a backup mx. I assume that this backup mx is run by your provider and you have no influence what settings are used to block spam. So you might as well not bother with too many anti spam settings as the spammer will simply use the backup mx as the target for his junk mails. In this case it might have helped you to have a backup mx, but it is the death of spam fighting. :-/ Sandy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org