Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Stephan Bosch
On 10/7/2013 1:01 AM, Wouter Berkepeis wrote: Everything OK I guess. Especially the first part of the output is interesting: IMPLEMENTATION Dovecot Pigeonhole This is what Smartsieve is looking at. With the former version the string was 'dovecot', so I changed this in the 'Managesieve.php'

Re: [Dovecot] retr errors

2013-10-07 Thread Przemysław Orzechowski
W dniu 07.10.2013 03:33, Noel Butler pisze: On 07/10/2013 11:19, Bill Morgan wrote: On 10/6/2013 5:58 PM, Daniel Parthey wrote: Hi Bill, any intercepting virus scanner or personal firewall software between your mail client and the dovecot server? Regards Daniel McAfee I would

Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Benny Pedersen
Wouter Berkepeis skrev den 2013-10-07 01:01: dovecot-info.log: 2013-10-06 21:16:20 managesieve-login: Info: Disconnected (no auth attempts in 0 secs): user=, rip=127.0.0.1, lip=127.0.0.1, TLS handshaking: SSL_accept() failed: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake

Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Benny Pedersen
Stephan Bosch skrev den 2013-10-07 08:54: And yes, SmartSieve is unmaintained, so I would not recommend using it anymore. just sad it is not, its imho still the best standalone webui for sieve

Re: [Dovecot] Yet another going from 1.2 to 2.X question: authentication

2013-10-07 Thread Noel Butler
On 07/10/2013 14:17, Mauricio Tavares wrote: Makes sense, so I shall set them up as /etc/dovecot/conf.d/10-master.conf # http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL service auth { unix_listener auth-userdb { mode = 0600 user = virtual #

[Dovecot] Replication: long detalys

2013-10-07 Thread Lucas Rothamel - Eye Catching Webdesign
Hello everybody, I am running dovecot 2.1.7 on Debian Wheezy on two servers with replication set up, MTA is postfix. The idea is to have a redundant mail system so that when one server fails, users can continue using the other server (failover of POP/IMAP through DNS redirection). Servers are

Re: [Dovecot] retr errors

2013-10-07 Thread Charles Marcus
On 2013-10-06 9:19 PM, Bill Morgan b...@bmorgan.com wrote: On 10/6/2013 5:58 PM, Daniel Parthey wrote: Hi Bill, any intercepting virus scanner or personal firewall software between your mail client and the dovecot server? McAfee Well, I'd just stop right there, fire whoever installed

Re: [Dovecot] Replication: long detalys

2013-10-07 Thread Oli Schacher
On Mon, 07 Oct 2013 12:35:10 +0200 Lucas Rothamel - Eye Catching Webdesign i...@eye-catching-webdesign.de wrote: Hello everybody, I am running dovecot 2.1.7 on Debian Wheezy on two servers with replication set up This kind of setup is recommended on dovecot 2.2+ only.

Re: [Dovecot] SSL with startssl.com certificates

2013-10-07 Thread Dan Langille
On 2013-10-06 17:06, Reindl Harald wrote: Am 06.10.2013 22:42, schrieb Dan Langille: I have Thunderbird working just fine on my Macbook. But my goal is mail.app on my iPhone and my Macbook. When they try to connect, the mail server logs are: Oct 6 20:20:25 imaps dovecot: imap-login:

Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Wouter Berkepeis
Hello Stephan, Thanks for the answer. I also thought it should work this way. Thank you for the suggestion using rawlog, hopefully I can find out why it does not work (yet). Complicating factor is that I run 2 versions of SmartSieve on two different machines, the old one for everyday use, and the

Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Wouter Berkepeis
Thanks for the reply. I already tried all possible options in server.php : from 993/imap/ssl/novalidate-certs to 143/imap/notls with setting use_starttls to false. It seems that smartsieve/managesieve-login is always trying to setup a secure connection. Looking at my log files TLS handshaking is

[Dovecot] Proxy to gmail not working

2013-10-07 Thread Alex Wanderley
Hi, I've been trying to build a password forwarding proxy to Gmail without success... The SSL connection to Dovecot is happening no problem (as far as I can tell), but for some reason the conversation between Dovecot and Gmail is getting timed out. I know this is supposed to be simple... :-(

Re: [Dovecot] Proxy to gmail not working

2013-10-07 Thread Charles Marcus
On 2013-10-07 12:11 PM, Alex Wanderley alex.wander...@edmonton.ca wrote: # OS: Linux 2.6.18-308.8.2.el5xen x86_64 CentOS release 5.8 (Final) Aaaack! Makes me wonder what vancient version of openssl, and maybe that is the culprit?

Re: [Dovecot] Proxy to gmail not working

2013-10-07 Thread Reindl Harald
Am 07.10.2013 18:37, schrieb Charles Marcus: On 2013-10-07 12:11 PM, Alex Wanderley alex.wander...@edmonton.ca wrote: # OS: Linux 2.6.18-308.8.2.el5xen x86_64 CentOS release 5.8 (Final) Aaaack! Makes me wonder what vancient version of openssl, and maybe that is the culprit?

Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Benny Pedersen
Wouter Berkepeis skrev den 2013-10-07 18:04: Thanks for the reply. I already tried all possible options in server.php : from 993/imap/ssl/novalidate-certs to 143/imap/notls with setting use_starttls to false. It seems that smartsieve/managesieve-login is always trying to setup a secure

Re: [Dovecot] SSL with startssl.com certificates

2013-10-07 Thread Bruno Tréguier
Le 06/10/2013 à 22:42, Dan Langille a écrit : After a long delay, I'm ready to tackle this again. [...] Testing via the command line gives: $ openssl s_client -connect imaps.unixathome.org:993 CONNECTED(0003) depth=2 C = IL, O = StartCom Ltd., OU = Secure Digital Certificate Signing,

Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Wouter Berkepeis
inline: fdfdeege.png

Re: [Dovecot] Proxy to gmail not working

2013-10-07 Thread Joseph Tam
On Mon, 7 Oct 2013, Alex Wanderley writes: passdb { args = proxy=y nopassword=y user=remotemail destuser=remotemail@gmail.comhost= pop.gmail.com port=995 proxy_timeout=15 starttls=y driver = static } ... Oct 7 09:33:13 dserver dovecot: auth: Debug: client passdb out: OK 2

Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Benny Pedersen
Wouter Berkepeis skrev den 2013-10-07 20:37: Thanks for the tip. I had to disable ssl completely to finally login to SmartSieve. But then I saw that the interface is 'crippled', it's missing some parts. I don't know what is causing that, but I've had it with SmartSieve for now. Which is a

Re: [Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-07 Thread Wouter Berkepeis
Hello Benny, Thanks for your response. Ingo looks promising to me as a sufficient solution, but on the Ingo site one of the stated prerequisites is : (start quote) To function properly, Ingo *requires* the following: A working Horde installation Ingo runs within the Horde Application