Lucio Crusca writes:
Sam Varshavchik writes: > Lucio Crusca writes: > > I ask that because I already have "opt BOFHBADMIME=accept" in place, I > > know that it implies "opt MIME=none" and I don't feel like changing it > > if it hasn't > > No, the two are independent settings. The first one controls what gets > accepted for incoming mail. The second one enables or disables MIME > encoding of messages that are accepted."man courier" says: Note BOFHBADMIME=accept implies MIME=none (see submit(8)[5] for more information). Does that mean that there are two different "opt MIME=..." settings, one for incoming mail and one for outgoing?
This means that for the older version of Courier you're running, that value of BOFHBADMIME forced MIME=none, basically the MIME setting is ignored.
BOFHBADMIME was removed in 0.66.0, and that section of the man page is no longer there.
pgpyXjdGeexKT.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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
