search for: plmail

Op 5/19/2017 om 8:33 AM schreef Christoph Pleger: > 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

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 search in all folders, only results from INBOX are found, then the error message is shown.

...onfiguration (output > from `dovecot -n`)? What exact Sieve script demonstrates this behavior? The output of 'dovecot -n' is attached. The sieve script is: if header :is "X-Virus-Status" "Yes" { discard; notify :method "mailto" :options "christoph at plmail.de" :high :message "Hallo, $env-from$ hat Ihnen eine Nachricht von $from$ mit dem Betreff $subject$ gesendet, die vom Virenscanner als infiziert erkannt und daher gel?scht wurde. Mit freundlichen Gr??en postmaster at plmail.de"; stop; } Regards Christoph -------------- n...

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 you enable core dumps and run bt full in gdb? I attached the result.

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 <postmaster@>, instead of <postmaster at mailserver.domain>, like it was before. Is it possible to revert to the old format?

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 <postmaster@>, instead of > <postmaster at mailserver.domain>, like it

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

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 thinks the Trash was empty.. Is there any solution in sight for this?

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 it to my dovecot folder Yesterday, I created a new user and wanted to let him have rules 1 and 2

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) VALUES ('1292525469','christoph','Trash')) failed: unable to open database

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 savedbefore <days>" with different values for <days>, I could see every day how