553 Requested action not taken: mailbox name not allowed.
kosy
To: myuser@mydomain.com at Internet Subject: test with
capitals
Subject: Undeliverable mail
Author: Postmaster at State
Date: 1/11/00 12:50 PM
----------------------------------------------------------------------
--------------------------
Reporting-MTA: dns;mailhub.theirdomain
Original-Recipient: rfc822;myuser@mydomain.com
Final-Recipient: rfc822;myuser@mydomain.com Action: failed
Status: 5.1.1
Remote-MTA: dns;mail.mydomain.com
Diagnostic-Code: smtp;553 Requested action not taken: mailbox name not
allowed
kosy
Rich Matheisen [MVP] <rich...@rmcons.com.NOSPAM.COM> wrote in message
news:qb9rascgvdtodd09e...@4ax.com...
> "kosy" <ko...@medmanagement.com> wrote:
>
> >I have the same problem between two separate domains and exchange
servers. I
> >recreated the problem with my friends domain and exchange server also. If
> >exchange is not sending the 553, who is?
>
> Why don't you try it yourself? Telnet to port 25 on your server, enter
> "HELO" and then "MAIL FROM: a'user@x.y" and "RCPT TO: a'nother@x.y".
> Do you get a 553?
YES
>
> >Ideas, somebody???
>
> It's easy to create a problem that *LOOKS* like this one, but is
> actually very different. Try sending THIS address (complete with
> leading and trailing apostrophes):
>
> 'us...@theirdomain.com'
NO LUCK EITHER
>
> The apostrophe is legal in the <local-part> of the address, but it's
> not allowed in the <domain> part.
>
>
> ------------------
> Rich Matheisen
> MCSE+I, Exchange MVP
> MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
I have been on Micro$oft's support to, just to discover that they have the
same problem. They also claim that apostrophe is not allowed according to
rfc822. How can this be?
Rich Matheisen [MVP]
>
>Rich Matheisen [MVP] <rich...@rmcons.com.NOSPAM.COM> wrote in message
>news:qb9rascgvdtodd09e...@4ax.com...
>> "kosy" <ko...@medmanagement.com> wrote:
>>
>> >I have the same problem between two separate domains and exchange
>servers. I
>> >recreated the problem with my friends domain and exchange server also. If
>> >exchange is not sending the 553, who is?
>>
>> Why don't you try it yourself? Telnet to port 25 on your server, enter
>> "HELO" and then "MAIL FROM: a'user@x.y" and "RCPT TO: a'nother@x.y".
>> Do you get a 553?
>YES
Okay, then tell us your e-mail domain so we can see for ourselves what
might be the problem. [See below. This is only needed if
"medmanagement.com" is not the e-mail domain exhibiting the problem.]
>> >Ideas, somebody???
>>
>> It's easy to create a problem that *LOOKS* like this one, but is
>> actually very different. Try sending THIS address (complete with
>> leading and trailing apostrophes):
>>
>> 'us...@theirdomain.com'
>NO LUCK EITHER
Of course not! That one's patently wrong!
[ snip ]
>I have been on Micro$oft's support to, just to discover that they have the
>same problem. They also claim that apostrophe is not allowed according to
>rfc822. How can this be?
Ask for the specific part of the BNF that they're telling you that
this apostrophe violates. Then tell us -- or look for yourself.
MS doesn't employ infallible people. Nor will you find them here.
Either you've explained the problem incorrectly to them, or they've
misunderstood your problem. In eather case you should take the
initiative and read RFC821. Discover for yourself that what I'm
telling you is the truth -- that apostrophe is NOT in violation of
either RFC821 or RFC822.
Just for the record, here's the information from DNS about your e-mail
domain:
QUESTIONS:
medmanagement.com., type = MX, class = 1
ANSWERS:
-> medmanagement.com.
type = MX, class = 1, ttl = 86400, dlen = 9
preference 10, mail exchanger = mail.medmanagement.com.
ADDITIONAL RECORDS:
-> mail.medmanagement.com.
type = A, class = 1, ttl = 86400, dlen = 4
inet address = 208.167.189.61
Here's what I see when I telnet to your server's IP address:
220 SMTP service ready
helo
250 Requested mail action okay, completed
mail from: m'e@a.b
553 Requested action not taken: mailbox name not allowed
This is NOT an Exchange server!
Here's what I get from an Exchange server:
220 dc3.rmcons.com ESMTP Server (Microsoft Exchange Internet Mail
Service 5.5.2650.21) ready
helo
250 OK
mail from: m'e@a.b
250 OK - mail from <m'e@a.b>
So, I repeat: telnet to YOUR SERVER, not some other SMTP relay, and
see what happens when you submit that supposedly illegal address to an
EXCHANGE server. Then submit your question to THAT software vendor for
resolution.
kosy
Thanks for all the help.
Rich Matheisen [MVP] <rich...@rmcons.com.NOSPAM.COM> wrote in message
news:lub3bscsi11m30jsh...@4ax.com...
> 553 Requested action not taken: mailbox name not allowed
>