Gnus development mailing list
 help / color / mirror / Atom feed
From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: unsent messages
Date: Thu, 05 Aug 2010 10:16:50 +0200	[thread overview]
Message-ID: <874of9fqhs.fsf@mean.albasani.net> (raw)
In-Reply-To: <87k4o51pq6.fsf@pellet.net> (Eric Abrahamsen's message of "Thu, 05 Aug 2010 00:30:09 -0700")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> It seems to be working fine, but the original problem was so sporadic
> it's really hard to know. I can say that since I started using the queue
> I don't seem to have lost any messages.
>
> I also don't know who to "blame", though it does seem that msmtp would
> leave something in the logs if it choked...

Well, just keep using it and if you find a message queued that should
have been sent, please post the corresponding lines of your log
files; it will happen eventually, I assume.

Have a look at these excerpts from my logs:


,---- msmtp.queue.log
| 2010 27 Jul 19:55:13 : mail for [ -oi -f
| gegendosenfleisch@googlemail.com -t ] : send was successful
|
! 2010 27 Jul 20:09:07 : mail for [ -oi -f xxx@xxx.xxx -t ] : couldn't
! be sent - host not connected
! 2010 27 Jul 20:09:07 : enqueued mail as : [ 2010-07-27-20.09.07 ] (
! -oi -f xxx@gmx.net -t ) : successful
|
| 2010 27 Jul 20:27:40 : mail for [ -oi -f
| gegendosenfleisch@googlemail.com -t ] : send was successful
`----

,---- msmtp.log
| Jul 27 19:55:13 host=smtp.gmail.com tls=on auth=on
| user=gegendosenfleisch@googlemail.com
| from=gegendosenfleisch@googlemail.com
| recipients=xxx@live.com mailsize=121663 smtpstatus=250
| smtpmsg='250 2.0.0 OK 1280253313 a9sm4036453bxx.23' exitcode=EX_OK
|
| Jul 27 20:27:40 host=smtp.gmail.com tls=on auth=on
| user=gegendosenfleisch@googlemail.com
| from=gegendosenfleisch@googlemail.com
| recipients=eric@ericabrahamsen.net,ding@gnus.org mailsize=2758
| smtpstatus=250 smtpmsg='250 2.0.0 OK 1280255260 f10sm4061429bkl.17'
| exitcode=EX_OK
`----

"couldn't be sent - host not connected" : I was definately online when I
sent that mail. Thats why I think my (really) unreliable wifi is
responsible. 
Lets see what your logs will say.

Maybe, I should ask on the msmtp list, but not yet.





  reply	other threads:[~2010-08-05  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27  0:36 Eric Abrahamsen
2010-07-27 18:27 ` Memnon Anon
2010-08-03 18:55   ` Ted Zlatanov
2010-08-05  2:44     ` Memnon Anon
2010-08-05  7:30       ` Eric Abrahamsen
2010-08-05  8:16         ` Memnon Anon [this message]
2010-08-15 18:41     ` Memnon Anon
2010-08-18 13:38       ` Ted Zlatanov

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=874of9fqhs.fsf@mean.albasani.net \
    --to=gegendosenfleisch@googlemail.com \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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).