From: Juha Autero <Juha.Autero@iki.fi>
Subject: Re: smtp server
Date: Mon, 02 Sep 2002 19:18:54 +0300 [thread overview]
Message-ID: <878z2k8ivl.fsf@intercal.localdomain> (raw)
In-Reply-To: <iluheh94n34.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Wu XiaoGuang <woohsiaokuang@yahoo.com.cn> writes:
>
>> RCPT TO: <xgwu@linux.net.cn>
>> 500 error in command
>
> I don't see any error in that command. Is the server really working?
I don't think that you have to allow (white)space after "RCPT TO:". At
least RFC 2821 describes the syntax as:
"RCPT TO:" ("<Postmaster@" domain ">" / "<Postmaster>" / Forward-Path)
[SP Rcpt-parameters] CRLF
--
Juha Autero
http://www.iki.fi/jautero/
Eschew obscurity!
prev parent reply other threads:[~2002-09-02 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2hehbvxpe.fsf@localhost.localdomain>
[not found] ` <m2vg5ruirx.fsf@localhost.localdomain>
2002-09-01 0:10 ` Simon Josefsson
[not found] ` <m21y8dzz8k.fsf@localhost.localdomain>
[not found] ` <iluheh94n34.fsf@latte.josefsson.org>
2002-09-02 16:18 ` Juha Autero [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=878z2k8ivl.fsf@intercal.localdomain \
--to=juha.autero@iki.fi \
/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).