Gnus development mailing list
 help / color / mirror / Atom feed
From: Christoph Groth <christoph@grothesque.org>
To: ding@gnus.org
Subject: with local imap: sent mail (Gcc) sometimes not saved
Date: Fri, 28 Nov 2014 00:41:08 +0100	[thread overview]
Message-ID: <87d2888b57.fsf@grothesque.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

Hi,  I’m using Gnus (from Emacs 24.4.1) with a local dovecot and 
mbsync for synchronizing to remote IMAP servers [1].   This works 
really rather well.  There is, however, one problem:  I set the 
gcc-self Gnus parameter to save all outgoing mail.  Usually this 
works flawlessly, but from time to time I cannot find some message 
that I know that was sent out successfully (I can see it in my 
msmtp log, and I also already got replies to such messages).  Do 
you have any suggestions how to debug this?  I noticed that 
dovecot, when used directly through the /usr/lib/dovecot/imap 
executable, does not seem to log anything.  I tried to add the 
command line parameter 
 
 -o log_path=/home/myuser/.dovecot.log 
 
but nothing gets logged there.

For now, I've added "2>>$HOME/.dovecot.err" to the end of
nnimap-shell-program.  Nothing has appeared there so far, so I'm not too
confident to be able to catch the problem in this way.  Also, I'm not
even sure whether it's a dovecot problem at all.  It could be also due
to Gnus itself.

It's disquieting to randomly and quietly loose mail.  I'd love to fix this.

Christoph


[1] http://roland.entierement.nu/blog/2010/09/08/gnus-dovecot-offlineimap-search-a-howto.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 810 bytes --]

             reply	other threads:[~2014-11-27 23:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 23:41 Christoph Groth [this message]
2014-11-28 11:44 ` Couldn't store article in group Christoph Groth
2015-01-26  4:07   ` Lars Ingebrigtsen
2015-01-26 22:13     ` Christoph Groth
2015-01-27  0:50       ` Lars Ingebrigtsen
2015-01-28 12:56         ` Alan Schmitt
2015-01-29  1:37           ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d2888b57.fsf@grothesque.org \
    --to=christoph@grothesque.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).