Hi,
are there plans to support Debian 8 (alias stable, alias jessie) in the
dovecot-ee repository? Currently there are only squeeze and wheezy
repos. The wheezy repo is uninstallable due to an unsatisfyable
dependency on libicu48.
Of course you can install libicu48 from Wheezy on a Jessie system
Bernhard Schmidt wrote:
*bump* this is still an issue with Dovecot 2.2.18.2 from the dovecot-ee
repository
> With 2.2.15 from dovecot-ee it is different. The quota is now checked at
> RCPT stage
>
> # 2.2.15.8 (912dd04d7a14+): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.
Hello,
we run a Dovecot 2.0.13 instance purely as SASL backend for Postfix,
authenticating against a local passwd-file and our central LDAP
database.
# dovecot -n
# 2.0.13: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32.36-0.5-default x86_64 SUSE Linux Enterprise Server 11
# (x86_64)
auth_mechanism
Hi,
compiling dovecot-1.1rc1 with the option --with-storages=maildir,raw
raises the following error:
cc -std=gnu99 -g -Wall -O2 -Wall -W -Wmissing-prototypes
-Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2
-Wbad-function-cast -Wstrict-aliasing=2 -o deliver auth-client.o
delive
Hi,
I'm having a really really strange problem. After upgrading from
1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect
to the services using IPv4 anymore. dovecot happily binds to the IPv6
wildcard socket which should accept IPv4 connections as well.
[EMAIL PROTECTED]:~# nets
Timo Sirainen <[EMAIL PROTECTED]> wrote:
>> I'm having a really really strange problem. After upgrading from
>> 1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect
>> to the services using IPv4 anymore. dovecot happily binds to the IPv6
>> wildcard socket which should accept IPv
Timo Sirainen wrote:
Mar 8 13:02:57 vs02 deliver((null)): User request from dovecot-auth
timed out
Oh, that's a new bug. This should fix it:
http://hg.dovecot.org/dovecot-1.1/rev/631fd6f25e41
Works, thanks a lot.
Regards,
Bernhard
Hello everyone,
I've been asked by a colleague to have a look at some extremely weird
dovecot SSL issue they are seeing on one of the student mailservers.
They are running dovecot 1.1.6 (yes, I know, a bit old ...) on SLES 10.2
x86_64 with imap(+starttls), imaps, pop3(+starttls) and pop3s enabled
Hello,
two days ago I've upgraded to 1.2rc2 and the new sieve implementation
(version 0.1.4). Today I got the first mail that got stuck in the
postfix queue because deliver was dying with a segfault.
The mail is spam, thus I don't have any issues sharing it:
http://users.birkenwald.de/~berni/temp
Hi,
we've found a weird bug (?) in Dovecot 1.1.11.
Since day and age we've been running dovecot for our student mailserver,
getting the location of the mailbox from a LDAP directory. We allow
login and LDA with both full mail address and an internal username,
so the mailbox directory is based on
Charles Marcus wrote:
>> we've found a weird bug (?) in Dovecot 1.1.11.
> dovecot -n output is usually desired when asking for help, especially
> when it is a likely config issue...
I don't think it's a config issue, but here we go:
lxmhs23: # dovecot -n
# 1.1.11: /mnt/mail2/
On Wed, Apr 08, 2009 at 12:41:17PM -0400, Timo Sirainen wrote:
> > So, it looks like there is an issue using the same LDAP attribute
> > (xxxMailbox in this case) twice in variable expansion.
> > Is this a known issue?
> Yes. I was planning on rewriting LDAP configuration and getting it fixed
> a
Daniel L. Miller wrote:
> I'll admit I don't understand what you're trying to do with the above
> parameters, but let me share what I'm using and see if it helps. I
> happen to be using a pure virtual configuration, with my mail users
> logging in using their full email address as a username.
Thomas Leuxner wrote:
> Narrowing down the issue a bit. With the code that was present on Nov
> 22, those Newsletter mails worked (needless to say config wasn't
> changed):
Same here, but I can limit the window some more. 8adacd9c03b2 from Nov
18th was fine and it was busted with 0bc3751c6657 on
Leo Baltus wrote:
Hello Leo,
> We want dovecot to listen on a specific ip4 & ipv6 addresses like so:
>
> listen = 145.58.1.1, [2a02:458:1::1]
>
> But on startup it tells me:
>
> Fatal: service(managesieve-login) Can't resolve address [2a02:458:1::1]: Name
> or service not known
Try without the
Hi,
I run Dovecot 2.0.13 fed by Postfix over LMTP. Today it rejected one
mail Postfix and Amavis accepted, generating a bounce. It was just a
spammail, but I think the sender address is legal according to RFC5321
and should be accepted. I don't like generating bounces, email should be
either rejec
Hi,
we recently hit an issue where one (of the three configured) LDAP
servers dropped an index on an attribute due to a misconfiguration,
which caused all/most queries for passdb to take a very long time
(several 10s of seconds).
The other servers would have been fine, but it seems like Dovecot
Hi,
Fallbacking to another LDAP server is done by OpenLDAP internally. So
what would be needed is either a) OpenLDAP to itself figure out that
queries are running too slowly and see if another server is faster, or
b) Dovecot figure that out itself and force OpenLDAP to switch to
another server.
Hello,
we run Dovecot 2.1.7 as SASL backend for our Postfix SMTP-AUTH farm and
see this error message occasionally
Oct 22 16:15:32 lxmhs52 dovecot: auth: PLAIN(?,xx.xx.xx.xx): Request
0.21 timeouted after 150 secs, state=2
Since it is mostly the same IP repeating I'm assuming it's a client
issue
Hello,
I've been asked to have a look at a misbehaving mail server of some
colleagues today where almost all logins where failing or excessively
delayed, while the LDAP database itself was pretty fast.
They run Dovecot 1.2.11 (yes, I know, stoneage) against an LDAP server
run by a 3rd party, auth
Hi,
I'm not sure whether the client or the server is at fault (probably the
client), but it's clearly a regression for me.
I'm using the LCG Profimail (http://lonelycatgames.com/?app=profimail)
application for my Symbian smartphone which has quite decent IMAP
capabilities. Amongst others it can
Hi,
Do you think there's any chance of getting Profimail fixed by
reporting this as a bug for them? Other new servers besides Dovecot
behave in a similar way.
I'll try. They are pretty active in development, but god knows how they
handle support queries. I've raised the issue with their suppor
Timo Sirainen wrote:
> On Sun, 2010-02-28 at 16:09 +0100, Thomas Leuxner wrote:
>> Feb 28 16:07:00 spectre dovecot: master: service(lmtp): child 17322 kille=
> d with signal 11 (core dumps disabled)
> Could you get gdb backtrace? http://dovecot.org/bugreport.html
For the record, I see those too.
Bernhard Schmidt wrote:
> And managesieve segfaults immediately at TCP connect, but I have not
> managed to get a backtrace yet (it always says "core not dumped"
> regardless of ulimit -c setting. I also added -D to the executable, but
> no core file yet)
>
> Feb 28 1
On 28.02.2010 20:24, Timo Sirainen wrote:
On Sun, 2010-02-28 at 18:34 +, Bernhard Schmidt wrote:
And managesieve segfaults immediately at TCP connect, but I have not
managed to get a backtrace yet (it always says "core not dumped"
regardless of ulimit -c setting. I also added
Bernhard Schmidt wrote:
>> On Sun, 2010-02-28 at 16:09 +0100, Thomas Leuxner wrote:
>>> Feb 28 16:07:00 spectre dovecot: master: service(lmtp): child 17322 kille=
>> d with signal 11 (core dumps disabled)
>> Could you get gdb backtrace? http://dovecot.org/bugreport.htm
Ed W wrote:
> Suggest drop them a line in the first instance? (You could check that
> the COMPRESS stuff made it into the released build also since Timo
> kindly added support for that to 2.0)
Lonelycat Games has sent me a fixed build and promised to have it
incorporated into the next version.
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 z
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 (
Hi,
apparently the following change in dovecot hg
* New revision (10876:370ee9717a6c) in dovecot Mercurial repository:
- config: Forgot to add header file.
broke
listen = 83.170.6.69, 2001:1b10:1000::110:1:1
mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf
doveconf: Warn
Thomas Leuxner wrote:
>> 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..
> Just tested and does not appear to be fixed by changeset 10875
>
On 09.03.2010 18:42, Timo Sirainen wrote:
On 9.3.2010, at 14.47, Bernhard Schmidt wrote:
* New revision (10876:370ee9717a6c) in dovecot Mercurial repository:
- config: Forgot to add header file.
mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf
doveconf: Warning: Obsolete
Hi,
another LMTP problem. When a sieve userscript tries to fileinto a
nonexisting mailbox the LMTP process hangs.
Mar 12 12:55:28 mail dovecot: lmtp(1328, be...@vmail.mail.mucip.net):
kPpuOKArmkswBQAA/GZUZg: sieve:
msgid=<201003111751.o2bhptbx069...@squid-cache.org>: failed to store
into mailbox
Timo Sirainen wrote:
>> mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf
>> doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:29:
>> listen=..:port has been replaced by service { inet_listener { port } }
>> doveconf: Fatal: Error in configuration file /etc/dovecot/d
Timo Sirainen wrote:
Hi Timo,
>> another LMTP problem. When a sieve userscript tries to fileinto a
>> nonexisting mailbox the LMTP process hangs.
>> I'm on 10869:bf978f2de0fd.
> It was fixed by the next changeset:
> http://hg.dovecot.org/dovecot-2.0/rev/6d260794f278
Ah right, did not use that b
Timo Sirainen wrote:
> On Wed, 2010-03-10 at 18:01 +0100, Bernhard Schmidt wrote:
>> mail.svr02.mucip.net:~# dovecot -F -c /etc/dovecot/dovecot.conf
>> doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:29:=20
>> listen=3D..:port has been replaced by service {
Hoi,
somewhere between Hg revisions 10945 and 10962 filing into a subfolder
using sieve Scripts (like fileinto "fwd.sixxs" here) broke
Mar 20 18:14:24 mail dovecot: lmtp(27326, be...@vmail.mail.mucip.net):
ojJwL3ACpUu+agAA/GZUZg:
msgid=: save failed to
fwd.sixxs: Mailbox doesn't exist: fwd.sixxs
Bernhard Schmidt wrote:
> somewhere between Hg revisions 10945 and 10962 filing into a subfolder
> using sieve Scripts (like fileinto "fwd.sixxs" here) broke
Disregard, stupid me broke his lmtp.conf on upgrade.
Bernhard
Thomas Leuxner wrote:
>> somewhere between Hg revisions 10945 and 10962 filing into a subfolder
>> using sieve Scripts (like fileinto "fwd.sixxs" here) broke
> Hmmm. Works for me with 10962 but there's quite a bunch of changes =
> inbetween...
I'm a bit confused as well. I accidentally dropped
Hi,
since a couple of weeks I occasionally have an imapd going crazy on me,
using up 100% CPU. Current revision is 10962
29865 vmail 20 0 47820 3296 1708 R 99.7 0.9 131:07.85 imap
vmail29865 86.1 0.8 47820 3296 ?RMar20 131:20
dovecot/imap [berni 2001:a60:f001:1:219:66ff
On 21.03.2010 15:17, Timo Sirainen wrote:
Hi,
strace -p shows a repeating pattern of
epoll_wait(8, {{EPOLLOUT, {u32=36560672, u64=36560672}}}, 5, 4872) = 1
gettimeofday({1269133967, 495298}, NULL) = 0
gettimeofday({1269133967, 495333}, NULL) = 0
gettimeofday({1269133967, 495370}, NULL) = 0
On 21.03.2010 15:17, Timo Sirainen wrote:
Hi Timo,
It would be helpful to find out what the I/O function is that is being
called. For example:
b ioloop-epoll.c:208
p *io
cont
p *io
cont
..etc..
What is the *io output? If it's client_output() or something else as
generic.. Use "step" to get in
Hi,
I just wanted to test the zlib plugin in Dovecot 2.0 and have a problem.
Delivery via LMTP works fine and the mail is saved compressed.
-rw--- 1 vmail vmail 1012 13. Jun 12:51
1276426292.M93539P15363.mail.svr02.mucip.net,S=2799,W=2850:2,
# file 1276426292.M93539P15363.mail.svr02.mucip.net
Hi,
a few days ago I started to get some complaints about authentication
delays from Thunderbird POP3 users. After some debugging it turned out
that the problem was introduced somewhere between 1.2rc3 and 1.2rc7
(1.2.0 is still affected).
A session with Thunderbird 2.0.0.22 against 1.2rc3 looks l
Bernhard Schmidt wrote:
> a few days ago I started to get some complaints about authentication
> delays from Thunderbird POP3 users. After some debugging it turned out
> that the problem was introduced somewhere between 1.2rc3 and 1.2rc7
> (1.2.0 is still affected).
Reverting
Pascal Volk wrote:
> * Added LSB-compliant info block (for insserv and friends)
[...]
> +# Required-Start:$local_fs $syslog
> +# Required-Stop: $local_fs $syslog
> +# Should-Start: $time
I think this should be $remote_fs, as according to
http://refspecs.freestandards.org/LSB
Debian Wheezy amd64 plus Stefan's stable-auto/dovecot2.2 repository
2:2.2.2-0~auto+57 = 16495:d447dcc6b611
Crash goes away when I disable mail_attachment_dir, happens with a
fresh home as well
# 2.2.2 (d447dcc6b611): /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.0
disable_p
Bernhard Schmidt wrote:
> Debian Wheezy amd64 plus Stefan's stable-auto/dovecot2.2 repository
> 2:2.2.2-0~auto+57 = 16495:d447dcc6b611
>
> Crash goes away when I disable mail_attachment_dir, happens with a
> fresh home as well
Log:
Jun 12 21:46:23 lxmhs69 doveco
Am 13.06.2013 03:56, schrieb Timo Sirainen:
On Wed, 2013-06-12 at 19:51 +, Bernhard Schmidt wrote:
Debian Wheezy amd64 plus Stefan's stable-auto/dovecot2.2 repository
2:2.2.2-0~auto+57 = 16495:d447dcc6b611
Crash goes away when I disable mail_attachment_dir, happens with a
fresh ho
Hi,
Dovecot 2.2.9 (Debian package from backports) does not seem to respect
lmtp_rcpt_check_quota
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4
deliver_log_format = from=<%e>, size=%p, message-id=<%m>, status=%$
disable_plaintext_auth = no
lmtp_rcpt_check_quota =
Axel Luttgens wrote:
Hi Axel,
> Le 11 févr. 2014 à 08:34, Bernhard Schmidt a écrit :
>
>> [...]
>> so Dovecot should reject in RCPT TO phase, but according to the logs of the
>> upstream Postfix it does so after END-OF-DATA
>>
>> (host xxx[2001:xxx] said: 4
Bernhard Schmidt wrote:
Hi Timo,
in case you missed that...
> Hi,
>
> Dovecot 2.2.9 (Debian package from backports) does not seem to respect
> lmtp_rcpt_check_quota
>
> # 2.2.9: /etc/dovecot/dovecot.conf
> # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4
> deliver_log_for
Hi,
we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand mailboxes.
We have two users that repeatedly trigger an OOM condition with IMAP.
Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Fatal:
pool_system_realloc(268435456): Out of memory
Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Error:
On 23.06.2014 16:38, Steffen Kaiser wrote:
On Mon, 23 Jun 2014, Bernhard Schmidt wrote:
we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand mailboxes.
We have two users that repeatedly trigger an OOM condition with IMAP.
Do those users have mailboxes extra ordinary large or is one
Hi Timo,
thanks for your answer.
we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand
mailboxes. We have two users that repeatedly trigger an OOM
condition with IMAP.
Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Fatal:
pool_system_realloc(268435456): Out of memory
..
#6 0x7f117
Bernhard Schmidt wrote:
Hi,
> Axel Luttgens wrote:
>
> Hi Axel,
>
>> Le 11 févr. 2014 à 08:34, Bernhard Schmidt a écrit :
>>
>>> [...]
>>> so Dovecot should reject in RCPT TO phase, but according to the logs of the
>>> upstream Postfix it do
Hi,
the dovecot-sieve plugin from the hg repository
(http://hg.dovecot.org/dovecot-sieve-1.0/) does not build against
current dovecot-1.0 repository.
/bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2
-Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith
-Wchar-su
Timo Sirainen schrieb:
Hi,
the dovecot-sieve plugin from the hg repository
(http://hg.dovecot.org/dovecot-sieve-1.0/) does not build against
current dovecot-1.0 repository.
..
/.libs/libsieve.a(script.o): In function `sieve_script_parse':
/usr/src/dovecot-sieve-1.0/src/libsieve/script.c:140:
Timo Sirainen <[EMAIL PROTECTED]> wrote:
> Unless someone finds something broken, I'll release v1.0.2 in a few
> days. The most important changes since v1.0.1:
I'm getting a _large_ number of UIDVALIDITY changes logging messages,
even when I have completely removed all old index files
Jul 13 00:
Timo Sirainen wrote:
Hi Timo,
Unless someone finds something broken, I'll release v1.0.2 in a few
days. The most important changes since v1.0.1:
I'm getting a _large_ number of UIDVALIDITY changes logging messages,
even when I have completely removed all old index files
rc2 should have fixed
Bernhard Schmidt <[EMAIL PROTECTED]> wrote:
> I've upgraded to dovecot 1.1beta2 and the latest dovecot-sieve release
> yesterday and have one single mail that cannot be delivered repeatedly.
Screw that, fixed already in the latest hg version, probably with
changeset 58d9
f66d96] ->
/usr/local/libexec/dovecot/deliver(main+0xe74) [0x417d24] ->
/lib/libc.so.6(__libc_start_main+0xf4) [0x2b662da15b44] ->
/usr/local/libexec/dovecot/deliver [0x416079]
All other mails work fine, so there is probably something corner case
here.
Timo, I'll send you the mail in private.
Regards,
Bernhard Schmidt
Hi,
since upgrading from 1.0.5 to latest 1.1-hg I get an incomplete subject
line for mails autogenerated by one of our systems in the message list
(Thunderbird and mutt). When I open the mail the subject line is intact.
It appears that the system is using multiline subjects. Example
Subject: =?I
Hi,
> > since upgrading from 1.0.5 to latest 1.1-hg I get an incomplete subject
> > line for mails autogenerated by one of our systems in the message list
> > (Thunderbird and mutt). When I open the mail the subject line is intact.
> >
> > It appears that the system is using multiline subjects. Ex
Hi,
> > Reply-To: Doku-Ticket System <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED],
> > [EMAIL PROTECTED]
> > Subject: =?ISO-8859-1?B?SG9zdG1hc3RlcjogMDAwMDAxMDE5OiBOYW1lc2U=?=
> > =?ISO-8859-1?B?cnZlcjogTmV1dmVyZ2FiZSBvZGVyIMRuZGVydW5n?=
>
> ..
>
> > To: [EMAIL PROTECTED],
> > Subject: =?ISO-88
Hi,
I've upgraded a mailstore from Debian Jessie (aka oldstable) with
Dovecot 2.2.13 to Debian Buster (next stable) with Dovecot 2.3.4.1
today. It worked pretty well, except that we're seeing error messages
very similar to this old thread
https://dovecot.org/pipermail/dovecot/2015-July/101396.htm
66 matches
Mail list logo
