Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: [BUG] Xemacs-21.5-b1/i686-pc-cygwin Build-Report, GNUS
Date: Thu, 23 Aug 2001 11:59:28 -0400	[thread overview]
Message-ID: <87bsl6bwdb.fsf@mclinux.com> (raw)
In-Reply-To: <5.1.0.14.0.20010822181254.03b4a3d0@mail>

"David A. Cobb" <superbiskit@home.com> writes:

> Ran build-report.  Typed C-c,C-c.  The message & gnus portions did
> their thing and reported "send .... complete".  The "*Sent message
> . . ." buffer now has a message-id and date stamp which must have
> come from the mail server, proving the connection was made.

What Adrian said, but I thought I'd mention that this is a false
assumption here.  Gnus adds the Date stamp and the message id before
sending the mail, so I'd definately make sure the SMTP sending is
working. (see other reply).

ttyl,

-- 
Josh Huber


      parent reply	other threads:[~2001-08-23 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 22:19 David A. Cobb
2001-08-23  4:53 ` Adrian Aichner
2001-08-23 15:59 ` Josh Huber [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=87bsl6bwdb.fsf@mclinux.com \
    --to=huber@alum.wpi.edu \
    /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).