Message: 7
Date: Mon, 15 Nov 2010 16:45:34 +
From: Timo Sirainen
Subject: Re: [Dovecot] proctitle woes with 2.0.7 vs. 2.0.6
To: Clemens Schrimpe
Cc: Dovecot Mailing List
Message-ID: <1289839534.1764.138.ca...@kurkku.sapo.corppt.com>
Content-Type: text/plain; charset="UTF-8"
On Sat, 2010-11
> On 8/29/2010 8:51 PM, Patrick Fay wrote:
>> Aug 26 20:43:45 hostname Firewall[55]: Deny ^L connecting from
>> XX.XX.XX.XX:37310 uid = 0 proto=6
>> Aug 26 20:43:53 hostname Firewall[55]: Deny ^H?^U???^Z connecting from
>> XX.XX.XX.XX:37310 uid = 0 proto=6
>>
Hi,
Thanks everyone for your help and input. I think perhaps my attempt to be
brief and focused in posing my question has led to some confusion about my
needs and configuration. I do not have the luxury of being able to segregate
the server (postfix and dovecot) from client (GUI, etc) on di
>
Hi,
I am running dovecot 1.2.11 on mac osx 1.5.8. Everything works
perfectly with the application-level firewall off, but enabling the
application firewall prevents dovecot connections. I have tried
explicitly authorizing dovecot in the firewall, but it does not work
>> Hi,
>>I am running dovecot 1.2.11 on mac osx 1.5.8. Everything works
>> perfectly with the application-level firewall off, but enabling the
>> application firewall prevents dovecot connections. I have tried
>> explicitly authorizing dovecot in the firewall, but it does not work. I
>> have
Hi,
I am running dovecot 1.2.11 on mac osx 1.5.8. Everything works
perfectly with the application-level firewall off, but enabling the
application firewall prevents dovecot connections. I have tried
explicitly authorizing dovecot in the firewall, but it does not work.
I have searche
