4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] AH HA!!!
FromSent OnAttachments
Randall ShawAug 2, 2002 2:38 pm 
secure42Aug 2, 2002 4:03 pm 
Randall ShawAug 3, 2002 10:29 am 
secure42Aug 4, 2002 6:27 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] AH HA!!!Actions...
From:secure42 (secu@flashmail.com)
Date:Aug 2, 2002 4:03:05 pm
List:net.sourceforge.lists.courier-users

Ok, you workaround the problem, but you did not solve it!! Problem is that you are composing a mail that contain not ascii characters and you have to add the property MIME headers on it. PHP mail() functions do not add them by itselfs, so you have to add them.

This message will work properly:

mail("joec@example.com", "My Subject", "Message");

but this message is not RFC compliant: mail("joec@example.com", "My Subject", "Some other characters: ñ, ü");

Many php apliccations out there (PHPNUKE, POSTNUKE ...) send not rfc mails and should be fixed.

Randall Shaw wrote:

=) Re: The "CORRUPTED MESSAGE" bs...

Found the problem, and found the solution.

Problem: A word with a (tm) (tiny tm char typed by macs), was throwing courier into a tissy, because php (and the rest of the world apparently) doesn't rightly care.

Solution: Made a new file called "~/courier/etc/bofh" and added only: "opt BOFHBADMIME=accept"

I had added the BOFHBADMIME=accept to the smtpaccess file, but it did nothing to help... so I assume it doesn't look there for local made mails.

Anyhow, it works like expected now... carry on.