Harald,
thanks for reporting.
On 2013-08-10 02:38, Reindl Harald wrote:
> after a week running dbmail 3.1 a short report
>
> * memory usage: perfect, dbmail-imapd currentyl 133 MB
> and sometimes it goes below 100 MB
> so no leaks and dail restarts needed
I see the same, and still improving in the master branch. And it's
not only the memory footprint that improves because of this, but also
speed to some extend.
> some small issues with no idea how to debug because
> it happens not often enough to enable debug-logs in
> production or not possible to reproduce with my clients
If it's impossible to reproduce reliably, it's difficult to debug. I run
into smaller and bigger problems all the time, mostly from testing with
the stuff in test-scripts. Also, adding new IMAP capabilities like I've
been busy doing since 3.1.2 exposes older code to review and
refactoring. I finally have a simple but effective framework in place
for automatic schema migrations - very cool. So, when adding a rather
complex capability like CONDSTORE (rfc4551) only takes a day or two, it
gives me a nice fuzzy feeling about the state of the code. I must be
doing something right. Of course that feeling disappears as I stumble on
older code that doesn't look quite right...
> * IMAP / Tunderbird: in the message-list randomly empty subject
> it is present in the preview
I've seen it, right around 3.1.0 or 3.1.1, but not since...
> mostly folder-options -> rapair let it appear in the list
> sometimes this is need twice, i can find no logic there
> maybe some timing/race-conditions, hard to debug
>
> * Apple Mail - i hate it
> POP3 as well as IMAP until now 3 messages which are
> reported to me with empy or crippeled body
> AFAIK all times multipart-messages
That is possibly a combination of the exact IMAP commands that expose a
bug in GMime. Only way to know for sure is by running the IMAP commands
Apple uses to fetch a message, against the exact MIME structure of the
message involved.
And even updating GMime is not guaranteed to fix things, since I've
worked around problems and limitations in GMime in the past, rather than
getting them fixed or dealt with in GMime proper.
GMime is really nice and it's author very helpful. It does however
depend on downstream users like dbmail for battle-testing some parts of
the code.
> in all cases no problem in roundcube-mail or Thunderbird
Good. I really love how much more responsive especially imap now is,
compared with 3.0.2.
> * twice one thread appeared to consume 100% CPU without
> lead to troubles for active users and SIGTERM ignroed
I would try to strace the thread involved. Maybe that will give me some
hint as to where it's happening in the code.
top -bH -n 1 -p <PID>
should give you a listing of the threads, with process-ids per thread.
Maybe one particular thread is causing havoc, which you can then strace.
> _____________________________________________
>
> [root@mail:~]$ systemctl status dbmail-imapd.service
> dbmail-imapd.service - DBMail IMAP Server
> Loaded: loaded (/usr/lib/systemd/system/dbmail-imapd.service;
> enabled)
> Active: active (running) since Di 2013-08-06 14:08:19 CEST; 3 days
> ago
> Main PID: 5921 (dbmail-imapd)
> CGroup: name=systemd:/system/dbmail-imapd.service
> └─5921 /usr/sbin/dbmail-imapd -D
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
