Can anyone explain these weird error messages? I have just started playing
with postfix, and it's not bad, but this seems to be a weird glitch.
I was testing the limits of message size, both of postfix and a couple of third
party mail providers, and came up with this log.
Dec 27 14:35:32 fw postfix/master[541]: warning: file size limit 524288000
< message_size_limit 1024000000 -- reset
Now, I have looked at http://www.postfix.org/resource.html#size
and I HAVE increased the Message Size Limit as this log states, but I can't
figure out how to increase the file size limit...
Also I would LOVE to know how to stop postfix from listening on a port, but
still
process the queue. Currently I have told postfix to listen on localhost
only, and have
Obtuse SMTPD listening on all other interfaces... This works fine, but is a
bit of a hack.
You should be able to stop it from listening totally like you can with
sendmail.
(Note, you can do this, but then it fails to process the mail queue...)
If anyone can help me with this, to save me from subscribing to the postfix
mailing
list..... Would be much appreciated.
Kurt? I seem to remember you being a postfix monkey??
(Bah.. really I just wanted to post something to the list to see if
everyone is still alive!!!
Is it only ME who is working between xmas and new year or are there other
idiots out
there too???)
/me stops playing with postfix and gets back to work...
-Nix
Dec 27 13:33:14 fw postfix/cleanup[426]: 3DDA3823E:
message-id=<5.0.2.1.0.20001227130542.02f9cda8@mail.itaudit.com.au>
Dec 27 13:35:59 fw postfix/smtpd[425]: disconnect from unknown[172.20.1.8]
Dec 27 13:35:59 fw postfix/qmgr[402]: 3DDA3823E: from=
Can anyone explain these weird error messages? I have just started playing with postfix, and it's not bad, but this seems to be a weird glitch. I was testing the limits of message size, both of postfix and a couple of third party mail providers, and came up with this log. Dec 27 14:35:32 fw postfix/master[541]: warning: file size limit 524,288,000 < message_size_limit 102400000 -- reset
message_size_limit (default: 10240000 bytes) The maximal size of a Postfix queue file, including envelope information (sender, recipient, etc.). Hmm. weird. You explicitly set the message_size_limit right to something larger then 524288000? I can't imagine a max size limit of like 100 megs (that's insanly huge). In sendmail I think it's 10 megs by default (I suspect postfix is the same and they made a typo).
Now, I have looked at http://www.postfix.org/resource.html#size and I HAVE increased the Message Size Limit as this log states, but I can't figure out how to increase the file size limit... Also I would LOVE to know how to stop postfix from listening on a port, but still process the queue. Currently I have told postfix to listen on localhost only, and have Obtuse SMTPD listening on all other interfaces... This works fine, but is a bit of a hack. You should be able to stop it from listening totally like you can with sendmail. (Note, you can do this, but then it fails to process the mail queue...)
If anyone can help me with this, to save me from subscribing to the
Ok in main.cf we have the variable "inet_interfaces", usually set to "all". leaving it blank doesn't work. setting it to "none" makes it look for the hostname "none" setting it to localhost and it only listens to 127.0.0.1 port 25 I'm not sure what to set it to, here are some interesting entries from the HISTORY file: 19991216 Feature: allow an empty inet_interfaces parameter, just like an empty mydestination parameter. It's needed for true null clients and for firewalls that deliver no local mail. 19991223 Bugfix: smtpd should not check for unknown users when running in stand-alone (sendmail -bs) mode. Problem experienced by Chuck Mead. File: smtpd/smtpd.c. Retraction: the "local_transports" configuration parameter is gone. Adjusted code and documentation accordingly. Instead, use just one "local_transport" parameter with the name of the default local transport. Files: smtpd/smtpd_check.c, qmgr/qmgr_message.c, trivial-rewrite/ resolve.c, local/resolve.c. Feature: Postfix SMTPD now insists that the smtpd recipient restrictions contain at least one restriction that by default rejects mail. This should make it much more difficult to change Postfix into an open relay. File: smtpd/smtpd_check.c. Retraction: null-length inet_interfaces is too confusing. Ask on the Postfix list is my advice, people must be doing this. postfix
mailing list..... Would be much appreciated. Kurt? I seem to remember you being a postfix monkey??
Eeee! Eeee!!! EEEE!!!!
(Bah.. really I just wanted to post something to the list to see if everyone is still alive!!! Is it only ME who is working between xmas and new year or are there other idiots out there too???)
Me to (seen my SSH/SSL stuff =)
/me stops playing with postfix and gets back to work...
-Nix
-Kurt
message_size_limit (default: 10240000 bytes) The maximal size of a Postfix queue file, including envelope information (sender, recipient, etc.).
Hmm. weird. You explicitly set the message_size_limit right to something larger then 524288000? I can't imagine a max size limit of like 100 megs (that's insanly huge). In sendmail I think it's 10 megs by default (I suspect postfix is the same and they made a typo).
Errm.. No, I set that.. I added two zeros to the default number :-) My test email is an 88Mb mp3 file :-) Insane I know, but I am testing a setup for an engineering firm who regularly ship >50Mb Cad files around the place via email...
Ok in main.cf we have the variable "inet_interfaces", usually set to "all".
leaving it blank doesn't work. setting it to "none" makes it look for the hostname "none" setting it to localhost and it only listens to 127.0.0.1 port 25
Yah... I tried all this, and hence ended up with it listening on localhost, with smtpd on all other interfaces..
Ask on the Postfix list is my advice, people must be doing this.
hmm.. will do later..
Me to (seen my SSH/SSL stuff =)
Yup.. u caused quite a stir there buddy :-) Bugtraq will never be the same.. rofl... -Nix "As far as the laws of mathematics refer to reality, they are not certain; as far as they are certain, they do not refer to reality." -- Albert Einstein
Nix wrote: [...]
Also I would LOVE to know how to stop postfix from listening on a port, but still process the queue. Currently I have told postfix to listen on localhost only, and have Obtuse SMTPD listening on all other interfaces... This works fine, but is a bit of a hack. You should be able to stop it from listening totally like you can with sendmail. (Note, you can do this, but then it fails to process the mail queue...)
Comment out the line smtp inet n - y - - smtpd in /etc/postfix/master.cf -- Ørnulf Nielsen
Kurt Seifried wrote:
Comment out the line
smtp inet n - y - - smtpd
in /etc/postfix/master.cf Pity it isn't documented. It appears to work properly, thank you!
Oh yes it is :-) http://www.postfix.org/faq.html#null_client -- Ørnulf Nielsen
Hi, Quoting Nix (suse@nix.hispeed.com) on Thu, Dec 28, 2000 at 12:44:52PM +1100:
Can anyone explain these weird error messages? I have just started playing with postfix, and it's not bad, but this seems to be a weird glitch. I was testing the limits of message size, both of postfix and a couple of third party mail providers, and came up with this log. Dec 27 14:35:32 fw postfix/master[541]: warning: file size limit 524288000 < message_size_limit 1024000000 -- reset
What does ulimit -a say? Sounds like the OS is limiting tthe size and postfix checks bevore attempting to write to the file. If you check the postfix source, you will see that this comes from the process limits. cheers afx -- atsec information security GmbH Phone: +49-89-44249830 Steinstrasse 68 Fax: +49-89-44249831 D-81667 Muenchen, Germany WWW: www.atsec.com May the Source be with you!
At 10:34 AM 28/12/2000 +0100, you wrote:
What does ulimit -a say? Sounds like the OS is limiting tthe size and postfix checks bevore attempting to write to the file. If you check the postfix source, you will see that this comes from the process limits.
fw:~ # cat /etc/profile --snip-- #Additions by harden_suse: ulimit -H -c 20000 # hardlimit: no coredumps > 20mb ulimit -S -c 0 # softlimit: no coredumps ulimit -f 512000 # hard/soft: no files > 512 mb in size allowed ulimit -S -n 250 # softlimit: no more than 250 filedescriptors ulimit -S -u 100 # softlimit: no more than 100 processes ulimit -H -v 100000 # hardlimit: no more than 100mb memory ulimit -S -v 50000 # softlimit: no more than 50mb memory (netscape needs ...) fw:/etc # ulimit -a core file size (blocks) 0 data seg size (kbytes) unlimited file size (blocks) 512000 max locked memory (kbytes) unlimited max memory size (kbytes) unlimited open files 250 pipe size (512 bytes) 8 stack size (kbytes) 8192 cpu time (seconds) unlimited max user processes 100 virtual memory (kbytes) 50000 -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
From: Nix
Date: Thu, 28 Dec 2000 23:03:50 +1100 To: suse-security@suse.com Subject: Re: [suse-security] weird postfix error At 10:34 AM 28/12/2000 +0100, you wrote:
What does ulimit -a say? Sounds like the OS is limiting tthe size and postfix checks bevore attempting to write to the file. If you check the postfix source, you will see that this comes from the process limits.
fw:~ # cat /etc/profile --snip-- #Additions by harden_suse: ulimit -H -c 20000 # hardlimit: no coredumps > 20mb ulimit -S -c 0 # softlimit: no coredumps ulimit -f 512000 # hard/soft: no files > 512 mb in size allowed ulimit -S -n 250 # softlimit: no more than 250 filedescriptors ulimit -S -u 100 # softlimit: no more than 100 processes ulimit -H -v 100000 # hardlimit: no more than 100mb memory ulimit -S -v 50000 # softlimit: no more than 50mb memory (netscape needs ...)
fw:/etc # ulimit -a core file size (blocks) 0 data seg size (kbytes) unlimited file size (blocks) 512000 max locked memory (kbytes) unlimited max memory size (kbytes) unlimited open files 250 pipe size (512 bytes) 8 stack size (kbytes) 8192 cpu time (seconds) unlimited max user processes 100 virtual memory (kbytes) 50000
-- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
Quoting Nix (suse@nix.hispeed.com) on Thu, Dec 28, 2000 at 11:03:50PM +1100:
At 10:34 AM 28/12/2000 +0100, you wrote:
What does ulimit -a say? Sounds like the OS is limiting tthe size and postfix checks bevore attempting to write to the file. If you check the postfix source, you will see that this comes from the process limits.
fw:~ # cat /etc/profile --snip-- #Additions by harden_suse: ^^^^^^^^^^^^^^^^^^^^^^^^^ Mark is a bit radical sometimes.....
ulimit -H -c 20000 # hardlimit: no coredumps > 20mb ulimit -S -c 0 # softlimit: no coredumps ulimit -f 512000 # hard/soft: no files > 512 mb in size allowed ^^^^^^ here you go... I got bittenn by harden_suse as well, took me a bit to figure out why mkisofs always died :-(
fw:/etc # ulimit -a core file size (blocks) 0 data seg size (kbytes) unlimited file size (blocks) 512000 <-------------- max locked memory (kbytes) unlimited
cheers afx -- atsec information security GmbH Phone: +49-89-44249830 Steinstrasse 68 Fax: +49-89-44249831 D-81667 Muenchen, Germany WWW: www.atsec.com May the Source be with you!
participants (5)
-
Andreas Siegert
-
Kurt Seifried
-
Nix
-
Peter Thalmann
-
Ørnulf Nielsen