Re: antispam plugin pipe script seems not to be called when it "should be"

On 16-08-18 22:43:32, Ben Johnson wrote: > On 8/18/2016 10:26 PM, Ben Johnson wrote: > > Hello, > > > > (Full "doveconf -n" output is at the end of this message.) > > > > I'm attempting to recreate a "recipe" I had used successfully for quite > > some time (in Ubuntu 12.04 LTS), which allowed me

Re: antispam plugin pipe script seems not to be called when it "should be"

On 8/18/2016 10:26 PM, Ben Johnson wrote: > Hello, > > (Full "doveconf -n" output is at the end of this message.) > > I'm attempting to recreate a "recipe" I had used successfully for quite > some time (in Ubuntu 12.04 LTS), which allowed me to train > SpamAssassin's Bayes database when someone

antispam plugin pipe script seems not to be called when it "should be"

Hello, (Full "doveconf -n" output is at the end of this message.) I'm attempting to recreate a "recipe" I had used successfully for quite some time (in Ubuntu 12.04 LTS), which allowed me to train SpamAssassin's Bayes database when someone dragged an email message from one sub-folder of the

Re: What might cause messages delivered with dovecot-lda to be "invisible" to IMAP clients?

I'm mildly ashamed of myself. The "butchered" messages were presumably the result of not having a valid message structure with appropriate syntax. If I do this, the mail is delivered and "visible" in any client, as expected: # su vmail $ cd ~ $ wget http://spamassassin.apache.org/gtube/gtube.txt

What might cause messages delivered with dovecot-lda to be "invisible" to IMAP clients?

Hello! I'm attempting to use dovecot-lda, and for whatever reason, messages that I send with it are not visible in my IMAP client. $ dovecot --version 2.2.22 (fe789d2) (Full "doveconf -n" output is at the bottom of this message!) Here's the the sequence of commands that I'm using: # su vmail

Quota issue: enforced, but reporting issue

Hello everyone, I face the following challenge: - dovecot 2.2.13 - userdb: passwd-file - quota enabled: -- default 1GB -- changed for some users thru users file: user@domain:passwd::userdb_quota_rule=*:storage=15M - when sending a message to this user while near quota, warnings are

Re: [patch] Improved error checking for the dovecot-antispam-plugin

(snip) > I have no issue in resending a new version of the patch with better > error reporting, will do so in the following days. > > Robert I've attached a second version of the patch, feel free to consider any of them for inclusion. Thanks, Robert -- http://robert.muntea.nu/ changeset:

Re: [patch] Improved error checking for the dovecot-antispam-plugin

Hi Harlan, On Wed, Aug 17, 2016 at 2:18 AM, Harlan Stenn wrote: > On 8/16/16 1:24 PM, Robert Munteanu wrote: >> Hi, >> >> Hopefully this is the right channel for such a patch. I have a minor >> enhancement to submit for the antispam plugin >> >>

Re: Reporting on CephFS being ready to use with Dovecot

Hi, > On 17 Aug 2016, at 23:29, Daniel van Ham Colchete > wrote: > My setup involves two clusters, each with about 30k-40k users. Each cluster > will have two HD storages (with 6TB HDs), two SSD storages (with Intel > 480GB SSDs) and two frontends. In a few months

Re: POP3 strange logging behavior after upgrade from 2.2.13 to 2.2.25

On 09.08.2016 16:50, Iavor Stoev wrote: > Hello, > > After the upgrade from Dovecot version 2.2.13 to 2.2.25, > we experience the following strange behavior with POP3 logging. > > When a connection is closed with reason "Connection closed" & > "Disconnected for inactivity", the number of deleted

Re: 2.3.0~alpha0-1~auto+197: Crash when openening a message via IMAP

On 12.07.2016 12:25, Ralf Hildebrandt wrote: > * Timo Sirainen : >> On 11 Jul 2016, at 14:15, Ralf Hildebrandt >> wrote: >>> From the log: >>> >>> Jul 11 13:12:42 mproxy dovecot: imap-login: Login: user=, >>> method=PLAIN, rip=141.42.206.36,

dsync replication issue

Hello, I'm facing a problem with dsync : replication between my two dovecot 2.2.10 servers (10.10.10.10 = serverA and 10.10.10.11 = serverB) is not done when a mail is received on any of the two servers. Sync is correctly working when running "doveadm [-D] sync -A tcp:10.10.10.10:12345" from