From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam.el puts mail into bogus group
Date: Tue, 17 Jun 2003 11:26:16 -0400 [thread overview]
Message-ID: <4nptlc9147.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <el1tgn16.fsf@calmar.ws>
On Tue, 17 Jun 2003, mac@calmar.ws wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Mon, 16 Jun 2003, mac@calmar.ws wrote:
>>> Hi,
>>> I have installed spam.el a few days ago, and I'm not able to
>>> handle it really.
>>>
>
>>> So why are there errors while receiving the mails (error in
>>> fancy-splitting --> use bogus group (or similar))?
>>
>> Without your settings, it's hard to know what's wrong
>
> Since I installed http://www.calwell.ca/articles/a0012.php Bind
> from there, (with the included 'dig' program)
> there are no errors anymore.
I'm glad you found the problem. Please consider submitting a gnus-bug
or including your settings manually next time, it's very hard to tell
what the problem is without your settings.
Thanks
Ted
prev parent reply other threads:[~2003-06-17 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 6:20 calmar
2003-06-16 17:13 ` Paul Furnanz
[not found] ` <4nel1uj8g7.fsf@lockgroove.bwh.harvard.edu>
2003-06-16 21:24 ` calmar
[not found] ` <el1tgn16.fsf@calmar.ws>
2003-06-17 15:26 ` Ted Zlatanov [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=4nptlc9147.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.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).