dovecot - Nov 2016 - How does one mark all messages as read (imap4flag "seen") with sieve?

so to summarize:
postfix (what version?)
dovecot-antispam plugin (version?  Installed from where?)

and when your script invokes deliver you get a core dump.
Have you a stack-trace from that coredump?



On Wed, Nov 9, 2016 at 5:49 PM, Ben Johnson <ben at indietorrent.org>
wrote:
> On 11/5/2016 1:22 PM, Larry Rosenman wrote:
> > What OS/MTA are you using?  Can you give me (privately if you want) a
> > re-hash of the LDA issues?
> >
> > I'm using FreeBSD 10.3 / Exim for my set up and LMTP for ALL
deliveries,
> > and it works great.
>
> Thanks again for your willingness to help with this, Larry.
>
> I'm using Postfix.
>
> Regarding the OS, I'm using Ubuntu 16.04 here, which ships dovecot
> 2.2.22 at present.
>
> ---- Slightly off-topic, but I'll bring it full-circle... ----
>
> Sure, a quick recap of the crashing issue I'm having with dovecot-lda:
>
> I struggled to get this working the first time (in dovecot 2.0.19), but
> prevailed with lots of help from this list. I described the roadblocks I
> encountered along the way in this thread:
>
> http://www.dovecot.org/list/dovecot/2013-June/091018.html
>
> All was well until I upgraded from Ubuntu 12.04 LTS to 14.04 LTS and
> thereby from Dovecot 2.0.19 to 2.2.9. To be clear (and it may be very
> relevant), this was a "manual" server migration and not an
> OS-level/package-managed upgrade. Point being, the potential to botch
> some aspect of the extremely fragile configuration was absolutely present!
>
> I wrote about the problems I encountered after the upgrade here:
>
> http://www.dovecot.org/list/dovecot/2014-July/097234.html
>
> The thread died-out, but I rekindled it here:
>
> http://www.dovecot.org/list/dovecot/2014-August/097385.html
>
> I ran out of steam after a soft dead-end.
>
> I wrote more about it a couple months later, mostly in the context of
> difficulty with dovecot-lda logging in an effort to debug the issue, but
> the thread received no replies:
>
> http://www.dovecot.org/list/dovecot/2014-October/098127.html
>
> Nearly two years later, I tried again:
>
> http://www.dovecot.org/list/dovecot/2016-August/105221.html
>
> The thread received some traction, and I changed the subject line to be
> more accurate partway through, which begins here:
>
> http://www.dovecot.org/list/dovecot/2016-August/105236.html
>
> I ended-up running with Karol's final suggestion, which was to forego
> the LDA in favor of a simple filesystem move/copy operation.
>
> But now the problem I'm having (to bring it full circle!) is that I
> can't mark the Antispam plugin's incoming emails as seen/read
> automatically because they aren't delivered by an LDA. And I want to
get
> this working with an LDA again for this reason, among others, such as
> quotas not being enforced when a "trained" message is
"copied" on the
> filesystem instead of "delivered" via an LDA.
>
> The more I think about this, the more I think I should go back and study
> the very first thread from June, 2013... maybe the solution is more or
> less the same!
>
> -Ben
>


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c)     E-Mail: larryrtx at gmail.com
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

On 11/9/2016 7:04 PM, Larry Rosenman wrote:
> so to summarize:
> postfix (what version?)
> dovecot-antispam plugin (version?  Installed from where?)
> 
> and when your script invokes deliver you get a core dump. 
> Have you a stack-trace from that coredump?
Yes, that summarizes it!

Postfix version 3.1.0 (installed from Ubuntu 16.04 repos.

Antispam plugin version 2.0+20150222-1build1, also installed from Ubuntu
16.04 repos.

Regarding a stack-trace, I forgot to mention that I ran into roadblocks
with that, too (the "average end-user doesn't have a chance!), as
described at

http://www.dovecot.org/list/dovecot/2016-September/105417.html

and no one was willing and able to offer assistance.

I persisted in the thread at

http://www.dovecot.org/list/dovecot/2016-September/105422.html

which dead-ended eventually with the stack-trace posted here:

http://pastebin.com/4xdGNXa6

Thanks again,

-Ben

looks to me from the coredump (although you pointed to the wrong binary)
that
deliver was PANIC()'ing with

io_add(0x%x) called twice fd=%d, callback=%p -> %p

I'm not sure what that message means, but maybe one of the dovecot folks
does.

Are all the packages built together?

Are you averse to compiling stuff yourself?



On Wed, Nov 9, 2016 at 6:25 PM, Ben Johnson <ben at indietorrent.org>
wrote:
> On 11/9/2016 7:04 PM, Larry Rosenman wrote:
> > so to summarize:
> > postfix (what version?)
> > dovecot-antispam plugin (version?  Installed from where?)
> >
> > and when your script invokes deliver you get a core dump.
> > Have you a stack-trace from that coredump?
>
> Yes, that summarizes it!
>
> Postfix version 3.1.0 (installed from Ubuntu 16.04 repos.
>
> Antispam plugin version 2.0+20150222-1build1, also installed from Ubuntu
> 16.04 repos.
>
> Regarding a stack-trace, I forgot to mention that I ran into roadblocks
> with that, too (the "average end-user doesn't have a chance!), as
> described at
>
> http://www.dovecot.org/list/dovecot/2016-September/105417.html
>
> and no one was willing and able to offer assistance.
>
> I persisted in the thread at
>
> http://www.dovecot.org/list/dovecot/2016-September/105422.html
>
> which dead-ended eventually with the stack-trace posted here:
>
> http://pastebin.com/4xdGNXa6
>
> Thanks again,
>
> -Ben
>


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c)     E-Mail: larryrtx at gmail.com
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

On 11/10/2016 2:02 AM, Aki Tuomi wrote:
> Hi!
> 
> Can you provide bt full from gbd?
> 
> Install debug symbols and acquire core file
> 
> Run gdb /path/to/bin /path/to/core
> 
> Issue bt ful
> 
> Send it to list.
> 
> 
> Aki Tuomi
> 
> Dovecot oy 
> 
> 
> 
>     On November 10, 2016 at 2:42 AM Larry Rosenman <larryrtx at
gmail.com>
>     wrote:
> 
>     looks to me from the coredump (although you pointed to the wrong
binary)
>     that
>     deliver was PANIC()'ing with
> 
>     io_add(0x%x) called twice fd=%d, callback=%p -> %p
> 
>     I'm not sure what that message means, but maybe one of the dovecot
folks
>     does.
> 
>     Are all the packages built together?
> 
>     Are you averse to compiling stuff yourself?


Thanks so much for the assistance here, Larry and Aki.

Aki, you had asked me to send this core-dump to the list when I asked
about it back in September; I did post the "bt full" output at that
time, but there were no further replies:

http://www.dovecot.org/list/dovecot/2016-September/105428.html

And for convenience, here is the "bt full" output I posted back then:

http://pastebin.com/4xdGNXa6

So, this is where I'm confused: Larry, you mentioned "although you
pointed to the wrong binary", which is a concern I had asked about back
in September:

http://www.dovecot.org/list/dovecot/2016-September/105424.html

I still don't understand how this is pointing to the wrong binary:

# gdb /usr/lib/dovecot/dovecot-lda
/var/vmail/tmp/core-deliver-6-5000-5000-29125-1473732949

Is /usr/lib/dovecot/dovecot-lda not the binary that segfaulted here?
Sure, the gdb output says, "Core was generated by
`/usr/lib/dovecot/deliver ...", but on the system in question, that is a
symlink pointing to /usr/lib/dovecot/dovecot-lda:

# ls -lah /usr/lib/dovecot/deliver
lrwxrwxrwx 1 root root 11 Sep 21 10:29 /usr/lib/dovecot/deliver ->
dovecot-lda

What am I missing here? The mismatch message does say something specific
about this:

warning: the debug information found in "/lib64/ld-2.23.so" does not
match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

Is this the result of pointing to the wrong executable when calling
"gdb"? If so, where is the correct executable to pass as the fist
argument?

Again, for convenience, the pipe script I'm using:

http://pastebin.com/zXzBDcvG

And the debug output from said pipe script:

http://pastebin.com/rz2f4S4G

My full "doveconf -n":

http://pastebin.com/hCgpA009

Thanks!

-Ben