Courier actually doesn't pipe this parameter to ulimit -d but
to ulimit -v per default if that option is available, if you are using
Linux the -v parameter is specified in bytes (in Solaris for
instance its specified in kb)

So 33554432 means 32mb, not really a lot.

See

$ ls > /dev/null
$ ulimit -v 10000000
$ ls > /dev/null
$ ulimit -v 10000
$ ls > /dev/null
ls: error while loading shared libraries: libc.so.6: failed to map
segment from shared object: Cannot allocate memory

But if you are not running a public IMAP service, why not remove
the memory limit altogether by editing the appropriate rc-Files.

Note that you also cannot raise your ulimit again as
an unprivileged user on Linux, so if you already have
a preset -v or -d limit, you probably won't be able
to raise it anyway without talking to the person
running your host.

C.f.
http://sourceforge.net/p/courier/courier.git/ci/master/tree/courier-imap/configure.ac
http://sourceforge.net/p/courier/courier.git/ci/master/tree/courier-imap/imapd.rc.in



On Wed, 2013-09-18 at 11:51 -0400, Daniel Corbe wrote:
> There seems to be some sort of artificial memory limitation in
> courier-imap which is causing me problems:
> 
> 
> ##NAME: IMAP_ULIMITD:0
> #
> # IMAP_ULIMITD sets the maximum size of the data segment of the server
> # process.  The value of IMAP_ULIMITD is simply passed to the "ulimit
> -d"
> # command (or ulimit -v).  The argument to ulimi sets the upper limit
> on the
> # size of the data segment of the server process, in kilobytes.  The
> default
> # value of 65536 sets a very generous limit of 64 megabytes, which
> should
> # be more than plenty for anyone.
> #
> # This feature is used as an additional safety check that should stop
> # any potential denial-of-service attacks that exploit any kind of
> # a memory leak to exhaust all the available memory on the server.
> # It is theoretically possible that obscenely huge folders will also
> # result in the server running out of memory when doing server-side
> # sorting (by my calculations you have to have at least 100,000
> messages
> # in a single folder, for that to happen).
> 
> 
> This doesn't make sense to me because I have run into such a
> situation.  I'm trying to open an "obscenely huge" folder.  Fetchmail
> gives me the following output:
> 
> 
> fetchmail: Received BYE response from IMAP server:  [ALERT] FATAL
> ERROR: CANNOT ALLOCATE MEMORYfetchmail: mailbox selection failed
> 
> 
> I've tried setting ULIMITD to the output of ulimit -d on my system
> which is currently 33554432,  I've restarted courier IMAP and I still
> can't access my E-Mail.  
> I want to completely disable all artificial memory limits in courier.
>  Please help.
> 
> 
> -Daniel
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________ Courier-imap mailing list 
> Courier-imap@lists.sourceforge.net Unsubscribe: 
> https://lists.sourceforge.net/lists/listinfo/courier-imap

Attachment: smime.p7s
Description: S/MIME cryptographic signature

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Reply via email to