On 9/22/10 1:58 PM, Ludovic Marcotte wrote:
On 22/09/10 3:48 PM, Chris Hobbs wrote:
And I meant to mention that there are not corresponding errors in our
dovecot logs.
Not that I don't trust you but I find it strange that SOGo tries to
connect, simply can't and you don't see anything in your Dovecot logs.
I hear you, and was surprised myself. That's why I was running
simultaneous "tail -f" on both servers' log files and watched the sogo
errors scrolling by while dovecot was quiet.
Perhaps it was a network error at that time? (lame or buggy switch,
flaky network cable or vacuum-cleaner-used-too-close-of-your-gears)
I wish it were that easy, but both are servers are VMs running in the
same ESX host, so I don't think we're dealing with network issues. And
switching back to 1.3.0 resolved things instantly.
--
Chris Hobbs
Director, Technology
New Haven Unified School District
--
This message was scanned by ESVA and is believed to be clean.
--
[email protected]
https://inverse.ca/sogo/lists
