This is a discussion on Re: [courier-users] possibly bug or misconfiguration? corrupted log within the Courier-Imap forums, part of the Mail Servers and Related category; This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
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. --===============1669550582== Content-Type: multipart/signed; boundary="=_mimegpg-commodore.email-scan.com-30879-1199493254-0002"; micalg=pgp-sha1; protocol="application/pgp-signature" 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. --=_mimegpg-commodore.email-scan.com-30879-1199493254-0002 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Thomas Jacob writes: > Jan 4 00:22:19 XXX pop3d: [ID 702911 mail.info] LOGIN, user=XXXXXINFO: > LOGIN, user=, ip=[::ffff:XX.XX.XX.XX], port=[XXX2609, ip=[] > > Basically it looks like several client processes log messages aren't > cleanly separated into single lines. > > We're running courier-authlib-0.60.2 /courier-imap-4.3.0 on Sun Fire > T1000 / Solaris 10 and we're processing the log messages for system > accounting purposes, so their reliability is relatively important. > > Is anybody else seeing this? Is it a bug? A misconfiguration on our > part? An OS issue? Any hints will be very welcome... An OS issue. Looks like Solaris doesn't line-buffer stderr, by default. Try sticking setvbuf(stderr, NULL, _IOLBF, BUFSIZ); as the first order of business in main() in both imaplogin.c and imapd.c. That should take care of it for IMAP. POP3, and other services, will likely have a similar issue. It's also remotely possibly that your libc might use an environment variable to set this, by default. --=_mimegpg-commodore.email-scan.com-30879-1199493254-0002 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQBHftCHx9p3GYHlUOIRAkBaAJ0YKGFfKZCyrXmSXcbG8f WO/3bI4gCfVld5 xUWGWmNBDg4J8f5UrULAI1A= =+N1R -----END PGP SIGNATURE----- --=_mimegpg-commodore.email-scan.com-30879-1199493254-0002-- --===============1669550582== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ --===============1669550582== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users --===============1669550582==-- |