| Author | Messages | |
tkern
Posts:6
 | | 09/23/2005 7:08 AM |
| | thanks | | | |
| Alm@xxxx.yyy
| | 09/24/2005 1:03 AM |
| Exchange should be able to deliver to a literal address as
long as it is not its own. That's a valid and a common address in SMTP.
Check the logs to see what the failure is. There's a lot of
possibilities as to why it may not get to its destination.
Al
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom
KernSent: Friday, September 23, 2005 3:07 PMTo:
activedirectorySubject: [ActiveDir] exchange one more
time(ot)
If i set up a contact with the server name in the addy as in name@xxxxxxxxxxxxxxxxxxxxx, will
the message get delivered or will exchange think "servername.domain.tld " is the
domain name and throw an error?
Just a question i'm throwing out because an archive solution is giving me
that kind of contact to send mail to and its not getting there.
I have a feeling its because of that and i should just create a connector
to forward to that addy as a smarthost but i want to confirm with you guys that
i can't write an address in that form and expect exchange(or any smtp server?)
to deliver the mail.
thanks | | | |
| hcoleman
Posts:31
| | 09/24/2005 3:26 AM |
| Does "servername.domain.tld" have MX and A records in DNS?
Is this one of your servers, or does domain.tld belong to someone
else?
What happens when you try to telnet on port 25 from your
Exchange server to servername.domain.tld?
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom
KernSent: Saturday, September 24, 2005 12:12 AMTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] exchange one
more time(ot)
how does it figure out its a literal addy and not a domain? how does it
know the RHS is not a domain name and fail trying to look it up?
or does it fail and then go up the list to the other part of the
name?
I'd like to know because i can't find any exchange docs on it.
there's nothing in the app log.
i'll turn up diag logging..
mail didn't start flowing untill i changed the connector to point to a
smart host rather than dns.
until then, it just sat in the queue. the error in the queue was "remote
destatination did not respond".
Thanks
On 9/23/05, Al
Mulnick
wrote:
Exchange
should be able to deliver to a literal address as long as it is not its own.
That's a valid and a common address in SMTP.
Check the
logs to see what the failure is. There's a lot of possibilities as to why it
may not get to its destination.
Al
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom
KernSent: Friday, September 23, 2005 3:07 PMTo:
activedirectorySubject: [ActiveDir] exchange one more
time(ot)
If i set up a contact with the server name in the addy as in name@xxxxxxxxxxxxxxxxxxxxx, will the message get delivered
or will exchange think " servername.domain.tld " is the domain name and throw
an error?
Just a question i'm throwing out because an archive solution is giving me
that kind of contact to send mail to and its not getting there.
I have a feeling its because of that and i should just create a connector
to forward to that addy as a smarthost but i want to confirm with you guys
that i can't write an address in that form and expect exchange(or any smtp
server?) to deliver the mail.
thanks | | | |
| tkern
Posts:6
| | 09/24/2005 6:13 AM |
| Exchange should be able to deliver to a literal address as long as it is not its own. That's a valid and a common address in SMTP.
Check the logs to see what the failure is. There's a lot of possibilities as to why it may not get to its destination.
Al
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom KernSent: Friday, September 23, 2005 3:07 PMTo: activedirectorySubject: [ActiveDir] exchange one more time(ot)
If i set up a contact with the server name in the addy as in name@xxxxxxxxxxxxxxxxxxxxx, will the message get delivered or will exchange think "
servername.domain.tld " is the domain name and throw an error?
Just a question i'm throwing out because an archive solution is giving me that kind of contact to send mail to and its not getting there.
I have a feeling its because of that and i should just create a connector to forward to that addy as a smarthost but i want to confirm with you guys that i can't write an address in that form and expect exchange(or any smtp server?) to deliver the mail.
thanks | | | |
| listmail
Posts:490
| | 09/26/2005 9:07 AM |
| From my experience it should work fine. It doesn't have to
know if the right hand side is a domain or host IP, it simply needs to try and
look it up in DNS. I believe it will try an MX lookup and failing that, fall
back to a host record lookup.
A simple test would be to enable SMTP on some machine in
your domain, make sure there is a host record for the given name and then send a
message to it, you should see the message hit your configured drop
folder.
joe
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom
KernSent: Saturday, September 24, 2005 2:12 AMTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] exchange one
more time(ot)
how does it figure out its a literal addy and not a domain? how does it
know the RHS is not a domain name and fail trying to look it up?
or does it fail and then go up the list to the other part of the
name?
I'd like to know because i can't find any exchange docs on it.
there's nothing in the app log.
i'll turn up diag logging..
mail didn't start flowing untill i changed the connector to point to a
smart host rather than dns.
until then, it just sat in the queue. the error in the queue was "remote
destatination did not respond".
Thanks
On 9/23/05, Al
Mulnick
wrote:
Exchange
should be able to deliver to a literal address as long as it is not its own.
That's a valid and a common address in SMTP.
Check the
logs to see what the failure is. There's a lot of possibilities as to why it
may not get to its destination.
Al
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom
KernSent: Friday, September 23, 2005 3:07 PMTo:
activedirectorySubject: [ActiveDir] exchange one more
time(ot)
If i set up a contact with the server name in the addy as in name@xxxxxxxxxxxxxxxxxxxxx, will the message get delivered
or will exchange think " servername.domain.tld " is the domain name and throw
an error?
Just a question i'm throwing out because an archive solution is giving me
that kind of contact to send mail to and its not getting there.
I have a feeling its because of that and i should just create a connector
to forward to that addy as a smarthost but i want to confirm with you guys
that i can't write an address in that form and expect exchange(or any smtp
server?) to deliver the mail.
thanks | | | |
| tkern
Posts:6
| | 09/26/2005 11:34 AM |
| From my experience it should work fine. It doesn't have to know if the right hand side is a domain or host IP, it simply needs to try and look it up in DNS. I believe it will try an MX lookup and failing that, fall back to a host record lookup.
A simple test would be to enable SMTP on some machine in your domain, make sure there is a host record for the given name and then send a message to it, you should see the message hit your configured drop folder.
joe
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom KernSent: Saturday, September 24, 2005 2:12 AM
To: ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] exchange one more time(ot)
how does it figure out its a literal addy and not a domain? how does it know the RHS is not a domain name and fail trying to look it up?
or does it fail and then go up the list to the other part of the name?
I'd like to know because i can't find any exchange docs on it.
there's nothing in the app log.
i'll turn up diag logging..
mail didn't start flowing untill i changed the connector to point to a smart host rather than dns.
until then, it just sat in the queue. the error in the queue was "remote destatination did not respond".
Thanks
On 9/23/05, Al Mulnick wrote:
Exchange should be able to deliver to a literal address as long as it is not its own. That's a valid and a common address in SMTP.
Check the logs to see what the failure is. There's a lot of possibilities as to why it may not get to its destination.
Al
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom KernSent: Friday, September 23, 2005 3:07 PMTo: activedirectorySubject: [ActiveDir] exchange one more time(ot)
If i set up a contact with the server name in the addy as in name@xxxxxxxxxxxxxxxxxxxxx, will the message get delivered or will exchange think "
servername.domain.tld " is the domain name and throw an error?
Just a question i'm throwing out because an archive solution is giving me that kind of contact to send mail to and its not getting there.
I have a feeling its because of that and i should just create a connector to forward to that addy as a smarthost but i want to confirm with you guys that i can't write an address in that form and expect exchange(or any smtp server?) to deliver the mail.
thanks | | | |
| hcoleman
Posts:31
| | 09/27/2005 1:35 AM |
| Why should Exchange not think that servername.domain.tld is
a domain?
Can
you resolve servername.domain.tld from the Exchange server? How about from the
smarthost?
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx
[mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom
KernSent: Monday, September 26, 2005 5:32 PMTo:
ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re: [ActiveDir] exchange one
more time(ot)
when i had the smtp connector point to dns, it failed with "remote host did
not respond".
when pointing to a smarthost it worked.
maybe exchange while sending to myname@xxxxxxxxxxxxxxxxxxxxx,
thinks servername.domain.tld is a domain and when it gets a nxdomain from
domain.tld, it fails?
no?
sillier things have been know to occur with exchange...
thanks
On 9/26/05, joe
wrote:
From my
experience it should work fine. It doesn't have to know if the right hand side
is a domain or host IP, it simply needs to try and look it up in DNS. I
believe it will try an MX lookup and failing that, fall back to a host record
lookup.
A simple
test would be to enable SMTP on some machine in your domain, make sure there
is a host record for the given name and then send a message to it, you should
see the message hit your configured drop folder.
joe
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto: ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom
KernSent: Saturday, September 24, 2005 2:12 AM To: ActiveDir@xxxxxxxxxxxxxxxxxxSubject: Re:
[ActiveDir] exchange one more time(ot)
how does it figure out its a literal addy and not a domain? how does it
know the RHS is not a domain name and fail trying to look it up?
or does it fail and then go up the list to the other part of the
name?
I'd like to know because i can't find any exchange docs on it.
there's nothing in the app log.
i'll turn up diag logging..
mail didn't start flowing untill i changed the connector to point to a
smart host rather than dns.
until then, it just sat in the queue. the error in the queue was "remote
destatination did not respond".
Thanks
On 9/23/05, Al
Mulnick Alm@xxxxxxxxxxxxxxx >
wrote:
Exchange
should be able to deliver to a literal address as long as it is not its own.
That's a valid and a common address in SMTP.
Check
the logs to see what the failure is. There's a lot of possibilities as to
why it may not get to its destination.
Al
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:
ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom
KernSent: Friday, September 23, 2005 3:07 PMTo:
activedirectorySubject: [ActiveDir] exchange one more
time(ot)
If i set up a contact with the server name in the addy as in name@xxxxxxxxxxxxxxxxxxxxx, will the message get delivered
or will exchange think " servername.domain.tld " is the domain name and
throw an error?
Just a question i'm throwing out because an archive solution is giving
me that kind of contact to send mail to and its not getting there.
I have a feeling its because of that and i should just create a
connector to forward to that addy as a smarthost but i want to confirm with
you guys that i can't write an address in that form and expect exchange(or
any smtp server?) to deliver the mail.
thanks | | | |
| listmail
Posts:490
| | 09/27/2005 3:00 AM |
| ________________________________
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx on behalf of Coleman, Hunter
Sent: Mon 9/26/2005 9:34 PM
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] exchange one more time(ot)
Why should Exchange not think that servername.domain.tld is a domain?
Can you resolve servername.domain.tld from the Exchange server? How about from the smarthost?
________________________________
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto:ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom Kern
Sent: Monday, September 26, 2005 5:32 PM
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Subject: Re: [ActiveDir] exchange one more time(ot)
when i had the smtp connector point to dns, it failed with "remote host did not respond".
when pointing to a smarthost it worked.
maybe exchange while sending to myname@xxxxxxxxxxxxxxxxxxxxx, thinks servername.domain.tld is a domain and when it gets a nxdomain from domain.tld, it fails?
no?
sillier things have been know to occur with exchange...
thanks
On 9/26/05, joe wrote:
From my experience it should work fine. It doesn't have to know if the right hand side is a domain or host IP, it simply needs to try and look it up in DNS. I believe it will try an MX lookup and failing that, fall back to a host record lookup.
A simple test would be to enable SMTP on some machine in your domain, make sure there is a host record for the given name and then send a message to it, you should see the message hit your configured drop folder.
joe
________________________________
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto: ActiveDir-owner@xxxxxxxxxxxxxxxxxx] On Behalf Of Tom Kern
Sent: Saturday, September 24, 2005 2:12 AM
To: ActiveDir@xxxxxxxxxxxxxxxxxx
Subject: Re: [ActiveDir] exchange one more time(ot)
how does it figure out its a literal addy and not a domain? how does it know the RHS is not a domain name and fail trying to look it up?
or does it fail and then go up the list to the other part of the name?
I'd like to know because i can't find any exchange docs on it.
there's nothing in the app log.
i'll turn up diag logging..
mail didn't start flowing untill i changed the connector to point to a smart host rather than dns.
until then, it just sat in the queue. the error in the queue was "remote destatination did not respond".
Thanks
On 9/23/05, Al Mulnick wrote:
Exchange should be able to deliver to a literal address as long as it is not its own. That's a valid and a common address in SMTP.
Check the logs to see what the failure is. There's a lot of possibilities as to why it may not get to its destination.
Al
________________________________
From: ActiveDir-owner@xxxxxxxxxxxxxxxxxx [mailto: ActiveDir-owner@xxxxxxxxxxxxxxxxxx ] On Behalf Of Tom Kern
Sent: Friday, September 23, 2005 3:07 PM
To: activedirectory
Subject: [ActiveDir] exchange one more time(ot)
If i set up a contact with the server name in the addy as in name@xxxxxxxxxxxxxxxxxxxxx, will the message get delivered or will exchange think " servername.domain.tld " is the domain name and throw an error?
Just a question i'm throwing out because an archive solution is giving me that kind of contact to send mail to and its not getting there.
I have a feeling its because of that and i should just create a connector to forward to that addy as a smarthost but i want to confirm with you guys that i can't write an address in that form and expect exchange(or any smtp server?) to deliver the mail.
thanks
> | | | |
|
|