Re: [Dovecot] couple of errors on new setup

2013-10-06 Thread Noel Butler
On 06/10/2013 03:16, Dean Guenther wrote: mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl mbox over NFS has *never* been recommended, it is unsafe - for any pop/imap type server, not just dovecot. If its not too late, and since yo

[Dovecot] Transparent Migration from cyrus to dovecot

2013-10-06 Thread Jogi Hofmüller
Hi dovecot people, We are in the process of preparing the migration from a cyrus 2.1 installation to dovecot. Dovecot will be installed on new hardware, so we have separated servers that can/will exist in parallel for a while. Our goal is to do the migration without interrupting the service for

[Dovecot] retr errors

2013-10-06 Thread Bill Morgan
My ISP uses Dovecot and I have had an ongoing problem for a while using several email clients. Sometimes the response to a retr request is mal-formed. The expected response "+OK nnn octets" is not returned. The response looks like it started somewhere in the message headers. Sometimes a retry

[Dovecot] State of the FTS modules and packaging

2013-10-06 Thread Benjamin Podszun
Hi there. I'm running a small (VPS) mail system just for myself for quite a while and want to support some friends and family now. For that I'm improving / documenting the setup. One thing I never cared to implement was FTS support. Looking at the options [1] now, I'm stuck. I don't want sol

Re: [Dovecot] couple of errors on new setup

2013-10-06 Thread Timo Sirainen
On 6.10.2013, at 4.04, Noel Butler wrote: > mail_nfs_index = yes > mail_nfs_storage = yes These are never recommended. They may be a kludgy workaround to avoid worst problems, but they will never work 100% In the recommended configurations (one Dovecot server or director cluster) you won't nee

[Dovecot] Problems getting Squirrelmail and Avelsieve to connect to Pigeonhole

2013-10-06 Thread Steve
Hi, I have been going around in circles trying to find the solution. Many others appear to have the same problem, but never a solution or explanation. I am running Dovecot 2.0.21 under Fedora 16. All components are running on the same server, whose IP address is shown as '192.168.x.y'. The

Re: [Dovecot] Problems getting Squirrelmail and Avelsieve to connect to Pigeonhole

2013-10-06 Thread Stephan Bosch
On 10/6/2013 9:01 PM, Steve wrote: > Running/*# /usr/sbin/ngrep -d lo port 4190 */produces the following > trace: > >/##/ >/T 127.0.0.1:35495 -> 127.0.0.1:4190 [AP]/ >/ AUTHENTICATE "PLAIN" \{28+}.. / >/##/ >/T 127.0.0.1:35495 -> 127.0.0.1:4190 [AP]/ >/c3RldmUAc3RldmUAbWFna

Re: [Dovecot] SSL with startssl.com certificates

2013-10-06 Thread Dan Langille
On Sep 17, 2013, at 10:59 AM, Bruno Tréguier wrote: > Le 17/09/2013 à 16:32, Dan Langille a écrit : >> $ openssl s_client -connect imaps.unixathome.org:993 -quiet >> depth=0 >> /description=P4s7A2l6clvQRRJ4/C=US/CN=imaps.unixathome.org/emailAddress=postmas...@unixathome.org >> >> verify error:nu

Re: [Dovecot] Transparent Migration from cyrus to dovecot

2013-10-06 Thread Ed W
Make use of the proxy feature. You can add a "server" entry into your userdb, that way you can literally move users over one by one and flip their server location. You can easily test individual users and move them over individually. Works brilliantly Ed W On 06/10/2013 11:39, Jogi Hofmül

Re: [Dovecot] SSL with startssl.com certificates

2013-10-06 Thread Reindl Harald
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: Warning: SSL failed: where=0x2002: >

Re: [Dovecot] retr errors

2013-10-06 Thread Daniel Parthey
Hi Bill You should send the wireshark traces to your ISP and ask him to fix it. At least one would require the doveconf -n output and the version of dovecot. Probably a bug in an older dovecot version? Regards Daniel

Re: [Dovecot] retr errors

2013-10-06 Thread Daniel Parthey
Hi Bill, any intercepting virus scanner or personal firewall software between your mail client and the dovecot server? Regards Daniel

[Dovecot] smartsieve managesieve-login failure with dovecot 2.1.7

2013-10-06 Thread Wouter Berkepeis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I just subscribed to the mailing list because I am stuck trying to solve a problem getting smartsieve to work with a new version of dovecot. But let me first explain the situation shortly. I am running a mail server at home for personal use, a

Re: [Dovecot] couple of errors on new setup

2013-10-06 Thread Noel Butler
On 07/10/2013 04:58, Timo Sirainen wrote: On 6.10.2013, at 4.04, Noel Butler wrote: mail_nfs_index = yes mail_nfs_storage = yes These are never recommended. They may be a kludgy workaround to avoid worst problems, but they will never work 100% In the recommended configurations (one Dovecot s

Re: [Dovecot] retr errors

2013-10-06 Thread Bill Morgan
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 and the ISP wasn't interested in the wireshark traces. I know, I should change the ISP and see if the

Re: [Dovecot] retr errors

2013-10-06 Thread Noel Butler
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 As I'm sure Daniel was implying, did you also test without

Re: [Dovecot] Transparent Migration from cyrus to dovecot

2013-10-06 Thread Darren Pilgrim
On 10/6/2013 1:56 PM, Ed W wrote: Make use of the proxy feature. You can add a "server" entry into your userdb, that way you can literally move users over one by one and flip their server location. You can easily test individual users and move them over individually. Works brilliantly Second

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

2013-10-06 Thread Mauricio Tavares
On Thu, Sep 19, 2013 at 2:40 AM, Noel Butler wrote: > On Thu, 2013-09-19 at 00:50 -0400, Mauricio Tavares wrote: > >> So in 1.2.9 I had something like this: >> >> [...] >> >> socket listen { >> master { >> path = /var/run/dovecot/auth-master >> mode = 0600 >

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

2013-10-06 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