-
All replies
-
Helpful answers
-
Oct 11, 2014 1:33 AM in response to Masta Mastenby MarkusLoeberbauer,I have the same error, the log entry is (for this post i changed the domain to xxx.xx, other than that it is the original messes, up to an and including the typo in the error message, it really says "charracters" with two "r"s.):
Oct 11 09:32:14 xxx.xx postfix/local[4556]: 6B01FD32027: to=<partner@xxx.xx>, relay=local, delay=0.04, delays=0/0/0/0.04, dsn=5.3.0, status=bounced (Command died with status 1: "/Applications/Server.app/Contents/ServerRoot/usr/libexec/MailService/list_serv er_post post partner". Command output: /Applications/Server.app/Contents/ServerRoot/usr/libexec/MailService/list_serve r_post invalid charracters in message )
Additional information:
- The text in the message is not important, I don't get any message delivered, even an empty one.
- OS X version is: 10.9.5
- Server version in: 3.2.1
- Before the update the list worked and I had OS X 10.9.4 and Server 3.1.2
I hope this information helps to find the bug.
Best regards,
Markus
-
Oct 28, 2014 2:42 AM in response to MarkusLoeberbauerby eimann,We are seeing the same issues, same releases as Markus.
-
Nov 9, 2014 8:47 AM in response to eimannby sweh,Same here, too. I wonder about the misspelling in the error message: charracters
-
Nov 24, 2014 12:33 PM in response to swehby glen.circle,I've isolated the problem on my site to sending group emails from Thunderbird, when there are accented characters (say a single é) in the message body.
This can be a plain text or html (multipart) - as long as the Content-Transfer-Encoding header says "8bit", the list server will bail. Any other individuals in the "To:" field receive the message normally, but the local group email addresses make list_server_post fail and return "invalid charracters in message".
Outlook and Apple Mail seem unaffected, possibly because Outlook doesn't set a transfer encoding and Apple Mail uses "quoted-printable".
-
Dec 14, 2015 5:35 PM in response to glen.circleby CILT I.T.,I'm experiencing the same issue and the summary of the problem by glen.circle above seems a very accurate description of what I am seeing.
We are still running OSX 10.9.5 + Server 3.2.2 and what I would like to know is if upgrading to OSX 10.10 or 10.11 has solved this problem for any users who experienced this problem while running 10.9.
Any shared experiences about whether upgrading solved this problem or not, or any other solutions to this problem would be greatly appreciated.
Thanks.
-
