And in my case, I use procmail which has none of these issues and receives mail instantly into OTRS.
On Tue, Oct 2, 2012 at 4:13 PM, David Boyes <[email protected]> wrote: > 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. > > > > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
