[Dovecot] sieve_execute_bytecode failed with squirrelmail

[Gregory Charot (EVENIUM)]

Hello all,

I'm using dovecot on CentOS 5.8 (official CentOS package) and have lot 
of lock and "sieve_execute_bytecode error" in my dovecot.log.


$ cat /etc/redhat-release
CentOS release 5.8 (Final)

$ dovecot --version
1.0.13

The sieve scripts are generated by squirrelmail mail and are mostly mail 
filters and vacations notices.


$ yum info squirrelmail.noarch
Installed Packages
Name   : squirrelmail
Arch   : noarch
Version: 1.4.8
Release: 5.el5.centos.13

When I look at my dovecot.log I have a lot of sieve error :

deliver(foo): Sep 11 15:08:04 Info: 
msgid=<1881992580.96697.1347363282479.javamail.jb...@gula1.xxx.com>: 
save failed to EvSUPPORT: Timeout while wait

ing for lock
deliver(foo): Sep 11 15:08:04 Info: sieve runtime error: Fileinto: 
Generic Error
deliver(foo): Sep 11 15:08:04 Error: 
sieve_execute_bytecode(/home/foo/.dovecot.sievec) failed



The server hosts around 50 mailboxes, some people does have sieve errors 
some doesn't.


Is there any way to get more details about the runtime error ? How can I 
debug this issue ?


Thanks a lot in advance,
Greg

My config below :

#dovecot -n

# 1.0.13: /etc/dovecot.conf
log_path: /var/log/dovecot.log
ssl_ca_file: /etc/pki/roch_crt/roch_evenium_com.ca-bundle
ssl_cert_file: /etc/pki/roch_crt/roch_evenium_com.crt
ssl_key_file: /etc/pki/roch_crt/private/roch-private.key
ssl_cipher_list: 
ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+SSLv3

login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap-login
login_executable(imap): /usr/libexec/dovecot/imap-login
login_executable(pop3): /usr/libexec/dovecot/pop3-login
login_process_per_connection: no
login_process_size: 256
login_processes_count: 10
login_max_connections: 32
mail_privileged_group: mail
dotlock_use_excl: yes
fsync_disable: yes
maildir_copy_with_hardlinks: yes
mail_executable(default): /usr/libexec/dovecot/imap
mail_executable(imap): /usr/libexec/dovecot/imap
mail_executable(pop3): /usr/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/lib64/dovecot/imap
mail_plugin_dir(imap): /usr/lib64/dovecot/imap
mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls,oe-ns-eoh
auth default:
  passdb:
driver: pam
  userdb:
driver: passwd
  socket:
type: listen
client:
  path: /var/run/dovecot/auth-client
  mode: 438
  user: postfix
  group: postfix
master:
  path: /var/run/dovecot/auth-master
  mode: 384

Re: [Dovecot] best way to activate quota

[Angel L. Mateo]

El 07/09/12 12:28, Robert Schetterer escribió:


 I have tried to activate it in one of my nodes. The problem is that
load of it has increase a lot, as much as the system was unusable
(maildir is in nfs storage, with indexes in local disks).


that might not be the optimal storage solution

	Why do you say it might be not optimal? I think that nfs storage is a 
very common scenario.

[Dovecot] Couldn't drop privileges: User is missing UID (see mail_uid setting)

[Carsten Laun-De Lellis]

Hi all

 

I hope anyone could help me out with my problem regarding the user_id
settings.

 

I am running my mail servers just for fun and I am not a professional mail
admin. After I am using postfix and dovecot for my mail servers with a mysql
backend for the last 2 years I have tried to set up an installation with a
ldap backend.

I followed the how-to from the “Postfix Book” and now I have always the
following error message: 

 

Couldn't drop privileges: User is missing UID (see mail_uid setting)

 

This error message occurs whenever I try to connect via a mail client.
System emails were delivered the way I expected. So I assume postfix is
working fine. The ldap search I use for user authentication is as follows:

 

uris = ldap://myserver.com

dn = cn=admin, dc=mydomain, dc=com

dnpass = secure

tls = no

base = ou=mailuser,dc=mydomain,dc=com

ldap_version = 3

 

user_attrs = pfMailMessageStore=home

user_filter = (&(objectClass=PFMailAccount)(pfMail=%u))

 

pass_attrs = pfClearPassword=password,pfMailMessageStore=userdb_home

pass_filter = (&(objectClass=PFMailAccount)(pfMail=%u))

 

default_pass_scheme = PLAIN

 

user_global_uid = 5000

user_global_gid = 5000

 

I am using dovecot 2.1.9, postfix 2.8.5 and openldap 2.4.23

 

I would appreciate any help or tipps.

 

 

~ 

 

Mit freundlichem Gruß

 

Carsten Laun-De Lellis

Dipl.-Ing. Elektrotechnik

Certified Information Systems Auditor (CISA)

 

Hauptstrasse 13

D-67705 Trippstadt

 

Phone:   +49 (6306) 992140

Mobile:  +49 (151) 27530865

Fax: +49 (6306) 992142

email:
carsten.delel...@delellis.net

 

Re: [Dovecot] sieve_execute_bytecode failed with squirrelmail

[Stephan Bosch]

Op 9/14/2012 10:59 AM, Gregory Charot (EVENIUM) schreef:

Hello all,

I'm using dovecot on CentOS 5.8 (official CentOS package) and have lot 
of lock and "sieve_execute_bytecode error" in my dovecot.log.


$ cat /etc/redhat-release
CentOS release 5.8 (Final)

$ dovecot --version
1.0.13


Very, very, very, very old.

The sieve scripts are generated by squirrelmail mail and are mostly 
mail filters and vacations notices.


$ yum info squirrelmail.noarch
Installed Packages
Name   : squirrelmail
Arch   : noarch
Version: 1.4.8
Release: 5.el5.centos.13

When I look at my dovecot.log I have a lot of sieve error :

deliver(foo): Sep 11 15:08:04 Info: 
msgid=<1881992580.96697.1347363282479.javamail.jb...@gula1.xxx.com>: 
save failed to EvSUPPORT: Timeout while wait

ing for lock


There's the actual error. This has very little to do with Sieve itself. 
Looks like some mbox locking issue, but I don't really know. You could 
try enabling mail_debug to get more info.


deliver(foo): Sep 11 15:08:04 Info: sieve runtime error: Fileinto: 
Generic Error
deliver(foo): Sep 11 15:08:04 Error: 
sieve_execute_bytecode(/home/foo/.dovecot.sievec) failed


Yuck, I was hoping that people would finally have stopped using cmusieve.

Regards,

Stephan.

Re: [Dovecot] Possible mbox corruption

[Jost Krieger]

On Tue 11 Sep 2012 05:33:10 PM GMT, Timo Sirainen wrote:

> Any Content-Length header sent by IMAP client or via LDA input should
> always get dropped (among some other headers) and replaced with the
> correct value. So if there's a bug, I doubt it has anything to do with
> that. But if you can easily reproduce this failure it would be nice to
> get it fixed..

You're right, of course. And I cannot reproduce the problem. The user
that could reproduce it has somehow given up.
 
I'v experimented and read the source, and there is no way a "Content-Length"
could be saved by dovecot :-)

But ...

This is on a system where delivery is not (yet) via dovecot, but directly
by qmail. Two possibilities come to mind:

1. We have a locking problem that only surfaces when qmail and dovecot
   try to write at the same time to the end of the mbox. Most people
   (and clients) hardly ever do an APPEND to the INBOX.

2. Something qmail writes to the INBOX makes dovecot hiccup (like a
   wrong Content-Length header :-;).

Which would anyone think more likely?

Yours
Jost Krieger
-- 
| jost.krieger+...@ruhr-uni-bochum.de  Please help stamp out spam! |
| Postmaster, JAPH, resident answer machineat RUB Comp. Center |
| Sincere words are not sweet, sweet words are not sincere.|
|  Lao Tse, Tao Te King 81 |

Re: [Dovecot] sieve_execute_bytecode failed with squirrelmail

[Gregory Charot (EVENIUM)]

Thanks for the quick reply Stephan !

Is it possible to upgrade from 1.0.13 (which is the official CentOS 
release) to the atrpms version 2.1.1-2 available at


http://packages.atrpms.net/dist/el5/dovecot/

Do I need a migration plan ?

Thanks !
Greg

Le 14/09/2012 11:48, Stephan Bosch a écrit :

Op 9/14/2012 10:59 AM, Gregory Charot (EVENIUM) schreef:

Hello all,

I'm using dovecot on CentOS 5.8 (official CentOS package) and have 
lot of lock and "sieve_execute_bytecode error" in my dovecot.log.


$ cat /etc/redhat-release
CentOS release 5.8 (Final)

$ dovecot --version
1.0.13


Very, very, very, very old.

The sieve scripts are generated by squirrelmail mail and are mostly 
mail filters and vacations notices.


$ yum info squirrelmail.noarch
Installed Packages
Name   : squirrelmail
Arch   : noarch
Version: 1.4.8
Release: 5.el5.centos.13

When I look at my dovecot.log I have a lot of sieve error :

deliver(foo): Sep 11 15:08:04 Info: 
msgid=<1881992580.96697.1347363282479.javamail.jb...@gula1.xxx.com>: 
save failed to EvSUPPORT: Timeout while wait

ing for lock


There's the actual error. This has very little to do with Sieve 
itself. Looks like some mbox locking issue, but I don't really know. 
You could try enabling mail_debug to get more info.


deliver(foo): Sep 11 15:08:04 Info: sieve runtime error: Fileinto: 
Generic Error
deliver(foo): Sep 11 15:08:04 Error: 
sieve_execute_bytecode(/home/foo/.dovecot.sievec) failed


Yuck, I was hoping that people would finally have stopped using cmusieve.

Regards,

Stephan.

Re: [Dovecot] sieve_execute_bytecode failed with squirrelmail

[Stephan Bosch]

Op 9/14/2012 1:03 PM, Gregory Charot (EVENIUM) schreef:

Thanks for the quick reply Stephan !

Is it possible to upgrade from 1.0.13 (which is the official CentOS 
release) to the atrpms version 2.1.1-2 available at


http://packages.atrpms.net/dist/el5/dovecot/

Do I need a migration plan ?


http://wiki2.dovecot.org/Upgrading?action=show&redirect=UpgradingDovecot
http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Migration

Regards,

Stephan.

[Dovecot] POP3S PORT

[Robert JR]

 

Hello 

I am using dovecot with POP3S and IMAPS ports, 

When client
connect to POP3S port (995) , i can see in dovecot log file that the
protocol is TLSv1 

So how come the protocol is TLSv1 and not SSL ?


Does the user connect t port 995 with SSL protocol then encrypt again
inside the SSL session to make 

The TLSv1 protocol ? Or does the client
use TLSv1 Protocol immediately when connect to port 995 without 

Using
SSL protocol ? 

Please Help. 

Robert JR 
 

Re: [Dovecot] POP3S PORT

[Darac Marjal]

On Fri, Sep 14, 2012 at 01:37:31PM +0300, Robert JR wrote:
>  
> 
> Hello 
> 
> I am using dovecot with POP3S and IMAPS ports, 
> 
> When client
> connect to POP3S port (995) , i can see in dovecot log file that the
> protocol is TLSv1 
> 
> So how come the protocol is TLSv1 and not SSL ?

First of all, read http://wiki2.dovecot.org/SSL and see if that answers
your question.



signature.asc
Description: Digital signature

Re: [Dovecot] POP3S PORT

[Reindl Harald]

Am 14.09.2012 12:37, schrieb Robert JR:
>  
> 
> Hello 
> 
> I am using dovecot with POP3S and IMAPS ports, 
> 
> When client
> connect to POP3S port (995) , i can see in dovecot log file that the
> protocol is TLSv1 
> 
> So how come the protocol is TLSv1 and not SSL ?

because it is simply the same
read about what TLS is



signature.asc
Description: OpenPGP digital signature

[Dovecot] key -> object mailstore

[Damien Churchill]

Hi,

I was wondering what would be entailed in modifying dovecot 2.2 to
support storing mail in an object store. I've seen a few mails dotted
around in the ML history about supporting such a thing and seen it's
basically dependant upon some changes in lib-storage to support
writing messages without locking. Is this still the case?

Regards,
Damien

Re: [Dovecot] key -> object mailstore

[Timo Sirainen]

On 14.9.2012, at 17.46, Damien Churchill wrote:

> I was wondering what would be entailed in modifying dovecot 2.2 to
> support storing mail in an object store. I've seen a few mails dotted
> around in the ML history about supporting such a thing and seen it's
> basically dependant upon some changes in lib-storage to support
> writing messages without locking. Is this still the case?

I've a whole new design for it and I was planning on implementing it for v2.2. 
Do you want to help coding it? :) Which storage would you want to use?

The generic idea is:
 - only one server accesses one user simultaneously
 - index files are copied from object storage to local filesystem and accessed 
there, once in a while uploaded back to object storage
 - if user is accessed from two servers because of some bug/split 
brain/something, the changes are merged using dsync
 - support high latency: asynchronous reads/writes. prefetch mail bodies.

Re: [Dovecot] key -> object mailstore

[Damien Churchill]

On 14 September 2012 15:59, Timo Sirainen  wrote:
> On 14.9.2012, at 17.46, Damien Churchill wrote:
>
>> I was wondering what would be entailed in modifying dovecot 2.2 to
>> support storing mail in an object store. I've seen a few mails dotted
>> around in the ML history about supporting such a thing and seen it's
>> basically dependant upon some changes in lib-storage to support
>> writing messages without locking. Is this still the case?
>
> I've a whole new design for it and I was planning on implementing it for 
> v2.2. Do you want to help coding it? :) Which storage would you want to use?
>

That's good to hear :) I've been evaluating RADOS as an object store,
which is similar to S3. Although any distributed storage would be
great. I'd be more than happy to help code it!

> The generic idea is:
>  - only one server accesses one user simultaneously
>  - index files are copied from object storage to local filesystem and 
> accessed there, once in a while uploaded back to object storage
>  - if user is accessed from two servers because of some bug/split 
> brain/something, the changes are merged using dsync
>  - support high latency: asynchronous reads/writes. prefetch mail bodies.
>

I'm assuming that the director would be used in order to distribute
connections to the same server, so it's only within a local instance
of dovecot you'd need to be aware of what currently has a connection
open for that user?

How are you planning on handling the situation where say node X dies
and hasn't uploaded the latest index file? Would that result in
missing messages from the mailbox when accessed by another node, or is
the local index intended to be more of a write-through cache?

Re: [Dovecot] key -> object mailstore

[Jeff Gustafson]

On Fri, 2012-09-14 at 17:59 +0300, Timo Sirainen wrote:
> I've a whole new design for it and I was planning on implementing it
> for v2.2. Do you want to help coding it? :) Which storage would you
> want to use?
> 
> The generic idea is:
>  - only one server accesses one user simultaneously
>  - index files are copied from object storage to local filesystem and
> accessed there, once in a while uploaded back to object storage
>  - if user is accessed from two servers because of some bug/split
> brain/something, the changes are merged using dsync
>  - support high latency: asynchronous reads/writes. prefetch mail bodies.

With this system, would the read/write ultimately go to a normal OS
file function? If it is a file function, could this be used with a
system like glusterfs, ceph, etc? The other option would be to write it
against a object store client library and bypass the normal file
functions.

...Jeff