Bowie, Thanks for your reply. I really have to excuse myself for not finding this information. It is clearly documented in the man pages.
However, It is rather binary and as far as I understand missing logging. I do quite a lot of logging with MRTG based on the content of maillog and procmailrc. I believe it would be beneficial for me and some others maybe if 1) If you set the opt BOFHBADMIME=accept it would be nice to have a logentry in maillog that told me a mail has been detected and accepted 2) I would also be glad to fin a finer granularity so that you could reject some MIME format errors and accept some. For example if a mail is recieved that contain a foregin characterset that is not properly described in the mail header. /Lars I really enjoy all good answers from Mr Sam and some others in this mailing list. This is really a good source for learning the courier. Thanks all that responds. ----- Original Message ----- From: "Bowie Bailey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, May 27, 2003 8:15 PM Subject: RE: [courier-users] Mime formatting error > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > > Users on my mailsystem recieves the following text quite offen. > > [MIME error message removed] > > > I looked in to some of thoes mails and thay are incorrectly > > formattted, as courier says. Usually the mail contain 8-bit > > characters, but has not declared this via MIME commands, as far as > > I udnerstand. > > Yes, Courier tends to be quite strict with RFC compliance. > > > I searched in the archive for this list and found several good > > descriptions about the problem. > > Hmmm... This question comes up on the list quite regularly. You > should have found the solution in one of those threads. > > > Question: > > Would it be possible to have a more distinct check of the problem > > and make it possible to disable the feature in courier to attach > > the mail and instead just simply let is pass. For example if the > > only problem is that some one use an incorrect defined 8-bit > > character set since they do not write in native English, the mail > > may be forwarded unchanged. May be a list of "allowed illegal > > characters" ? > > Don't know about this. AFAIK, Courier just gives the one error for > any message with screwy mime headers. > > > From another perspective (than following RFC's) one may expect the > > mailserver to pass on the message, even if the MIMEsettings of the > > mailclient behaves incorerct. > > Just add this line to the file /etc/courier/bofh (or wherever your > Courier config files live). > > opt BOFHBADMIME=accept > > > BTW: You'll get more answers (and it's easier to follow the thread) > if you give your emails a subject line. > > > Bowie > > > ------------------------------------------------------- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > _______________________________________________ > courier-users mailing list > [EMAIL PROTECTED] > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users > ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
