What have you done to troubleshoot this, ie. identify majordomo as the
problem? What is your MTA, and version? What version of majordomo are
you running? What modifications/patches have been applied? Is your
MTA configured to allow non-ASCII characters?
Typically, majordomo could care less what is in the "BODY" of a message.
Is your global "majordomo.cf" catching "TABOO" regular expressions? Is
the problem specific to one list, or all your lists? Have you tried to
send a message with foreign characters to another list to be certain it
is not a configuration issue?
Tell us more so we can help you more.
Dan Liston
Brett Charbeneau wrote:
> One of our MJ lists is a newsletter of sorts and has a moderator who
> sends text to the list by cutting and pasting text from MS
> FrontPage-prepared HTML pages.
> Occasionally, this text contains characters from non-English sets -
> mostly accented characters and such - which majordomo seems to choke on.
> As long as these accents are in the text the message cannot be approved
> for distribution. Once they are manually removed, the messages go out fine.
> I originally asked the moderator to past her text into Notepad to
> 'normalize' the text, and THEN cut and past into Pine for and MJ post,
> but many of these characters seem to survive this.
> Is there a way to force MJ to ignore these kinds of characters in
> the body of a post?
>
Follow-Ups:
References:
|
|
