Hello,
how is the future of the automatically built nightly debian packages of
dovecot? Has that project been ceased? The current auto-built version is
still 2.2.28 from April 28, though 2.2.29 (with a security patch) of
dovecot is out now for a while.
Regards
Christoph
Hello,
I am using sieve with notification of the original recipient in the case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifications, their sender address is now , instead of
, like it was before.
Is it p
Hello,
On 2017-05-14 21:29, I wrote:
I am using sieve with notification of the original recipient in the
case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifications, their sender address is now , instead
Hello,
I am using sieve with notification of the original recipient in the
case
that an email has been identified to contain a virus. After upgrading
dovecot from 2.2.21 to 2.2.29.1, I now detected that in these
notifications, their sender address is now , instead of
, like it was before.
Is i
Hello,
I just found that with my dovecot 2.2.21, when I use squirrelmail to
search for something in my mailfolders, that fails with
ERROR: Connection dropped by IMAP server.
Query: SEARCH CHARSET ISO-8859-1 ALL FROM "someone"
That happens for searches in any folder, except from INBOX. When I sea
Hello,
> On 29 Jun 2016, at 16:40, Christoph Pleger wrote:
>>
>> Hello,
>>
>> I just found that with my dovecot 2.2.21, when I use squirrelmail to
>> search for something in my mailfolders, that fails with
>>
>> ERROR: Connection dropped by IMAP se
Hello,
>>> Lucene library is throwing an error, which crashes Dovecot. Maybe Dovecot
>>> should catch the error, but it would still be broken. Try deleting the
lucene indexes and rebuilding them?
>> Deleting the indexes helped, but after they had been rebuilt, the error
occurred again.
> Could yo
Hello,
>>> Could you enable core dumps and run bt full in gdb?
>>
>> I attached the result.
>
> It crashes in:
>
> _CLTHROWA(CL_ERR_IllegalArgument, "language not available for
> stemming\n"); //todo: richer error
>
> So looks like you're trying to use an unknown language. If you have only a
> sin
Hello,
I installed dovecot 2.0.6 and pigeonhole 0.2.1 on my system, but I guess that
sieve is not working, because netstat does not show that anything is listening
to ports 2000 and 4190.
Regards
Christoph
# 2.0.6 (601065674f74): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-bpo.5-amd64 x86_6
Hello,
> > I installed dovecot 2.0.6 and pigeonhole 0.2.1 on my system, but I guess
> > that sieve is not working, because netstat does not show that anything is
> > listening to ports 2000 and 4190.
>
> You mean that the Sieve protocol (ManageSieve) is not working.
>
> > protocols = imap lmtp
>
>
Hello,
I followed the instructions on http://wiki2.dovecot.org/Plugins/Expire to
configure the expire plugin, but when I move a message to the Trash folder, I
get the following error messages in my logfile:
dovecot: dict: Error: sqlite: exec(INSERT INTO expires
(expire_stamp,username,mailbox)
Hello,
I forgot to mention the dovecot version number. It is version 2.0.7.
Regards
Christoph
Hello,
> But if it's 0666, I'm not really sure what the problem could be. You
> could try if dict can access it as root:
>
> service dict {
> user = root
> }
I have found the solution: The directory where the sqlite3 database resides
must be writable by the dovecot user.
Regards
Christoph
Hello,
I am using squirrelmail with avelsieve to edit my filter rules. The filter
rules are like this:
1. If the message contains a virus, delete the mail and notify me by email.
2. If the message is spam, deliver it to my spam folder.
3. If the message is from the dovecot mailing list, deliver
Hello,
it seems that "doveadm mailbox create" does not handle the mailbox parameters
correctly if used with the "-s"-Parameter.
I am using the following command in a script for adding new users:
doveadm mailbox create -u "${ACCOUNT}" -s INBOX Drafts Sent Trash Spam
Templates
This creates mail
Hello,
I am running dovecot 2.0.9 with expire plugin, using the sqlite backend. The
following command is executed every day by cron:
doveadm expunge -A mailbox Trash savedbefore 30d
I started to use the expire plugin about one month ago. Since then,
using "doveadm search -A mailbox Trash save
Hello,
> Are the timestamps wrong in the database? They should contain the
> timestamp of the oldest save-date of message in the mailbox.
How can I look at the timestamps and check them? I opened my database with
sqlite3 and entered "select * from expires;" this showed only one line:
christoph|
at, with every mail in a single file? I am using mdbox right now.
Best regards
Christoph
On Tuesday, 22 February 2011 10:07:40 Timo Sirainen wrote:
> On Sat, 2011-02-19 at 10:10 +0100, Christoph Pleger wrote:
> > I started to use the expire plugin about one month ago. Since
Hello,
Timo Sirainen wrote:
> Are the timestamps wrong in the database? They should contain the
> timestamp of the oldest save-date of message in the mailbox.
Today, messages from Trash have been expunged again.
The only timestamp in the database is Sun Mar 6 08:37:55 UTC 2011. This is
obvio
Hello,
Timo Sirainen wrote:
> > Does anyone have an idea what is going wrong with the timestamps?
>
> So it's as if the timestamp keeps changing to the newest deleted
> message.. Maybe mail_debug=yes shows something helpful with these
> patches:
>
> http://hg.dovecot.org/dovecot-2.0/rev/eac54c2dc
Hello,
I wrote:
> > So it's as if the timestamp keeps changing to the newest deleted
> > message.. Maybe mail_debug=yes shows something helpful with these
> > patches:
> >
> > http://hg.dovecot.org/dovecot-2.0/rev/eac54c2dc98b
> > http://hg.dovecot.org/dovecot-2.0/rev/63ed0d3f4f52
> > http://hg.d
Hello,
Timo Sirainen wrote:
> > > It seems to work now. Message were expunged today and 'doveadm search
> > > -A mailbox Trash savedbefore d' still shows me messages that are
> > > four days old or younger.
> >
> > Big surprise: Something bad must have happened after the messages were
> > delete
Hello,
> > Big surprise: Something bad must have happened after the messages were
> > deleted from Trash; now all messages are zero days old.
>
> Are you using maildir? Did you run with those patches + mail_debug=yes?
Today, the daily cronjob expired some messages. I have attached the output of
Hello,
> > Big surprise: Something bad must have happened after the messages were
> > deleted from Trash; now all messages are zero days old.
>
> Are you using maildir? Did you run with those patches + mail_debug=yes?
Today, the daily cronjob expired some messages. I have attached the output of
Hello,
>> Today, the daily cronjob expired some messages. I have attached the
>> output of
>> the job.
> It looks like it expunged all the messages from Trash. Did you check if
> that happened? Did it expunge too many messages?
No, after expunging, there still were messages in the Trash folder.
Hello,
> It looks like it expunged all the messages from Trash. Did you check if
> that happened? Did it expunge too many messages?
>
> > Mar 18 09:50:28 joseph dovecot: imap(christoph): Debug: expire: Saving
> > first message to Trash, updating timestamp to 1300438228
>
> This happens, because it
Hello,
Timo Sirainen wrote:
> > Is there any solution in sight for this? Is there some additional
> > information I can give you for solving that problem?
>
> Well, the weird thing is that the logs say it's expunging everything and
> you say it's not.. What about if you change the cronjob to do:
Hello,
>> I have attached a file with the output of yesterday's cron job's
>> execution. As
>> you can see, after expunging there are still messages in the Trash
>> folder,
>> though expunge itself says that it has removed the first message.
>
> Thanks. Looks like it was a simple mdbox-specific bu
Hello,
> Thanks. Looks like it was a simple mdbox-specific bug. Fixed:
> http://hg.dovecot.org/dovecot-2.0/rev/2269cea521b6
Yes, that was it. Expunging works fine now.
Regards
Christoph
Hello,
On 2019-08-28 14:10, Aki Tuomi via dovecot wrote:
Dear subscribers, we have been made aware of critical vulnerability in
Dovecot and Pigeonhole.
Has this already been fixed in 2.2.36.4? Changelog does not mention it.
Regards
Christoph
30 matches
Mail list logo
