From: Soren Dayton <dayton@overx.com>
Subject: Re: Why doesn't posting through nntp proxies work?
Date: Wed, 08 Sep 1999 18:18:15 GMT [thread overview]
Message-ID: <861zc95kt9.fsf@polo.overx.com> (raw)
In-Reply-To: <xnohfl6rjm9.fsf@tyr.diku.dk>
Peter Makholm <peter@makholm.net> writes:
> Soren Dayton <dayton@overx.com> writes:
>
> > And I can't post. When I try (C-c C-c in the message buffer) gnus
> > reports:
> >
> > No methods specified to send by
>
> I got the same problem (sometimes). I can't exatly say when it errors
> but it seems I always get it when following up on messages read on
> foreing servers posting through foreing servers.
This problem sounds like the gnus-post-method.
> *Backtrace*:
> Signaling: (error "No methods specified to send by")
> signal(error ("No methods specified to send by"))
> error("No methods specified to send by")
> message-send(nil)
> message-send-and-exit(nil)
> call-interactively(message-send-and-exit)
But this is what I get all the time
prev parent reply other threads:[~1999-09-08 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 6:31 Soren Dayton
1999-08-31 15:31 ` Kai Großjohann
1999-09-04 6:20 ` Soren Dayton
1999-09-07 12:29 ` Peter Makholm
1999-09-08 18:18 ` Soren Dayton [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=861zc95kt9.fsf@polo.overx.com \
--to=dayton@overx.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).