[Dovecot] force to recalculate quotadict

[Andre Hübner]

Hello,

i use working quotasystem with sql-quotadict.
The values stored in db are used to realize also a quotasystem in postfix to 
reject mails if they are bigger then remaining quota.
if dataset in quotadict is missing for some reasons, postfix can't calculate 
quota and mail gets delivered even if user is already over quota.
I am looking for a way to force dovecot/lda to recalculate users 
bytes/messages with command xy and not to wait for incomming mail.


Currently i use:
deliver -d $user -n -m folderwithunspeakablenamesonobodyusesthis
and send a small message which gets lost but starts the calculation.
This works but seems not to be the finest way.
Is there a better way or my current procedure acceptable?

Thanks,
Andre 

Re: [Dovecot] force to recalculate quotadict

[Steffen Kaiser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, 8 Mar 2010, Andre Hübner wrote:

http://www.dovecot.org/list/dovecot/2009-March/038249.html

"Quota is updated whenever Dovecot is the one doing changes and quota
plugin is loaded."

Hmm, I would expect a quota recalculation, too, if there is no current 
quota at all.


In the parents of the mail, there is the outline:

1. remove the quota in the DB,
2. make same changes.

With "| dovecot --exec-mail imap" you can do changes or request the 
current quota easily.


However, you probably need to set some environment variables or su to the 
user for "dovecot" running as the correct system user and mail user.


Regards,

- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBS5TJN7+Vh58GPL/cAQK1+Af/ckGKX+5KqVXkYIg4ZmLd2qvt9JkYjEvq
gn1H9tyDi3P9wcC1rI+oioi7j79OMvFqDzLSTR7RZAOi/gVR/upOLzvSU6x+cCGU
jit8IDlUYUql0tsgpx3XqYI6c/bugMwNX69feuvuh8gg3grtBs/NefshEv51p8u8
IOvt2D0RG5s+qPSCm+DNe+P2LEOfjfhAJt3xtUzkB7+TgWQIZGrHUIhRpu3MIhR0
FDuOQXy2qLl0Ze5agjAkCduYjzJ4GA4aSnmwDU0xk8bfJKkWUaT48M9MzDo9NJU3
wN7orKhNTA+n5ZJ/I4L7ae9GwJlh1BdyAc2BPgvj/8ot4m1OJtZ5rQ==
=H9SS
-END PGP SIGNATURE-

Re: [Dovecot] force to recalculate quotadict

[Andre Hübner]

Hello,


1. remove the quota in the DB,
2. make same changes.


hmm, i see. but unfortunately this is not a way  i can do. it would be 
acceptable in private scope but not for bussinesscustomers.
to make a change i would manipulate customers maildata which is not allowed 
this way.
a simple command to update complete quota for the single user would be the 
best way.
now i tried to connect per telnet and use command Getquotaroot, seems also 
to work. this should be scriptable...


ok thanks, i will try something...
Andre

Re: [Dovecot] force to recalculate quotadict

[Pascal Volk]

On 03/08/2010 11:45 AM Andre Hübner wrote:
> Hello,
> 
>> 1. remove the quota in the DB,
>> 2. make same changes.
> 
> hmm, i see. but unfortunately this is not a way  i can do. it would be 
> acceptable in private scope but not for bussinesscustomers.
> to make a change i would manipulate customers maildata which is not allowed 
> this way.
> a simple command to update complete quota for the single user would be the 
> best way.
> now i tried to connect per telnet and use command Getquotaroot, seems also 
> to work. this should be scriptable...
> 
> ok thanks, i will try something...

You found 'something'? If not, have a look at:
http://wiki.dovecot.org/Quota/Dict#Insert_used_quotas_to_the_new_table_after_upgrade_to_1.2.x


Regards,
Pascal
-- 
The trapper recommends today: beeffeed.1006...@localdomain.org

Re: [Dovecot] force to recalculate quotadict

[Steffen Kaiser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, 8 Mar 2010, Pascal Volk wrote:


You found 'something'? If not, have a look at:
http://wiki.dovecot.org/Quota/Dict#Insert_used_quotas_to_the_new_table_after_upgrade_to_1.2.x


Oh, cool, so Dovecot does calculate the quota, if there is none in the 
database:


1) delete the quota of user $M
2) call

echo "x GETQUOTAROOT Inbox" | \
USER=$M /usr/sbin/dovecot --exec-mail imap

should do it.

Maybe, one needs to add

HOME=
MAIL=
sudo -u mail_user

Regards,

- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBS5Tbtr+Vh58GPL/cAQLFNAf/esUR5u0Fxe0+pZz2+jyyOME6RU3FuZu2
R7w+8SbgpDUimLUu6/z4RXhhO8058/RA+LsPHJvkyEs7pmpGY9JfVJ9Q/pGpTOrW
SzJRcVOUDGwIqUwd9H/mVWW5Nlsp1/hCogwiBhtD/US1GLTka2DRk3G+J2FU7V0b
trvoZgPfCSwOYHGAWMMC3J98QCborDrkz55LdcRf8LkTZd4PzlSIRNft0Gqh8AN5
9TRN6urInKd6Ik/Cj9fvoh5mdoug/usalSn0b4VtSYFJocBwp3leD9GBIMFfHg8U
BwOoWFHoNXlappOqRkhNYWDixWDbjpLn4m5QwDIeSC0byFA3edzpRw==
=qx4c
-END PGP SIGNATURE-

[Dovecot] Dovecot Proxy - auth on proxy

[BaQs]

Good afternoon list, 

I'm really struggling making this feature work:


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

Re: [Dovecot] force to recalculate quotadict

[Timo Sirainen]

BTW. v2.0 can now do:

doveadm quota username recalc



signature.asc
Description: This is a digitally signed message part

[Dovecot] Using MySQL For Mailboxes?

[Carlos Mennens]

I have always seen some people indicate they use MySQL for mailboxes
in Postfix and I wondered how difficult something like this would be?
I have 300 users on my company Postfix server right now. I am just
using Postfix, Dovecot (IMAP4 only), & Roundcube (Webmail). I have
MySQL loaded on the machine that runs Postfix but only to manage the
database for Roundcube. Do you think that 300+ users is recommended
for a MySQL database for mailboxes?

Secondly, how difficult is it to configure this? Right now everyone
user has a home directory and a mailbox in their private home folder.
Is it hard to configure Postfix & Dovecot to use MySQL mailboxes? Just
looking for some suggestions since I couldn't find a log of info via
Google.

*PS* I was told that Dovecot doesn't support MySQL mailboxes. I think
it does. Am I wrong?

http://howtoforge.com/forums/showthread.php?p=221396#post221396

Re: [Dovecot] Using MySQL For Mailboxes?

[Timo Sirainen]

On Mon, 2010-03-08 at 10:52 -0500, Carlos Mennens wrote:

> *PS* I was told that Dovecot doesn't support MySQL mailboxes. I think
> it does. Am I wrong?

Dovecot supports looking up user information from MySQL, but not
actually storing mails there. If you really wanted to store mails on
MySQL, you'd have to use dbmail instead of Dovecot.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Using MySQL For Mailboxes?

[Carlos Mennens]

On Mon, Mar 8, 2010 at 10:55 AM, Timo Sirainen  wrote:
> Dovecot supports looking up user information from MySQL, but not
> actually storing mails there. If you really wanted to store mails on
> MySQL, you'd have to use dbmail instead of Dovecot.

Is it even worth it with less than 500 users? I mean I don't have any
problems right now creating individual users and their home
directories in Linux but I have never used MySQL for mail so can't
differentiate the two. I guess I don't even know if this worth the
effort to change my configuration especially if it involves changing
out my IMAP server for 'dbmail' which I know nothing about until you
mentioned it.

Re: [Dovecot] Using MySQL For Mailboxes?

[Charles Marcus]

On 2010-03-08 10:52 AM, Carlos Mennens wrote:
> *PS* I was told that Dovecot doesn't support MySQL mailboxes. I
> think it does. Am I wrong?

You're confusing 'mailboxes' with user mail 'settings' and/or user
management.

Dovecot does not currently support storing users mail in any sql
database, although 2.0 is supposedly going to make it easier to
implement this with a plugin for anyone wants to write the code.

What you are reading about re: dovecot+mysql is simply using MySQL as
the backend for your user info. It can be as simple as username and
password, or you can add quota management, and even more (custom user
storage locations, etc) with extra_fields:

http://wiki.dovecot.org/UserDatabase/ExtraFields

Dovecot is extremely flexible with respect to configuration management.

-- 

Best regards,

Charles

Re: [Dovecot] Using MySQL For Mailboxes?

[Timo Sirainen]

On Mon, 2010-03-08 at 11:00 -0500, Carlos Mennens wrote:
> On Mon, Mar 8, 2010 at 10:55 AM, Timo Sirainen  wrote:
> > Dovecot supports looking up user information from MySQL, but not
> > actually storing mails there. If you really wanted to store mails on
> > MySQL, you'd have to use dbmail instead of Dovecot.
> 
> Is it even worth it with less than 500 users?

Why do you think it would be worth it for any amount of users?
Performance would definitely become worse. The only good reason I can
think of would be if you wanted easy SQL access to all the mails for
data mining/statistics/whatever purposes.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Using MySQL For Mailboxes?

[Bradley Giesbrecht]

On Mar 8, 2010, at 8:00 AM, Carlos Mennens wrote:


On Mon, Mar 8, 2010 at 10:55 AM, Timo Sirainen  wrote:

Dovecot supports looking up user information from MySQL, but not
actually storing mails there. If you really wanted to store mails on
MySQL, you'd have to use dbmail instead of Dovecot.


Is it even worth it with less than 500 users? I mean I don't have any
problems right now creating individual users and their home
directories in Linux but I have never used MySQL for mail so can't
differentiate the two. I guess I don't even know if this worth the
effort to change my configuration especially if it involves changing
out my IMAP server for 'dbmail' which I know nothing about until you
mentioned it.



No one will be able to answer what something is worth to you.

If your 500 users are mostly email only then you will probably enjoy  
storing email addresses, passwords, paths to mailboxes, quotes etc...  
in mysql.


This is how you can use mysql with dovecot. The emails will still be  
stored on a file system in one of the popular mailbox formats like  
mbox, maildir, etc


// Brad

Re: [Dovecot] Using MySQL For Mailboxes?

[Egbert Jan van den Bussche]

> -Oorspronkelijk bericht-
> Van: dovecot-bounces+egbert=vandenbussche...@dovecot.org 
> [mailto:dovecot-bounces+egbert=vandenbussche...@dovecot.org] 
> Namens Bradley Giesbrecht
> Verzonden: maandag 8 maart 2010 17:06
> Aan: Carlos Mennens
> CC: Dovecot Mailing List
> Onderwerp: Re: [Dovecot] Using MySQL For Mailboxes?
> 
> 
> 
> On Mar 8, 2010, at 8:00 AM, Carlos Mennens wrote:
> 
> > On Mon, Mar 8, 2010 at 10:55 AM, Timo Sirainen  wrote:
> >> Dovecot supports looking up user information from MySQL, but not 
> >> actually storing mails there. If you really wanted to 
> store mails on 
> >> MySQL, you'd have to use dbmail instead of Dovecot.
> >
> > Is it even worth it with less than 500 users? I mean I 
> don't have any 
> > problems right now creating individual users and their home 
> > directories in Linux but I have never used MySQL for mail so can't 
> > differentiate the two. I guess I don't even know if this worth the 
> > effort to change my configuration especially if it involves 
> changing 
> > out my IMAP server for 'dbmail' which I know nothing about 
> until you 
> > mentioned it.
> 
> 
> No one will be able to answer what something is worth to you.
> 
> If your 500 users are mostly email only then you will probably enjoy  
> storing email addresses, passwords, paths to mailboxes, 
> quotes etc...  
> in mysql.
> 
> This is how you can use mysql with dovecot. The emails will still be  
> stored on a file system in one of the popular mailbox formats like  
> mbox, maildir, etc
> 
> // Brad

You might have a look at PostfixAdmin. 

Egbert 


> 

[Dovecot] v1.2.11 released

[Timo Sirainen]

http://dovecot.org/releases/1.2/dovecot-1.2.11.tar.gz
http://dovecot.org/releases/1.2/dovecot-1.2.11.tar.gz.sig

mbox users really should upgrade, because by sending a message with a
huge header you could basically cause a DoS (this problem exists only
with v1.2.x, not with v1.0 or v1.1).

- mbox: Message header reading was unnecessarily slow. Fetching a
  huge header could have resulted in Dovecot eating a lot of CPU.
  Also searching messages was much slower than necessary.
- mbox, dbox, cydir: Mail root directory was created with 0770
  permissions, instead of 0700.
- maildir: Reading uidlist could have ended up in an infinite loop.
- IMAP IDLE: v1.2.7+ caused extra load by checking changes every
  0.5 seconds after a change had occurred in mailbox



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Pigeonhole Sieve date extension

[Edgar Fuß]

> What's going on? It's probably some totally stupid typo on my side.
Any comments on this? Anyone with a working date extension?

[Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery

[Thomas Leuxner]

Hi,

unsure how to provide more useful information, as I can not get LMTP to create 
a core dump. With the latest changes from Mercurial it dies upon message 
delivery:

==> /var/log/dovecot.log <==
Mar  8 20:03:33 spectre dovecot: lmtp(11690): Connect from local
Mar  8 20:03:33 spectre dovecot: lmtp(11690): Connect from local
Mar  8 20:03:33 spectre dovecot: lmtp(11690): Connect from local
Mar  8 20:03:33 spectre dovecot: master: service(lmtp): child 11690 killed with 
signal 11 (core not dumped)
Mar  8 20:03:33 spectre dovecot: master: service(lmtp): command startup failed, 
throttling

Thomas

Re: [Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery

[Thomas Leuxner]

Simple LMTP handshake crashes it:

[20:19] root spectre:/usr/lib/dovecot# ./lmtp
220 spectre.leuxner.net Dovecot LMTP ready
Info: Connect from local
lhlo leuxner.net
250-spectre.leuxner.net
250-8BITMIME
250-ENHANCEDSTATUSCODES
250 PIPELINING
mail from:
250 2.1.0 OK
rcpt to:
250 2.1.5 OK
data
354 OK
test
.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f08f26006e0 (LWP 11784)]
0x7f08f1ee1630 in message_parse_header_next () from 
/usr/lib/dovecot/libdovecot.so.0
(gdb) bt full
#0  0x7f08f1ee1630 in message_parse_header_next () from 
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#1  0x7f08f1ee2fb3 in ?? () from /usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#2  0x7f08f1ee2659 in message_parser_parse_next_block () from 
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#3  0x7f08f1ee286b in message_parser_parse_header () from 
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#4  0x7f08f2193c40 in index_mail_parse_headers () from 
/usr/lib/dovecot/libdovecot-storage.so.0
No symbol table info available.
#5  0x7f08f2193f77 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0
No symbol table info available.
#6  0x7f08f21942df in index_mail_get_first_header () from 
/usr/lib/dovecot/libdovecot-storage.so.0
No symbol table info available.
#7  0x7f08f0f21846 in ?? () from 
/usr/lib/dovecot/modules/lib90_sieve_plugin.so
No symbol table info available.
#8  0x0040a663 in mail_deliver ()
No symbol table info available.
#9  0x00406a53 in ?? ()
No symbol table info available.
#10 0x00406fc8 in ?? ()
No symbol table info available.
#11 0x7f08f1efc00b in io_loop_handler_run () from 
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#12 0x7f08f1efb188 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#13 0x7f08f1eeb193 in master_service_run () from 
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#14 0x00405be3 in main ()
No symbol table info available.

Re: [Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery

[Bernhard Schmidt]

Thomas Leuxner  wrote:

> Simple LMTP handshake crashes it:

Same here. I'm pretty sure it has been introduced with one of these two
changes:

dovecot (2:2.0.beta3-0~auto+24) unstable; urgency=low

  * New revision (10855:681e1c702899) in dovecot Mercurial repository:
- zlib: Several fixes to zlib/bzlib istreams.
- Simplified up istream-limit implementation.

 -- Stephan Bosch   Mon, 08 Mar 2010 15:13:34
+0200

(+23 worked fine, crashes since installing +24).

Unfortunately Stephan has already deleted the +23 .debs from his server
so I can't verify with the old version.

Bernhard

Re: [Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery

[Bernhard Schmidt]

Bernhard Schmidt  wrote:

>> Simple LMTP handshake crashes it:
> Same here. I'm pretty sure it has been introduced with one of these two
> changes:

Affects dovecot-lda as well:

mail.svr02.mucip.net:/var/run/dovecot# sudo -u vmail gdb
/usr/lib/dovecot/dovecot-lda 
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/lib/dovecot/dovecot-lda...Reading symbols from
/usr/lib/debug/usr/lib/dovecot/dovecot-lda...done.
(no debugging symbols found)...done.
(gdb) set args -d berni
(gdb) run
Starting program: /usr/lib/dovecot/dovecot-lda -d berni
[Thread debugging using libthread_db enabled]
Executing new program: /usr/bin/doveconf
[Thread debugging using libthread_db enabled]
Executing new program: /usr/lib/dovecot/dovecot-lda
[Thread debugging using libthread_db enabled]
asjk

Program received signal SIGSEGV, Segmentation fault.
0x778d21c0 in message_parse_header_next (ctx=0x6427b0,
hdr_r=)
at message-header-parser.c:196
196 message-header-parser.c: Datei oder Verzeichnis nicht gefunden.
in message-header-parser.c
(gdb) bt full
#0  0x778d21c0 in message_parse_header_next (ctx=0x6427b0,
hdr_r=)
at message-header-parser.c:196
msg = 0x64c3d9 ""
i = 23591
size = 18446744073709464054
startpos = 0
colon_pos = 520
parse_size = 18446744073709464053
ret = 
continues = 
no_newline = 
crlf_newline = 
__PRETTY_FUNCTION__ = "message_parse_header_next"
#1  0x778d3a97 in parse_next_header (ctx=0x64c588,
block_r=0x7fffcca0) at message-parser.c:480
part = 0x646f10
hdr = 
size = 
ret = 
__PRETTY_FUNCTION__ = "parse_next_header"
#2  0x778d3149 in message_parser_parse_next_block (ctx=0x64c588,
block_r=0x7fffcca0)
at message-parser.c:768
ret = 23591
eof = false
full = false
__PRETTY_FUNCTION__ = "message_parser_parse_next_block"
#3  0x778d334b in message_parser_parse_header (ctx=0x64c588,
hdr_size=0x646860, 
callback=0x77b83a90 ,
context=0x646648) at message-parser.c:807
block = {part = 0x646f10, hdr = 0x6427b0, data = 0x77b83a90
"\351\063\341\373\377ff.\017\037\204", 
  size = 0}
ret = 
__PRETTY_FUNCTION__ = "message_parser_parse_header"

I'm now on +27 (10867:c56358283605), still crashing.

Bernhard

[Dovecot] Cannot create auth-master file

[Greg Frith]

Hi all,

I'm trying to get postfix and dovecot working nicely together to process and 
store mail for both local (system) on one domain and virtual users and a few 
different domains.

I've got postfix up and running quite nicely, but am having a few problems with 
Dovecot.  Every time postfix tried to delivery a message to a virtual user 
using dovecot I get an error like the following in /var/log/mail.log:

Mar  8 21:53:58 rhy postfix/pipe[6616]: 89C94846E: to=, 
orig_to=, relay=dovecot, delay=8795, 
delays=8794/0.01/0/0.61, dsn=4.3.0, status=deferred (temporary failure)

At the same instant, in my dovecot log I'll get this error:

deliver(gr...@gregsfamily.com): 2010-03-08 21:53:58 Error: Can't connect to 
auth server at /var/run/dovecot/auth-master: Connection refused

So, I'm guessing that this is a permissions issue (somewhere) and that the 
dovecot process is not able to create the file /var/run/dovecot/auth-master.  
The permissions on this folder are as follows:

gr...@rhy:/etc/dovecot$ ls -al /var/run/dovecot/
total 0
drwxr-xr-x  3 root  root100 2010-03-08 21:44 .
drwxr-xr-x 15 root  root660 2010-03-08 22:00 ..
srw---  1 vmail root  0 2010-03-08 21:43 auth-master
srwxrwxrwx  1 root  root  0 2010-03-08 21:43 dict-server
drwxr-x---  2 root  dovecot  60 2010-03-08 21:44 login

I've searched around for hours, found several threads describing similar 
issues, but no solutions that have worked for me.  If anyone is able to give me 
any pointers or suggestions I would be most grateful.  

My dovecot configuration is:

gr...@rhy:/etc/dovecot$ sudo dovecot -n
# 1.1.11: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.28-18-generic x86_64 Ubuntu 9.04 ext3
log_timestamp: %Y-%m-%d %H:%M:%S 
protocols: imaps pop3s imap pop3
login_dir: /var/run/dovecot/login
login_executable(default): /usr/lib/dovecot/imap-login
login_executable(imap): /usr/lib/dovecot/imap-login
login_executable(pop3): /usr/lib/dovecot/pop3-login
mail_privileged_group: mail
mail_location: maildir:/home/vmail/%d/%u
mail_debug: yes
mail_executable(default): /usr/lib/dovecot/imap
mail_executable(imap): /usr/lib/dovecot/imap
mail_executable(pop3): /usr/lib/dovecot/pop3
mail_plugin_dir(default): /usr/lib/dovecot/modules/imap
mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3
auth default:
  mechanisms: plain login
  user: vmail
  debug: yes
  debug_passwords: yes
  passdb:
driver: sql
args: /etc/dovecot/dovecot-sql.conf
  userdb:
driver: static
args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes
  socket:
type: listen
client:
  path: /var/spool/postfix/private/auth
  mode: 432
  user: postfix
  group: postfix
master:
  path: /var/run/dovecot/auth-master
  mode: 384
  user: vmail


:wq
G

Re: [Dovecot] Cannot create auth-master file

[Timo Sirainen]

On Mon, 2010-03-08 at 22:06 +, Greg Frith wrote:
> gr...@rhy:/etc/dovecot$ sudo dovecot -n
> # 1.1.11: /etc/dovecot/dovecot.conf
> # OS: Linux 2.6.28-18-generic x86_64 Ubuntu 9.04 ext3

If you're using Ubuntu's dovecot-postfix package, it's actually
using /etc/dovecot/dovecot-postfix.conf, not dovecot.conf.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery

[Timo Sirainen]

On Mon, 2010-03-08 at 20:15 +, Bernhard Schmidt wrote:

> > Simple LMTP handshake crashes it:
> 
> - Simplified up istream-limit implementation.

Yeah, it's this one. I'll probably revert it soon. I did it mostly while
trying to fix istream-zlib bugs, but hopefully zlib won't break when
that change is reverted :) Started my stress test again..



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Pigeonhole Sieve date extension

[Stephan Bosch]

Edgar Fuß wrote:

What's going on? It's probably some totally stupid typo on my side.


Any comments on this? Anyone with a working date extension?
  
Most curious. That version should support the date extension as 
indicated by the binary containing the corresponding symbols. Did you 
set sieve_extensions in your configuration perhaps. Are you sure that 
you are using the correct instance of the Sieve plugin? Showing your 
dovecot -n output may help us pinpoint the error.


Regards,

Stephan.