| From | Sent On | Attachments |
|---|---|---|
| Ken Nagorski | Jan 16, 2002 2:35 pm | |
| Mark Constable | Jan 16, 2002 6:49 pm | |
| Juha Saarinen | Jan 16, 2002 7:05 pm | |
| Aly S.P Dharshi | Jan 16, 2002 7:12 pm | |
| Tomas Fasth | Jan 17, 2002 1:19 am | |
| Odhiambo Washington | Jan 17, 2002 2:34 am | |
| Mark Constable | Jan 17, 2002 3:11 am | |
| Marcus Felipe Pereira | Jan 17, 2002 6:22 am | |
| drea...@dreamwvr.com | Jan 17, 2002 7:33 am | |
| drea...@dreamwvr.com | Jan 17, 2002 7:52 am | |
| Gordon Messmer | Jan 17, 2002 8:07 am | |
| Aly S.P Dharshi | Jan 17, 2002 8:11 am | |
| Papo Napolitano | Jan 17, 2002 9:00 am | |
| Mark Constable | Jan 17, 2002 12:26 pm | |
| Tomas Fasth | Jan 17, 2002 1:47 pm | |
| Mark Constable | Jan 17, 2002 3:35 pm | |
| Sam Varshavchik | Jan 17, 2002 3:53 pm | |
| Petr Burian | Jan 17, 2002 4:51 pm | |
| Marcus Felipe Pereira | Jan 18, 2002 6:26 am | |
| Alexei Batyr' | Jan 18, 2002 9:01 am | |
| Roland Schneider | Jan 18, 2002 9:24 am | |
| Bill Williamson | Jan 18, 2002 9:29 am | |
| Aly S.P Dharshi | Jan 18, 2002 9:37 am | |
| William Hue | Jan 18, 2002 9:58 am | |
| William Hue | Jan 18, 2002 12:25 pm | |
| Petr Burian | Jan 18, 2002 1:09 pm | |
| William Hue | Jan 18, 2002 1:42 pm | |
| Yarema | Jan 18, 2002 1:44 pm | |
| Sam Varshavchik | Jan 18, 2002 6:12 pm | |
| Mark Constable | Jan 18, 2002 7:50 pm | |
| Sysop | Jan 18, 2002 9:36 pm | |
| David Ehle | Jan 18, 2002 9:55 pm | |
| Bill Williamson | Jan 18, 2002 10:01 pm | |
| Tomas Fasth | Jan 19, 2002 9:41 am | |
| Tomas Fasth | Jan 19, 2002 10:10 am | |
| Marcus Felipe Pereira | Jan 19, 2002 12:38 pm | |
| Mark Constable | Jan 19, 2002 11:12 pm | |
| John Laur | Jan 20, 2002 1:21 pm | |
| Olivier Poitrey | Jan 21, 2002 2:46 am | |
| Alexei Batyr' | Jan 21, 2002 5:37 am | |
| Olivier Poitrey | Jan 21, 2002 6:31 am | |
| Sam Varshavchik | Jan 21, 2002 8:14 am | |
| Stefan Kruger | Jan 23, 2002 8:21 am | |
| John Kloss | Jan 23, 2002 8:30 am | |
| Sam Varshavchik | Jan 23, 2002 3:11 pm | |
| Chester Wisniewski | Jan 23, 2002 3:50 pm |
| Subject: | [courier-users] Re: RFC2045_ERR8BITHEADER and RFC2045_ERR8BITCONTENT | |
|---|---|---|
| From: | Yarema (yd...@CoolRat.org) | |
| Date: | Jan 18, 2002 1:44:44 pm | |
| List: | net.sourceforge.lists.courier-users | |
--On Thursday, January 17, 2002 18:53:53 -0500 Sam Varshavchik <mrs...@courier-mta.com> wrote:
Mark Constable writes:
Yes to the last one. Every time I try to self-maintain various patched versions of any particular package then that need and situation deteriorates into a disaster over time but that's my problem, not courier-mta or this lists.
For the better half of last year I had to maintain my own fork of a Linux device driver, due to some bickering between the driver's official maintainer and Linus. It wasn't pretty, I hated having to rebuild the kernel each time Red Hat released an errata, but it wasn't the end of the world either. I survived. And eventually the right set of patches finally made it into the Linus tree. The world survived. -- Sam
FWIW, I too would like to see an "officially" blessed solution to the RFC2045/RFC2047 issue. Meanwhile the FreeBSD port, as the very first option, presents:
[ ] Accept8bit "http://www.Courier-MTA.org/FAQ.html#esmtperr"
this option is not on by default. But those who get too many users complaining about "important" mail not getting through will hopefully be able to follow the URL and determine if they need to enable the patch below or not. My patch is not as elegant as the one Marcus Felipe Pereira <mar...@provedor.net> provided, but it gets the job done without adding extra config options or documentation. Once again I would much prefer to see this solved in the base distribution of courier.
Honestly, I couldn't care less if my user's mail client blows up. I just point them at the URL above and tell them that's what they asked for. That takes a lot less effort than explaining to them that I'm actually protecting them from badly formatted mail that might potentially blow up their client. All I get in reply is that "it used to work before and now it doesn't -- fix your broken server".
I believe RFC2045/RFC2047 policing belongs under the BOFH section of the config or anywhere for that matter where it's tweak-able after install and not just at build time. That would make most of these silly threads go away.
Mark, I'm not that well versed in Debian's package manager. But isn't it possible to take the configs for the "official" Debian Courier-MTA package, add an RFC2045/RFC2047 patch and create your own package. In most cases that will automate the handling of new versions with just a little overhead in effort. Perhaps the Debian maintainer of the Courier package would be willing to incorporate such a patch into the official Debian package.
I too run many production servers. As nice as it might be to have everything prepackaged just the way you like it in reality local modifications are just about always necessary. Automating those local tweaks is the only way to keeps one's sanity as the number of boxes grow.
-- Yarema
--- courier/submit2.C.orig Sat Dec 15 16:19:01 2001 +++ courier/submit2.C Mon Jan 14 20:32:21 2002 @@ -800,6 +800,7 @@ return (1); }
+#if !defined(RFC2045_ERR8BITACCEPT) if (rwrfcptr->rfcviolation & RFC2045_ERR8BITHEADER) { rfcerr= SYSCONFDIR "/rfcerr2047.txt"; @@ -810,6 +811,7 @@ rfcerr= SYSCONFDIR "/rfcerr2045.txt"; dorewrite=1; } +#endif else if (rwrfcptr->rfcviolation & RFC2045_ERRBADBOUNDARY) { rfcerr= SYSCONFDIR "/rfcerr2046.txt";





