
Hello, We've upgraded from OTRS 1.3.x and now PostMasterPOP3.pl is occasionally falling over with this error: Wide character in syswrite at /usr/lib/perl5/5.8.8/Net/Cmd.pm line 436 I've attached the full output from PostMasterPOP3.pl at the end of this email. We are running: OTRS 2.0.4 Perl v5.8.8 mysql Ver 14.12 Distrib 5.0.18 Linux version 2.6.15-1.2054_FC5 Config.pm has: $Self->{'DefaultCharset'} = 'utf-8'; googling for this error message I found this open bug for perl: http://rt.cpan.org/Public/Bug/Display.html?id=18589 At the moment this is a major problem for us because we get so much spam that contains non-ascii chars, and each one causes PostMasterPOP3.pl to fall over and leave it's processID in the database, which in turn means that it won't run again, because we get this error: Can't create PID PostMasterPOP3, because it's already running If there is any patch we can apply or other way to fix the problem it would be much appreciated, because at the moment the only solution is to go into the mailbox feeding OTRS and manually delete the offending emails, which is a huge headache. Cheers, -Brendan ----------------- $ ./PostMasterPOP3.pl -f 1 -d 2 Notice: PostMasterPOP3.pl is already running but is starting again! Message 1/80 (otrs@xxxxxxxxx.com) Sub part(1/1)! ->GotArticle::Atm: 'file-1' 'text/html; charset="iso-2022-jp"' New Ticket created! TicketNumber: 2006042510000211 TicketID: 15607 Priority: 3 normal State: new CustomerID: ammy6017295@hotmail.com CustomerUser: ammy6017295@hotmail.com Wide character in syswrite at /usr/lib/perl5/5.8.8/Net/Cmd.pm line 436.

Brendan Humphreys wrote:
We've upgraded from OTRS 1.3.x and now PostMasterPOP3.pl is occasionally falling over with this error:
Wide character in syswrite at /usr/lib/perl5/5.8.8/Net/Cmd.pm line 436
[...] Config.pm has: $Self->{'DefaultCharset'} = 'utf-8';
googling for this error message I found this open bug for perl:
http://rt.cpan.org/Public/Bug/Display.html?id=18589
[...] If there is any patch we can apply or other way to fix the problem it would be much appreciated, because at the moment the only solution is to go into the mailbox feeding OTRS and manually delete the offending emails, which is a huge headache.
Do you really need UTF-8? I believe there are indeed some unresolved issues with OTRS and UTF-8. Do you still have these problems when you set your DefaultCharset to iso-8859-1? Nils Breunese.

Hi Nils,
We've upgraded from OTRS 1.3.x and now PostMasterPOP3.pl is occasionally falling over with this error:
Wide character in syswrite at /usr/lib/perl5/5.8.8/Net/Cmd.pm line 436
[...] Config.pm has: $Self->{'DefaultCharset'} = 'utf-8';
googling for this error message I found this open bug for perl:
http://rt.cpan.org/Public/Bug/Display.html?id=18589
[...] If there is any patch we can apply or other way to fix the problem it would be much appreciated, because at the moment the only solution is to go into the mailbox feeding OTRS and manually delete the offending emails, which is a huge headache.
Do you really need UTF-8? I believe there are indeed some unresolved issues with OTRS and UTF-8. Do you still have these problems when you set your DefaultCharset to iso-8859-1?
Unfortunately we do need OTRS to support UTF-8. Our company produces and supports software products that work with different character sets and we often get mails in different character sets. My understanding, from the bug report above, is that its a pretty simple fix. Regards, -Brendan
participants (2)
-
Brendan Humphreys
-
Nils Breunese (Lemonbit Internet)