From: dmonjar@orgtek.com (Daniel A. Monjar)
Subject: followup to 'I can't post and article'
Date: 18 Aug 1999 10:52:55 -0400 [thread overview]
Message-ID: <m3n1vpuomw.fsf@monjard.orgtek.com> (raw)
My problem was a bad From entry. I was playing with some stuff,
testing someone's theory that since spam harvesters only look at the
>From header that by having a bad from and a correct Reply-To one could
reduce spam stuff. After finally looking in the *Messages* buffer it
became obvious what was going on:
-----------
Loading mail-extr...
Loading mail-extr...done
Denied posting -- the From looks strange: "Daniel Monjar".
No methods specified to send by
-----
So I removed the From entry in .gnus:
-----
Sending...
There is no From line. Posting is denied.
No methods specified to send by
------
Guess it's looking for a '@' in the From?:
------
Sending...
Loading cl-seq...
Loading cl-seq...done
Sending...done
------
All is working now. Less than helpful error message though.
Thanks for the replies!
--
Daniel Monjar (mailto:dmonjar@orgtek.com)
Organon Teknika
Durham, NC US
next reply other threads:[~1999-08-18 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-18 14:52 Daniel A. Monjar [this message]
1999-08-27 18:05 ` Peter von der Ahé
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=m3n1vpuomw.fsf@monjard.orgtek.com \
--to=dmonjar@orgtek.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).