From: Chris Faylor <cgf@cygnus.com>
To: Ben Elliston <bje@redhat.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: ezmlm error
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000721233625.A17194@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0007221300020.8152-100000@moshpit.cygnus.com>
On Sat, Jul 22, 2000 at 01:00:59PM +1000, Ben Elliston wrote:
>Hi,
>
>When subscribing to new mailing lists, ezmlm tells me to reply to
><long-string>@redhat.com. That should be @sources.redhat.com. I reported
>this to sourcemaster@cygnus.com, but that it semes that went to the bit
>bucket.
Can you send me an example of this problem, Ben? I can't find anything
obvious in the ezmlm stuff.
cgf
WARNING: multiple messages have this Message-ID
From: Chris Faylor <cgf@cygnus.com>
To: Ben Elliston <bje@redhat.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: ezmlm error
Date: Fri, 21 Jul 2000 20:36:00 -0000 [thread overview]
Message-ID: <20000721233625.A17194@cygnus.com> (raw)
Message-ID: <20000721203600.OIdWRbjbRG6VV9sWmOnEnnIp6-5HlEtH1q6kx3U40U8@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0007221300020.8152-100000@moshpit.cygnus.com>
On Sat, Jul 22, 2000 at 01:00:59PM +1000, Ben Elliston wrote:
>Hi,
>
>When subscribing to new mailing lists, ezmlm tells me to reply to
><long-string>@redhat.com. That should be @sources.redhat.com. I reported
>this to sourcemaster@cygnus.com, but that it semes that went to the bit
>bucket.
Can you send me an example of this problem, Ben? I can't find anything
obvious in the ezmlm stuff.
cgf
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Ben Elliston
2000-07-21 20:01 ` Ben Elliston
2000-12-30 6:08 ` Chris Faylor
2000-07-21 20:31 ` Chris Faylor
2000-12-30 6:08 ` Chris Faylor [this message]
2000-07-21 20:36 ` Chris Faylor
2000-12-30 6:08 ` Ben Elliston
2000-07-21 21:01 ` Ben Elliston
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=20000721233625.A17194@cygnus.com \
--to=cgf@cygnus.com \
--cc=bje@redhat.com \
--cc=overseers@sourceware.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).