|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Strange behaviour
Aleksey I Zavilohin (villain
villain.home.ems.chel.su)
Wed, 10 Nov 1999 00:43:35 +0500
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Ted Spradley: "Re: Strange behaviour"
- Previous message: LaMont Jones: "Re: path MTU discovery and error sending data"
- In reply to: Adam Levin: "path MTU discovery and error sending data"
- Next in thread: Chris Wedgwood: "Re: Strange behaviour"
- Next in thread: Ted Spradley: "Re: Strange behaviour"
- Reply: Chris Wedgwood: "Re: Strange behaviour"
Daniel Serna wrote:
> It looks like you hit the default message_size_limit. This limit dictates
> how big in bytes the email your receive can be for Postfix to process. In
> looking at my configuration, it looks like the message_size_limit is set
> to 10240000 by default as well. So, I assume unless explicitly set, the
> default setting for message_size_limit out of the box is 10240000. Looks
> like you received a very large email which was over the Postfix limit and
> thus bounced. If you normally receive emails larger than 10240000 bytes in
> size, you may want to set a higer number with the following option in
> main.cf:
>
> message_size_limit = n
>
> Where "n" is the max size of an email you will receive in bytes.
>
> Hope that helps,
>
I know this 8-)
I ask other (maybe very uglu 8-)), and, maybe, as small bug report 8-)).
after reset message_size_limit still = 10240000 or unlimited?
> > I setup new linux kernel on my home computer (2.3.24 as you see in header 8-))
> > And postfix began complain in syslog
> >
> > Nov 8 14:13:34 villain postfix/master[253]: \
> > warning: file size limit 4294967295 < message_size_limit 10240000 -- reset
> >
> > Who is wrong?
> >
> > I don`t have source code for postfix at home 8-), but i think you use getrlimit
> > for check maximum file size
> > and this comment i find in linux/include/linux/resorce.h
> >
> > /*
> > * SuS says limits have to be unsigned.
> > *
> > * Which makes a ton more sense anyway.
> > */
> >
> > #define RLIM_INFINITY (~0UL)
> >
> > struct rlimit {
> > unsigned long rlim_cur;
> > unsigned long rlim_max;
> > };
> >
> >
> > fileds define as unsigned long (in glibc source - this fields define as long, and
> > in may man page define as int 8-())
-- Wisdom is knowing what to do with what you know. -- J. Winter Smith
- Next message: Ted Spradley: "Re: Strange behaviour"
- Previous message: LaMont Jones: "Re: path MTU discovery and error sending data"
- In reply to: Adam Levin: "path MTU discovery and error sending data"
- Next in thread: Chris Wedgwood: "Re: Strange behaviour"
- Next in thread: Ted Spradley: "Re: Strange behaviour"
- Reply: Chris Wedgwood: "Re: Strange behaviour"
This archive was generated by hypermail 2.0b3 on Tue Nov 09 1999 - 15:11:21 CST