Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Michael Slass <miknrene@drizzle.com>
Subject: Re: tracing mail problems... how to?
Date: Sun, 17 Nov 2002 03:23:32 GMT	[thread overview]
Message-ID: <m3u1iglvqt.fsf@localhost.localdomain> (raw)
In-Reply-To: <87k7jdhths.fsf@hilarius.disorg>

Garglemonster <garglemonster@my-deja.com> writes:

>i'm having some difficulty with my email setup these days.  the
>problem is that some of my mail is not reaching the intended
>recipients.  i hit C-c C-c and the mail seems to go out, but never
>gets there.  i doubt that this is a gnus problem -- some of my mail
>does go out -- but just to be sure, i'd like to hear something more
>than 'Sending...' from gnus.
>
>tracking such problems used to be easy when i dumped all my mail off
>to sendmail on localhost; i'd just check my logs and the returned
>mail.  in this case, however, i don't have logs or rejected mail. 
>
>thanks for your help.

Look for a buffer called *trace of SMTP session to ... *
Might have useful info in it.


-- 
Mike Slass


      reply	other threads:[~2002-11-17  3:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17  1:31 Garglemonster
2002-11-17  3:23 ` Michael Slass [this message]

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=m3u1iglvqt.fsf@localhost.localdomain \
    --to=miknrene@drizzle.com \
    /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).