Re: terminate called after throwing an ins tance of 'std::bad_alloc'

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============8158271071169822887==
Content-Type: multipart/signed;
    boundary="=_ripper.email-scan.com-249755-1783420772-0001";
    micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 8bit

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_ripper.email-scan.com-249755-1783420772-0001
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Christopher R=C3=BCprich writes:

> Hi,
>
> after upgrading to courier 2.0.2 I keep getting the following message i=
n my =20
> log files:
>
>> Jul=C2=A0 1 18:57:24 mail imapd-ssl[1222010]: Connection, =20
>> ip=3D[::ffff:**.***.***.***], port=3D[61400]
>> Jul=C2=A0 1 18:57:24 mail imapd-ssl[1222010]: LOGIN, user=3D****@****, =20
>> ip=3D[::ffff:**.***.***.***], port=3D[61400], protocol=3DIMAP, starttl=
s=3D1
>> Jul=C2=A0 1 18:57:26 mail imapd-ssl[1222010]: terminate called after t=
hrowing an =20
>> instance of 'std::bad_alloc'
>> Jul=C2=A0 1 18:57:26 mail imapd-ssl[1222010]: what():=C2=A0 std::bad_a=
lloc
>> Jul=C2=A0 1 18:57:26 mail imapd-ssl[1222010]: Connection, =20
>> ip=3D[::ffff:**.***.***.***], port=3D[63272]
>> Jul=C2=A0 1 18:57:26 mail imapd-ssl[1222010]: LOGIN, user=3D****@****, =20
>> ip=3D[::ffff:**.***.***.***], port=3D[63272], protocol=3DIMAP, starttl=
s=3D1
>> Jul=C2=A0 1 18:57:33 mail imapd-ssl[1222010]: terminate called after t=
hrowing an =20
>> instance of 'std::bad_alloc'
>> Jul=C2=A0 1 18:57:33 mail imapd-ssl[1222010]: what():=C2=A0 std::bad_a=
lloc
> Any idea what's going on?

You found a bug. The difficult part would be tracking it down. Add the =20
IMAPDEBUGFILE setting in the imapd configuration file, then touch this fi=
le =20
in the maildir's directory. This will collect the received IMAP commands, =
so =20
at least it's known which IMAP commands are affected.

It's also very likely that the bug depends on the contents of the existin=
g =20
messages, so it'll be necessary to look at those, too.

Check if this user has a large mailbox, if so the issue is most likely th=
e =20
additional memory requirements. Edit the imapd configuration file and =20
increase the ULIMIT setting. Others have reported that doubling and even =20
quadrupling it resolves the issue.

--=_ripper.email-scan.com-249755-1783420772-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCakzXZAAKCRCKYPgoojZS
4jaxAP9qMXlUi7okReaXm4LYLL8C/pcs0LZK4At1cFZXICes9QEA6Yo+VXBnAwfN
T4ebAL92n1IBjymLpWuQCB+p3FTIGgA=
=D0S4
-----END PGP SIGNATURE-----

--=_ripper.email-scan.com-249755-1783420772-0001--


--===============8158271071169822887==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============8158271071169822887==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

--===============8158271071169822887==--