On 12.05.2011, at 09:59,
we have lots of errors of this form in otrs.log: [Wed May 11 04:56:09 2011][Error][Kernel::System::MailAccount::IMAPS::_Fetch][159] IMAPS: Can't process mail, email no 17 is empty!
We are fetching on our linux system (SLES11) from an Exchange (2010 afaik) server. Can anyone shed a light on a) if mails will get lost
I don’t think that you will loose emails because ...
b) how that error could occur (no one sends empty mails to that addresses)
... this seems to happen on MS Exchange only, due to a slow behavior of MS Exchange. Did you modify the interval for fetching emails in the CronJob definition in /opt/otrs/var/cron/postmaster_mailbox? I experienced similar issues with MS Exchange when fetching email more often than every 3 minutes. One of our customers explained to me a few months ago: "MS Exchange doesn’t update the list of available/unread emails upon fetch, so it could be that it tells you a list of available messages where some of them are fetched and unavailable already.” Not sure how to come around this on OTRS site without reducing the fetch interval ... try with 3 minutes. A permanent and recommended solution is to move from fetching emails (POP3 or IMAP) to receiving emails (SMTP). Cheers, Nils -- Nils Leideck http://webint.cryptonode.de / a Fractal project