Why don't you use 'the easy way' (according to the docs) which uses
PostMasterPOP3.pl? See the docs:
http://doc.otrs.org/2.0/en/html/x1244.html#email-receiving-pop3
Well I do use PostMasterPOP3.pl at this moment. Two things I don't like:
- Cron running the script every 5 minutes, even if there
Hi all,
otrs (2.0.4.-01), default charset utf-8,
every mail with the charset=ISO-8859-2 in the header make this error:
./PostMasterPOP3.pl
Message 1/21 ([EMAIL PROTECTED])
Wide character in subroutine entry at
/opt/otrs/Kernel/System/Ticket/ArticleStorageDB.pm line 249.
or
this error:
Richard Hinkamp wrote:
Why don't you use 'the easy way' (according to the docs) which
uses PostMasterPOP3.pl? See the docs: http://doc.otrs.org/2.0/en/
html/x1244.html#email-receiving-pop3
Well I do use PostMasterPOP3.pl at this moment. Two things I don't
like:
- Cron running the script
- Cron running the script every 5 minutes, even if there may be no
mail at all.
What's the problem with that?
Unneeded CPU usage.
And if there's mail, there is a max 5 minute delay in getting the mails.
You can change the time between checks in the cronjob.
Yes, I can set the cronjob to
Hi I have seem this same thing happen. but in my case charset=iso-8859-15. This
happens in my case when the ticket gets created with a question mark in the
subject or body. I have not figured out the problem yet, but would be
interested in knowing the 'cure' for this problem.
thanks, Lief
We are still experiencing some very annoying behavior after moving to
a new SMTP account.
Agent Notifications from the Agent site and email ticket replies from
the Agent Site go through perfectly.
All the automatic notifications fail.
The otrs log says:
[Fri Aug 4 09:40:13
