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

[Benny Pedersen]

Wouter Berkepeis skrev den 2013-10-08 07:49:
So, if I can install Ingo without Horde as you say, I would be more 
then

happy.


yes ingo needs horde framework, but not the full horde problem to run

Btw, my remark about the LDAP authentication with Squirrelmail being 
too

tricky to implement maybe wasn't described right.


you dont need auth in squirrelmail, its imap auth in the first place


What I meant was it's
not worth the efforts installing all this, just to be able to manage
sieve filters from inside another program. I have installed 
Squirrelmail
for just being able to look now and then at my e-mail at public 
places,

I don't use it frequently.


if all needed tools is missing in debian why use it ?

create a launchpad bug of have ingo installed via apt-get will be next 
step



Anyway, thanks for your little help. :-)


no problem

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

[Simon B]

On 8 Oct 2013 07:50, "Wouter Berkepeis"  wrote:
>
> 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 Framework
> , a set of common tools for web
> applications written in PHP. You must install Horde before installing
Ingo.
>
> (end quote)
>
> So, if I can install Ingo without Horde as you say, I would be more then
> happy.
>
> Btw, my remark about the LDAP authentication with Squirrelmail being too
> tricky to implement maybe wasn't described right. What I meant was it's
> not worth the efforts installing all this, just to be able to manage
> sieve filters from inside another program. I have installed Squirrelmail
> for just being able to look now and then at my e-mail at public places,
> I don't use it frequently.
>
> Anyway, thanks for your little help. :-)

A working horde installation is in this case the horde package.  If you
don't need to install webmail, address book, calendar, tasks, you don't
have to. Let alone the wiki, photo gallery, bookmark manager or ticket
interface.

Just install horde and Ingo and be done.

You may find it useful to install imp too -to take care of the
authentication, but you don't have to show it to the user.

And installing by pear couldn't be easier.  Why do you need a  debian
package?

Simon

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

[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 Framework
, a set of common tools for web
applications written in PHP. You must install Horde before installing Ingo.

(end quote)

So, if I can install Ingo without Horde as you say, I would be more then
happy.

Btw, my remark about the LDAP authentication with Squirrelmail being too
tricky to implement maybe wasn't described right. What I meant was it's
not worth the efforts installing all this, just to be able to manage
sieve filters from inside another program. I have installed Squirrelmail
for just being able to look now and then at my e-mail at public places,
I don't use it frequently.

Anyway, thanks for your little help. :-)

Regards,
Wouter


On 10/08/2013 07:24 AM, Benny Pedersen wrote:
> 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 pity because it's the only
>> stand-alone (web)gui, as far as I know.
>
> ingo does not need full horde install, wake up :)
>
>> Looking for alternatives I already came across Ingo. But this is part of
>> the Horde suite and Horde is not part of Debian Wheezy.
>
> make a virtualbox with gentoo then where its supported :)
>
>> And I don't like
>> that I have to use a whole suite just for managing my sieve filter
>> settings.
>
> who sayed that ?
>
>> Another alternative maybe could be the Avelsieve plugin for
>> Squirrelmail.
>
> or roundcube ?
>
>> But with LDAP authentication I am using I also have to
>> install the LDAP backend plugin.
>
> nope, if you use webmail its done
>
>> It's becoming a bit too tricky for me,
>
> come on, you manage debian ?
>
>> and again, I have to use another program just to manage sieve.
>
> upto you, i just show you little help in solve it
>
>> So, I guess, maybe it's time to pick up my rusty programming skills and
>> create a gui myself
>
> its opensource
>

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

[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 pity because it's the only
stand-alone (web)gui, as far as I know.


ingo does not need full horde install, wake up :)

Looking for alternatives I already came across Ingo. But this is part 
of

the Horde suite and Horde is not part of Debian Wheezy.


make a virtualbox with gentoo then where its supported :)


And I don't like
that I have to use a whole suite just for managing my sieve filter
settings.


who sayed that ?


Another alternative maybe could be the Avelsieve plugin for
Squirrelmail.


or roundcube ?


But with LDAP authentication I am using I also have to
install the LDAP backend plugin.


nope, if you use webmail its done


It's becoming a bit too tricky for me,


come on, you manage debian ?


and again, I have to use another program just to manage sieve.


upto you, i just show you little help in solve it

So, I guess, maybe it's time to pick up my rusty programming skills 
and

create a gui myself


its opensource

Re: [Dovecot] Proxy to gmail not working

[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   user=remotemailproxy   nopassword=ydestuser=
remotem...@gmail.comhost=pop.gmail.com  port=995proxy
_timeout=15starttls=y  hostip=74.125.142.108   pass=123456789
Oct  7 09:33:13 dserver dovecot: pop3-login: Debug: Ignoring unknown passdb
extra field: nopassword
Oct  7 09:33:28 dserver dovecot: pop3-login: Error: proxy(remotemail):
Login for pop.gmail.com:995 timed out in state=0 (after 15 secs,
local=162.106.yyy.zzz:59282)


Idle speculation, but remote port 995 usually means SSL type connection
(i.e. dive right into SSL protocol), whereas "starttls=y" starts out in
plaintext, and SSL negotiations starts after a STARTTLS directive.

Looking at

http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy

methinks you want to replace "starttls=y" with "ssl=yes".

Joseph Tam 

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

[Wouter Berkepeis]

<>

Re: [Dovecot] SSL with startssl.com certificates

[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, 
> CN = StartCom Certification Authority
> verify error:num=19:self signed certificate in certificate chain
> verify return:0

Ok, this is fine, and different from the result you were getting a few
weeks ago. Your cert chain is ok, it seems. The "errornum=19:self signed
certificate in certificate chain" is a "normal" errot, due to the fact
that you didn't tell openssl where to find a list of valid root certs.


> All looks good.
> 
> /var/log/maillog shows:
> 
> Oct  6 20:06:28 imaps dovecot: imap-login: Login: user=, method=PLAIN, 
> rip=98.111.147.220, lip=199.233.228.197, mpid=81052, TLS, 
> session=
> Oct  6 20:08:21 imaps dovecot: imap(dan): Disconnected: Logged out in=26 
> out=691
> 
> 
> 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: 
> SSLv3 read client certificate A [98.111.147.220]
> Oct  6 20:20:25 imaps dovecot: imap-login: Disconnected (no auth attempts in 
> 1 secs): user=<>, rip=98.111.147.220, lip=199.233.228.197, TLS handshaking: 
> Disconnected, session=
> 
> Yet, the same iPhone and Macbook connect fine to a dovecot 1.2.17 
> installation.  That's my current IMAP server.  I'm moving to another server 
> and failing so far.
> 
> Suggestions to use another client app or platform will not be entertained, 
> because, clearly, this works with dovecot 1.

Well, sorry but no further suggestions as far as I'm concerned then,
except that some people tend to think that mail.app is pretty crappy and
behaves quite strangely in certain situations...

Best regards,

Bruno

-- 
- Service Hydrographique et Oceanographique de la Marine  -  DMGS/INF
-  13, rue du Chatellier -  CS 92803  - 29228 Brest Cedex 2, FRANCE
- Phone: +33 2 98 22 17 49  -  Email: bruno.tregu...@shom.fr

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

[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 connection. Looking at my log files 
TLS

handshaking is always been done. I don't know what is causing this
behaviour.


well then change to http://www.horde.org/apps/ingo with is still 
maintained


i have lost how to solve it in smartsieve, if you only want to have 
webui with smartsieve it possible to disable tls for the dovecot part on 
port 2000 / 4190, this is fine for connection as long is just loopback 
interface, its still possible to have smartsieve on a https webpage

Re: [Dovecot] Proxy to gmail not working

[Reindl Harald]

Am 07.10.2013 18:37, schrieb Charles Marcus:
> On 2013-10-07 12:11 PM, Alex Wanderley  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?

openssl-0.9.8e - so what - better read more than 1 line before answer

Port 995 *is not* STARTTLS and *that* is the reason

http://en.wikipedia.org/wiki/STARTTLS
STARTTLS is *always* the default port and starts unecrypted
while POP3S/IMAPS starts with a SSL handshake

>> passdb {
>>  args = proxy=y nopassword=y user=remotemail 
>> destuser=remotemail@gmail.comhost=
>> pop.gmail.com port=995 proxy_timeout=15 starttls=y
>>  driver = static
>> }



signature.asc
Description: OpenPGP digital signature

Re: [Dovecot] Proxy to gmail not working

[Charles Marcus]

On 2013-10-07 12:11 PM, Alex Wanderley  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?

[Dovecot] Proxy to gmail not working

[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...  :-(But could somebody please
give me some help by pointing what I'm not doing right?
No matter how much I've been researching about this, I can't find the
solution.

Thanks a lot,

Alex

# 2.2.5: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-308.8.2.el5xen x86_64 CentOS release 5.8 (Final)
auth_cache_negative_ttl = 10 mins
auth_cache_size = 1 k
auth_cache_ttl = 10 mins
auth_debug = yes
auth_debug_passwords = yes
auth_mechanisms = cram-md5 digest-md5 apop login plain
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@%
auth_username_translation =
%@AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz
auth_verbose = yes
base_dir = /var/run/dovecot/
listen = 162.106.yyy.zzz
login_greeting = Dovecot Ready
login_log_format_elements = %u %r %m %c
mail_debug = yes
mail_max_userip_connections = 100
passdb {
  args = proxy=y nopassword=y user=remotemail destuser=remotemail@gmail.comhost=
pop.gmail.com port=995 proxy_timeout=15 starttls=y
  driver = static
}
protocols = pop3
service pop3-login {
  client_limit = 200
  inet_listener pop3 {
address = dserver
port = 110
  }
  process_limit = 1
  process_min_avail = 1
  service_count = 0
  vsz_limit = 256 M
}
ssl = required
ssl_ca = ): lookup
Oct  7 09:33:13 dserver dovecot: auth: Debug:
static(remotemail,162.106.xxx.yyy,): Allowing any password
Oct  7 09:33:13 dserver dovecot: auth: Debug: client passdb out: OK
2   user=remotemailproxy   nopassword=ydestuser=
remotem...@gmail.comhost=pop.gmail.com  port=995proxy
_timeout=15starttls=y  hostip=74.125.142.108   pass=123456789
Oct  7 09:33:13 dserver dovecot: pop3-login: Debug: Ignoring unknown passdb
extra field: nopassword
Oct  7 09:33:28 dserver dovecot: pop3-login: Error: proxy(remotemail):
Login for pop.gmail.com:995 timed out in state=0 (after 15 secs,
local=162.106.yyy.zzz:59282)
Oct  7 09:33:34 dserver dovecot: pop3-login: Aborted login (internal
failure, 1 successful auths): remotemail, 162.106.xxx.yyy, PLAIN, TLS
Oct  7 09:33:34 dserver dovecot: pop3-login: Debug: SSL alert: close notify
[162.106.xxx.yyy]

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

[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 always been done. I don't know what is causing this
behaviour.

On 10/07/2013 12:06 PM, Benny Pedersen wrote:
> 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 failure: SSL alert number
>> 40, session=
>> syslog:
>
> setup smartsieve to disable tls, then it works
>
> edit in servers.php
>

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

[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 new one for testing inside my lan. Always a bit tricky these do not
interfere. For testing managesieve(-login) I also used the Thunderbird
sieve plugin. This is working ok for the new setup, I can actually log
in and send and save sieve settings on the server (a lot of s's...:-) ).
So Dovecot is working ok, it's the client side causing the problem.

Regards,

Wouter

On 10/07/2013 08:54 AM, Stephan Bosch wrote:
> 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' file.
>> This file was already patched as stated on the site. Furthermore I
>> changed everything referring to port 2000 to port 4190.
> That should work. I used the patch mentioned here:
>
> http://www.mail-archive.com/dovecot@dovecot.org/msg21862.html
>
> And modified it for the new situation. I'm assuming this is very similar
> to what you're doing and here it works.
>
> You could try to obtain more information by logging the protocol exchange:
>
> http://wiki2.dovecot.org/Debugging/Rawlog
>
> Alternatively you can debug Smartsieve by adding more logging into the
> source code.
>
> And yes, SmartSieve is unmaintained, so I would not recommend using it
> anymore.
>
> Regards,
>
> Stephan.
>
>

Re: [Dovecot] SSL with startssl.com certificates

[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: Warning: SSL failed: 
where=0x2002: SSLv3 read client certificate A [98.111.147.220]
Oct  6 20:20:25 imaps dovecot: imap-login: Disconnected (no auth 
attempts in 1 secs): user=<>, rip=98.111.147.220, lip=199.233.228.197, 
TLS handshaking: Disconnected, session=
Yet, the same iPhone and Macbook connect fine to a dovecot 1.2.17 
installation.  That's my current IMAP server.  I'm moving to another 
server and failing so far.


Suggestions to use another client app or platform will not be 
entertained, because, clearly, this works with dovecot 1


and mail.app is working even with *self signed* certificates and 
dovecot 2.2

you only have to accept / import the certificate
proven by a testserver all day long

so i assume the problem exists between chair and keyboard


It is something I am doing.  Without a doubt.

Clearly, there is something unique about this situation which is not 
going well.  I want to discover the problem so others do not encounter

it in future.

--
Dan Langille - http://langille.org/

Re: [Dovecot] Replication: long detalys

[Oli Schacher]

On Mon, 07 Oct 2013 12:35:10 +0200
Lucas Rothamel - Eye Catching Webdesign
 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.


http://wiki2.dovecot.org/Replication :
"""
NOTE: v2.2 is highly recommended for this. Earlier versions can't do
incremental metadata syncing. This means that the more mails a mailbox
has, the slower it is to sync it. 
"""

Also, Timo fixed *tons* of dsync replication bugs for 2.2. Upgrading to
the latest version will most likely make these errors go away.

Best regards
Oli

Re: [Dovecot] retr errors

[Charles Marcus]

On 2013-10-06 9:19 PM, 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?


McAfee 


Well, I'd just stop right there, fire whoever installed Macafee, remove 
it, and install a real antivirus (ESET is my preferred, but *anything* 
but Macafee or Norton)...


--

Best regards,

*/Charles/*

[Dovecot] Replication: long detalys

[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 
called srv06 and srv07:


Below is the dovecot config, both servers have identical config, only 
the replica srv0x address is different. I read to put this line into 
10-mail.conf and I did:

mail_plugins = $mail_plugins notify replication

My Problem: When E-Mail arrives on one server, it is only available on 
the other server many hours later. Same behaviour in both directions. 
This means I see different mailboxes via IMAP depending on which server 
I connect to - in theory I want the client not to be able to tell which 
server it is connected to.


dovecot -n:
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 ext4
auth_mechanisms = plain login cram-md5
disable_plaintext_auth = no
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_location = maildir:/home/%d/%n/Maildir
mail_privileged_group = mail
passdb {
  args = /etc/dovecot/dovecot-sql.conf
  driver = sql
}
plugin {
  mail_replica = remote:vm...@srv07.xxx
  quota = maildir:User quota
  quota_rule = *:storage=1GB
  replication_full_sync_interval = 1 hours
}
protocols = imap pop3
service aggregator {
  fifo_listener replication-notify-fifo {
mode = 0600
user = vmail
  }
  unix_listener replication-notify {
mode = 0600
user = vmail
  }
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
  user = root
}
service config {
  unix_listener config {
user = vmail
  }
}
service doveadm {
  user = vmail
}
service replicator {
  process_min_avail = 1
}
ssl_cert = Oct  7 05:31:45 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1522, 
file=1381075321.V902I19a2a66M626453.srv07.x:2,)
Oct  7 05:31:45 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1523, 
file=1381075381.V902I19a2bb2M737865.srv07.x:2,)
Oct  7 05:31:45 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1524, 
file=1381075441.V902I19a3185M959529.srv07.x:2,)
Oct  7 05:31:45 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1525, 
file=1381075501.V902I19a3187M989935.srv07.x:2,)
Oct  7 05:31:45 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1526, 
file=1381075561.V902I19a3188M971187.srv07.x:2,)
Oct  7 05:31:45 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1527, 
file=1381075622.V902I19a3189M60093.srv07.x:2,)
Oct  7 05:31:45 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1528, 
file=1381075682.V902I19a318aM231725.srv07.x:2,)
Oct  7 05:31:45 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1529, 
file=1381075741.V902I19a318bM353115.srv07.x:2,)
Oct  7 05:31:46 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1530, 
file=1381075801.V902I19a318cM609633.srv07.x:2,)
Oct  7 05:31:46 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1531, 
file=1381075861.V902I19a318dM392514.srv07.x:2,)
Oct  7 05:31:46 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1532, 
file=1381075921.V902I19a318eM521040.srv07.x:2,)
Oct  7 05:31:46 srv06 dovecot: dsync-local(sysop@x): Error: remote: 
dsync-remote(sysop@x): Warning: Maildir /home/x/sysop/Maildir: 
Expunged message reappeared, giving a new UID (old uid=1533, 
file=1381075981.V902I19a318fM611775.srv07.x:2,)
Oct  7 05:31:46 srv06 dovecot: dsync-local(syso

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

[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 # User running Dovecot LDA's deliver
}

# Dovecot as SASL Auth
unix_listener /var/spool/postfix/private/dovecot-auth {
mode = 0660
user = postfix
group = postfix
}
}



Looks good to me


Thanks for the help (and sorry for the late reply)! Now as soon as the
namespaces make sense to me and I figure out how to get sieve properly
configured I can do the upgrade.


hehe, no problems, I wont comment on namespaces since I don't use 
anything special in that regards, but sieve is easy to configure


service managesieve-login {
service_count = 1
process_min_avail = 0
vsz_limit = 64M
inet_listener sieve {
port = 4190
}
}

service managesieve {
process_limit = 1024
}

protocol sieve {
managesieve_max_line_length = 65536
managesieve_logout_format = bytes=%i/%o
managesieve_implementation_string = Dovecot Pigeonhole
managesieve_max_compile_errors = 5
mail_max_userip_connections = 10
}


set...
in global:
protocols = pop3 imap sieve (assuming you use both pop3 and imap)


protocol lda:
 mail_plugins = $mail_plugins sieve


and in the plugin section, something like
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_vacation_min_period = 1d
sieve_vacation_default_period = 7d

...and you're all set

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

[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] smartsieve managesieve-login failure with dovecot 2.1.7

[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 failure: SSL alert 
number

40, session=
syslog:


setup smartsieve to disable tls, then it works

edit in servers.php

Re: [Dovecot] retr errors

[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 suggest temporaily disabling McAffle (might be not posssible 
without uninstaling it, at least its the case with norton and kaspersky) 
as from my personal experience AV suits tend to break mail transfers.

AV's that i had problems with include Norton, Kaspersky, Avast ...
We are not using McAffe here but it's probable that if mail filtering or 
Firewall/Internet security/Anti phishing is enabled, McAffe is 
intercepting Your mail en route and scanning it what might lead to errors.



As I'm sure Daniel was implying, did you also test without these?
Also, do they provide webmail?  next time you get a stuck message, 
login to webmail and see if its OK there, try using only webmail for a 
week or two, if you have this trouble every day, you'll soon reproduce 
it, or rule out the ISP end.



and the ISP wasn't interested in the wireshark traces.


Baring in mind, that ISP tech support, is exactly that, "ISP, Tech 
Support" not Microsoft support, or apple support or whatever, the ISP 
can only support its services, not your local client software, if they 
can prove, and your ISP should have by process of elimination, for 
instance, webmail, you have no trouble, then they have ruled out an 
ISP related cause, and they are very within their rights to say "not 
our problem".


Also remember, engineers tend to act/get-involved when complaints are 
en-mass, its to their advantage to look at it then, IOW, the care 
factor will increase with multiple people exhibiting the same problem 
over a short  or same period of time.




I know, I should change the ISP and see if the problem goes away. :-)



Sounds like a fair idea to me if you rule out everything on your end 
and can prove beyond doubt it is the ISP, else you'll just be moving 
the problem sideways, not up towards resolution.