In data lunedì 8 ottobre 2012 14:30:33, Sam Varshavchik ha scritto: > Well, since mail delivery for them is such a low priority, I see no reason > why anyone else has to be concerned, either.
Sure. However it happens I have two customers. The first buys email service from me. The second buys software support, but uses Aruba mail services. Aruba mail services here are considered to be standard and working also when they do not work, because many people use them. You can look at it as if it were a de-facto standard. Now here the world is to little that those two customers are also in contact between each other, and the first needs to send emails with attachments to the second. In order to workaround the problem I had set up a ftp server for the first. However this changes my second customer workflow, who is willing to charge my first customer for the added service of receiving attachments via ftp... and I'm seen as the guilty for the situation just because I switched from Postfix to the brand new Courier mailserver and what before worked now it doesn't work anymore. So that's the reason why I have to be concerned... > > My workaround would be to force 8bit mime conversion on all outgoing > > messages. > > Why exactly do you believe this would be a workaround? If you do not know > the actual issue that's causing your problem, at most what you have is a > guess. Yes it's only a guess. I guess those 7bit data errors are related to the mime type of messages being 7bit and some 7bit messages being broken. I then guess Courier passes those broken messages almost untouched to the recipient mail server, while Postfix "fixed" those messages somehow. Maybe my guesses are all wrong, but, if enabling 8bit conversion doesn't cause any harm, it may be worth a try. > > The docs say I should set the MIME env variable to "8bit" for that. > > Assuming my workaround makes any sense, where should I set the value for > > the MIME env variable? Is there any configuration file better suited for > > that assignment? > > For this particular case, you would put > > opt MIME=8bit > > into the courier configuration file. But, I think it's unlikely that this > will make much of a difference. I'm hoping that avoiding 7bit mime messages will workaround the recipient (comcast) mailserver bug. Obviously this assumes that 7bit data errors and 7bit mime messages are somehow related to each other. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
