search for: db36

Hi, I'm testing Dovecot to migrate from my old Courier IMAP/POP server. It work fine but I have some problems to start the sieve server "pysieved" from Neale Pickett in PAM auth, I got the message: Traceback (most recent call last): File "/usr/share/pysieved/pysieved.py", line 97, in <module> main() File "/usr/share/pysieved/pysieved.py", line

Sparked from the discussion on the list, I've put my antispam plugin into git and split up the code into a frontend and possibly multiple backends. See http://git.sipsolutions.net/dovecot-antispam.git/ (URL functions as both gitweb and git URL) Andreas, I took your README file and adjusted it, I hope you don't mind. I didn't fork from your git tree because you'd already

http://dovecot.org/releases/dovecot-1.0.1.tar.gz http://dovecot.org/releases/dovecot-1.0.1.tar.gz.sig Lots of small fixes. * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked).

http://dovecot.org/releases/dovecot-1.0.1.tar.gz http://dovecot.org/releases/dovecot-1.0.1.tar.gz.sig Lots of small fixes. * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked).

I'm running 1.0.13 If I run dovecot for a while, I see a /var/run/dotvecot folder created with the following: drwxr-xr-x 3 root root 4096 2008-05-18 13:30 dotvecot drwxr-xr-x 3 root root 4096 2008-05-18 13:47 . drwxr-xr-x 18 root root 4096 2008-05-18 13:47 .. srw------- 1 root root 0 2008-05-18 13:47 auth-worker.15138 srwxrwxrwx 1 root root 0

...16-bit code (1337:01dd). In 16 bit mode. Register dump: CS:1337 SS:128f DS:16af ES:16b7 FS:0033 GS:003b IP:01dd SP:d9c4 BP:d9d6 FLAGS:0207( - 00 -RIP1C) AX:60d8 BX:7fc0 CX:1335 DX:16af SI:8dc2 DI:ffff Stack dump: 0x128f:0xd9c4: 128f 12df 0b38 0066 128f 5355 7fc0 16b7 0x128f:0xd9d4: 5355 db36 4921 1317 60d8 16af 60d8 16af 0x128f:0xd9e4: 0000 0000 0000 0000 0000 0000 0000 0000 02d5: sel=16af base=00138000 limit=0000ffff 16-bit rw- 02d6: sel=16b7 base=00140000 limit=0000ffff 16-bit rw- Backtrace: =>1 0x1337:0x01dd (0x128f:0xd9d6) 2 0x7b8a45f3 K32WOWCallback16Ex+0xc3() in kernel32 (0...

Hello, I would like to suggest a change in handling of 'Time moved backwards' problem. Right now dovecot just dies. So, the scenario: 1) Colocation server is shut down for some reason. The internal time drifts. 2) Server is started again. 3) Dovecot starts successfully. 4) In about a minute, NTP daemon feels confident about adjusting the system time. 5) Dovecot sees the changed time and

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/