Hi Marco.
It occurs with our 2.4.10 installation. Switching from POP3S to IMAPS and increasing the frequency of fetching mails (every nine minutes atm) helped a little.
I have no idea where this comes from exactly, but I’m pretty sure it belongs to the imo heavy use and the high number of POP3 accounts and mails within these. I haven’t seen this behavior on our 3.0 or 3.1 installations (which have much lower load).
Regards
Jan Dreyer
Depends a lot on the POP server implementation, too. If the POP server is set to rate-limit incoming connections (default on recent versions of Exchange, and most of the “free” email providers these days), the client (in this case, OTRS) will see the full list of messages in the mailbox, but will be allowed to get only a certain number per connection attempt, and will not be able to connect more than once per X minutes. This confuses the OTRS POP client a lot.
The best permanent solution we’ve found is to use fetchmail to interact with the POP server, and a local SMTP server listening only on the loopback address with local aliases for the OTRS queues. Fetchmail is much smarter about dealing with obscure remote mailbox problems, and has super-helpful logging if it has problems.
at which point the local aliases file works about equally well
One thing I did use procmail for at one implementation was to alert a department manager (cc email) when a ticket request came from a department employee. Of course, it didn't have the ticket number, but otherwise it was a good-enough workaround.
Yeah – there is where procmail really shines. You can do all sorts of useful things to the incoming email before it hits OTRS.