From: Henrik Storner <henrik-kernel@hswn.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: Problems contacting Linus
Date: Mon, 21 Jul 2003 08:03:07 +0000 (UTC) [thread overview]
Message-ID: <bfg6nr$ekr$1@ask.hswn.dk> (raw)
In-Reply-To: 200307210744.h6L7iUDW000468@81-2-122-30.bradfords.org.uk
In <200307210744.h6L7iUDW000468@81-2-122-30.bradfords.org.uk> John Bradford <john@grabjohn.com> writes:
>> Some of my mails to Linus return with:
>> <torvalds@osdl.com>: host mail.goweb.com[211.174.63.240] said: 550 5.7.1
>> <torvalds@osdl.com>... Relaying denied. Proper authentication
>> required.
Try using "osdl.ORG" instead of "osdl.COM"
Henrik
--
Henrik Storner <henrik@hswn.dk>
next prev parent reply other threads:[~2003-07-21 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 7:44 Problems contacting Linus John Bradford
2003-07-21 8:03 ` Henrik Storner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-21 9:26 John Bradford
2003-07-20 22:58 Pavel Machek
2003-07-20 23:02 ` Davide Libenzi
2003-07-20 23:16 ` Olaf Dietsche
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='bfg6nr$ekr$1@ask.hswn.dk' \
--to=henrik-kernel@hswn.dk \
--cc=linux-kernel@vger.kernel.org \
/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).