sorry, no mailbox here by that name (#5.1.1 - >chkuser)
Sanjay Mehta
I have a user trying to email us but they get the following error:
>RCPT TO generated following response:
>511 5.7.1 server [vmail1.sentex.ca] for <mehul.c...@parkinson.ca>
>rejected address saying "sorry, no mailbox here by that name (#5.1.1 -
>chkuser)"
what could be wrong because the email address seems fine.
thx
Susan
--
Susan Conkey [MVP]
"Sanjay Mehta" <Sanja...@discussions.microsoft.com> wrote in message
news:5DFBAD3E-4E62-4F7B...@microsoft.com...
Sanjay Mehta
At the moment I am aware its just one user from outside trying to email me
or user2 in our organisation.
I have pasted that error above.
Another user is having problem user2 and this time the error is:
>This Message was undeliverable due to the following reason:
>
>Your message was not delivered because the return address was refused.
>
>The return address was '<mini...@bellnet.ca
what could it be?
thanks
Susan
--
Susan Conkey [MVP]
"Sanjay Mehta" <Sanja...@discussions.microsoft.com> wrote in message
news:5AC83BD5-4CA8-4A92...@microsoft.com...
Sanjay Mehta
http://www.box.net/shared/clya7uqfbg
yes. is it our dns provider? what should we do?
thanksx
Susan
--
Susan Conkey [MVP]
"Sanjay Mehta" <Sanja...@discussions.microsoft.com> wrote in message
news:4012F50B-C19F-4D1C...@microsoft.com...
Rich Matheisen [MVP]
You should ask the admin of the server that sent that status message.
It wasn't Exchange.
My guess, if it wasn't the machine at 208.97.82.2, that it's a badly
configured secondary MX at 66.231.182.80 or 205.234.170.136.
In other word, it's probably not your problem.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.p...@getronics.com
Or to these, either: mailto:h.p...@pinkroccade.com mailto:melvin.mcp...@getronics.com mailto:melvin.mcp...@pinkroccade.com
Rich Matheisen [MVP]
[ snip ]
>My guess, if it wasn't the machine at 208.97.82.2, that it's a badly
>configured secondary MX at 66.231.182.80 or 205.234.170.136.
>
>In other word, it's probably not your problem.
Sorry . . . I meant "not your server".
If those two other IP addresses are your secondary MX then I'd take
the problem back to the owner of those machines -- or just drop the
sedondary and tertiary MX altogether, they're probably just spam
magnets.
Sanjay Mehta
I am surprised.
IP=66.231.182.35 is from dnsmadeeasy.com
And IP=205.234.170.136 is from dnsmadeeasy.com
i.e in case our server is down.
The funny thing is that if you go to DNSReport
(http://member.dnsstuff.com/pages/tools.php) and input the domain for the
report [Domain Tools]– you can see the MX records if you traverse down.
However if you go to [HostName Tools] and search specifically for MX records
for the domain – you don’t get any MX records.
Thanks
Sanjay Mehta
your reply
Rich Matheisen [MVP]
>I am surprised.
>
>IP=66.231.182.35 is from dnsmadeeasy.com
>
>
>And IP=205.234.170.136 is from dnsmadeeasy.com
>
>
>i.e in case our server is down.
Most SMTP servers will retry messages for a day or two. There are
those that give up after 30 minutes. Unless getting all you spam
without losing any, the secondary MX provides a lot of extra risk and
only little extra value.
I can't get a connection to 66.231.182.35:25, but 205.234.170.136
accepts the address okay.
The "A" record for your domain points to an email server, too:
220-casina.technosys.ca ESMTP Exim 4.66 #1 Tue, 28 Aug 2007 20:20:54
-0500
Perhaps that's the machine that rejects the address?
No matter how you slice it, you've got a pretty weird setup going
there.
