From: Christopher Faylor <cgf@redhat.com>
To: Jason Molenda <jason@molenda.com>
Cc: Ian Lance Taylor <ian@zembu.com>, overseers@sources.redhat.com
Subject: Re: [MAILER-DAEMON@sources.redhat.com: failure notice]
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20001107194625.A13594@redhat.com> (raw)
In-Reply-To: <20001107152151.A8280@shell17.ba.best.com>
I agree that Ian was amazing diplomatic in his response. It's
nice to know who I can send all of the angry email to in the future.
:-)
On Tue, Nov 07, 2000 at 03:21:51PM -0800, Jason Molenda wrote:
>Another option is to use a free e-mail service like, oh I don't
>know, Yahoo Mail. Set up a Yahoo Mail account and you can send
>your outgoing mail through them, and you can even retrieve any
>Yahoo Mail via POP3. I'm sure Hotmail and other free mail services
>on the net provide similar services.
This is what I usually suggest.
What about his idea of allowing anyone who was a subscriber to the
mailing list in question through? That would be easy to implement.
Do we want to do this?
cgf
WARNING: multiple messages have this Message-ID
From: Christopher Faylor <cgf@redhat.com>
To: Jason Molenda <jason@molenda.com>
Cc: Ian Lance Taylor <ian@zembu.com>, overseers@sources.redhat.com
Subject: Re: [MAILER-DAEMON@sources.redhat.com: failure notice]
Date: Tue, 07 Nov 2000 16:46:00 -0000 [thread overview]
Message-ID: <20001107194625.A13594@redhat.com> (raw)
Message-ID: <20001107164600.KqWiJ54YSn2csAQAz9hrj2wVtyA99xkQ1ez7NbSC_28@z> (raw)
In-Reply-To: <20001107152151.A8280@shell17.ba.best.com>
I agree that Ian was amazing diplomatic in his response. It's
nice to know who I can send all of the angry email to in the future.
:-)
On Tue, Nov 07, 2000 at 03:21:51PM -0800, Jason Molenda wrote:
>Another option is to use a free e-mail service like, oh I don't
>know, Yahoo Mail. Set up a Yahoo Mail account and you can send
>your outgoing mail through them, and you can even retrieve any
>Yahoo Mail via POP3. I'm sure Hotmail and other free mail services
>on the net provide similar services.
This is what I usually suggest.
What about his idea of allowing anyone who was a subscriber to the
mailing list in question through? That would be easy to implement.
Do we want to do this?
cgf
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 [MAILER-DAEMON@sourceware.cygnus.com: " Ian Lance Taylor
2000-11-07 10:10 ` Ian Lance Taylor
2000-12-30 6:08 ` Jason Molenda
2000-11-07 15:22 ` Jason Molenda
2000-12-30 6:08 ` Christopher Faylor [this message]
2000-11-07 16:46 ` [MAILER-DAEMON@sources.redhat.com: " Christopher Faylor
2000-12-30 6:08 ` Jason Molenda
2000-11-07 17:25 ` Jason Molenda
2000-12-30 6:08 ` Christopher Faylor
2000-11-07 19:38 ` Christopher Faylor
2000-12-30 6:08 ` Jason Molenda
2000-11-07 19:43 ` Jason Molenda
2002-01-03 8:29 Craig Rodrigues
2002-07-25 9:08 Zack Weinberg
2002-11-19 12:38 Roland McGrath
2002-11-19 13:36 ` Christopher Faylor
2002-11-19 13:38 ` Roland McGrath
2002-11-19 14:02 ` Christopher Faylor
2002-11-19 13:39 ` Jason Molenda
2003-01-20 17:06 Daniel Jacobowitz
2003-12-17 8:45 Robert Schiele
2003-12-17 15:40 ` Christopher Faylor
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=20001107194625.A13594@redhat.com \
--to=cgf@redhat.com \
--cc=ian@zembu.com \
--cc=jason@molenda.com \
--cc=overseers@sources.redhat.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).