exchange 2003 routing problem

Hello there,

I hope this time it's the right forum for my question.

I am having problems configuring a MS Exchange Server 2003. The server is
located in our LAN. The mail addresses first go to a public server which is
forwarding them to a router with a static IP. This router is the entrance to
our LAN. It should forward all messages to another router in our LAN which
then should process the messages to the Exchange server.
For example:
I have a mail address like (E-Mail Removed). All messages to
mylocalnet.com are forwarded from the public server to the router with port
25000.
The router forwards them to a second router with port 25000.
This router forwards them to the Exchange server. Port 25 or 25000?

I dont know where exactly is the mistake, but the Exchange server does not
receive any messages. So I dont know to which port I have to send the
messages from the second router. I tried various.

I can send messages from the Exchange server without problems. Just
receiving them does not work.

Any ideas are appreciated?

Greetings,
Ralf

ralf <(E-Mail Removed)> wrote:
> Hello there,
>
> I hope this time it's the right forum for my question.

Actually, no.....microsoft.public.exchange.connectivity might be better.
>
> I am having problems configuring a MS Exchange Server 2003. The
> server is located in our LAN. The mail addresses first go to a public
> server which is forwarding them to a router with a static IP. This
> router is the entrance to our LAN. It should forward all messages to
> another router in our LAN which then should process the messages to
> the Exchange server.

What's the reason for all these hops?

> For example:
> I have a mail address like (E-Mail Removed). All messages to
> mylocalnet.com are forwarded from the public server to the router
> with port 25000.

Why a nonstandard port, out of curiosity?

>
> The router forwards them to a second router with port 25000.
> This router forwards them to the Exchange server. Port 25 or 25000?

I don't know; I can't see your server from here. But unless you changed your
virtual SMTP server's listening port to 25000, it's 25, and it sounds like
you want to change that.
>
> I dont know where exactly is the mistake, but the Exchange server
> does not receive any messages. So I dont know to which port I have to
> send the messages from the second router. I tried various.

Elsewhere on your LAN, can you telnet to your Exchange server on port 25000?
>
> I can send messages from the Exchange server without problems. Just
> receiving them does not work.
>
> Any ideas are appreciated?
>
> Greetings,
> Ralf

It might help if you could include a simple diagram (in text).

Hi,

The diagram may look like this:

-server in internet: www.mydomain.com
-this server has a subdomain: exchange.mydomain.com
-this server shell forward all mails going to (E-Mail Removed) to
our router with the static IP 1.2.3.4 and port 25000
-then comes our router 1.2.3.4
-this (3COM) router shell forward everything coming to port 25000 to the
internal Win 2003 server 192.168.0.1
-then comes the server 192.168.0.1 which shell forward all the mails to the
Exchange server 192.168.0.2

Hope this makes it a bit clearer.
It's a bit complicated, but I dont see any other posibility.
I thought a non standard port would be better for security reason.
The Exchange server is listening on the standard port. There I didnt change
anything.
The telnet thing I havent tried yet. I will tomorrow.
One problem is that I dont know where the messages get lost. Is there a way
to see if the messages reach the router 1.2.3.4?

Regards,
Ralf


"Lanwench [MVP - Exchange]" wrote:

> ralf <(E-Mail Removed)> wrote:
> > Hello there,
> >
> > I hope this time it's the right forum for my question.
>
> Actually, no.....microsoft.public.exchange.connectivity might be better.
> >
> > I am having problems configuring a MS Exchange Server 2003. The
> > server is located in our LAN. The mail addresses first go to a public
> > server which is forwarding them to a router with a static IP. This
> > router is the entrance to our LAN. It should forward all messages to
> > another router in our LAN which then should process the messages to
> > the Exchange server.
>
> What's the reason for all these hops?
>
> > For example:
> > I have a mail address like (E-Mail Removed). All messages to
> > mylocalnet.com are forwarded from the public server to the router
> > with port 25000.
>
> Why a nonstandard port, out of curiosity?
>
> >
> > The router forwards them to a second router with port 25000.
> > This router forwards them to the Exchange server. Port 25 or 25000?
>
> I don't know; I can't see your server from here. But unless you changed your
> virtual SMTP server's listening port to 25000, it's 25, and it sounds like
> you want to change that.
> >
> > I dont know where exactly is the mistake, but the Exchange server
> > does not receive any messages. So I dont know to which port I have to
> > send the messages from the second router. I tried various.
>
> Elsewhere on your LAN, can you telnet to your Exchange server on port 25000?
> >
> > I can send messages from the Exchange server without problems. Just
> > receiving them does not work.
> >
> > Any ideas are appreciated?
> >
> > Greetings,
> > Ralf
>
> It might help if you could include a simple diagram (in text).
>
>
>

ralf <(E-Mail Removed)> wrote:
> Hi,
>
> The diagram may look like this:
>
> -server in internet: www.mydomain.com

What kind of server?

> -this server has a subdomain: exchange.mydomain.com
> -this server shell forward all mails going to
> (E-Mail Removed) to our router with the static IP 1.2.3.4
> and port 25000

What does the server *run* that it's doing this forwarding, and how?

> -then comes our router 1.2.3.4
> -this (3COM) router shell forward everything coming to port 25000 to
> the internal Win 2003 server 192.168.0.1
> -then comes the server 192.168.0.1 which shell forward all the mails
> to the Exchange server 192.168.0.2
>
> Hope this makes it a bit clearer.
> It's a bit complicated, but I dont see any other posibility.

It's difficult for me to see how to make it more complicated - and I'm still
not sure what the reasoning is.

> I thought a non standard port would be better for security reason.

No, not really - but that still doesn't explain why you aren't going
straight from your first router directly to your Exchange server. I'm not
sure what you mean by "forward the mails" anyway - what exactly is doing
that? Port forwarding is one thing; mail forwarding requires a mail server &
is quite different.

> The Exchange server is listening on the standard port. There I didnt
> change anything.

> The telnet thing I havent tried yet. I will tomorrow.

Yes, I would. I'd also simplify it considerably.
> One problem is that I dont know where the messages get lost. Is there
> a way to see if the messages reach the router 1.2.3.4?

Only if your router logs these connections, I'd imagine.

>
> Regards,
> Ralf
>
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> ralf <(E-Mail Removed)> wrote:
>>> Hello there,
>>>
>>> I hope this time it's the right forum for my question.
>>
>> Actually, no.....microsoft.public.exchange.connectivity might be
>> better.
>>>
>>> I am having problems configuring a MS Exchange Server 2003. The
>>> server is located in our LAN. The mail addresses first go to a
>>> public server which is forwarding them to a router with a static
>>> IP. This router is the entrance to our LAN. It should forward all
>>> messages to another router in our LAN which then should process the
>>> messages to the Exchange server.
>>
>> What's the reason for all these hops?
>>
>>> For example:
>>> I have a mail address like (E-Mail Removed). All messages to
>>> mylocalnet.com are forwarded from the public server to the router
>>> with port 25000.
>>
>> Why a nonstandard port, out of curiosity?
>>
>>>
>>> The router forwards them to a second router with port 25000.
>>> This router forwards them to the Exchange server. Port 25 or 25000?
>>
>> I don't know; I can't see your server from here. But unless you
>> changed your virtual SMTP server's listening port to 25000, it's 25,
>> and it sounds like you want to change that.
>>>
>>> I dont know where exactly is the mistake, but the Exchange server
>>> does not receive any messages. So I dont know to which port I have
>>> to send the messages from the second router. I tried various.
>>
>> Elsewhere on your LAN, can you telnet to your Exchange server on
>> port 25000?
>>>
>>> I can send messages from the Exchange server without problems. Just
>>> receiving them does not work.
>>>
>>> Any ideas are appreciated?
>>>
>>> Greetings,
>>> Ralf
>>
>> It might help if you could include a simple diagram (in text).

The server in the internet has cPanel installed. It's the server where our
website is hosted and our "normal" mail client is installed.
There I can create subdomains of our website domain.
And they allow me to set up a mail domain forwarding. What I understand as
that they forward all mail sent to the new subdomain to another server.
In this case to our router on port 25000.

The Exchange server is located in our LAN as it cannot be installed on that
internet server.

I just changed the ports to 25, but it still is not working.

I cannot reach the Exchange via Telnet.

Thanx for your help!
Ralf


"Lanwench [MVP - Exchange]" wrote:

> ralf <(E-Mail Removed)> wrote:
> > Hi,
> >
> > The diagram may look like this:
> >
> > -server in internet: www.mydomain.com
>
> What kind of server?
>
> > -this server has a subdomain: exchange.mydomain.com
> > -this server shell forward all mails going to
> > (E-Mail Removed) to our router with the static IP 1.2.3.4
> > and port 25000
>
> What does the server *run* that it's doing this forwarding, and how?
>
> > -then comes our router 1.2.3.4
> > -this (3COM) router shell forward everything coming to port 25000 to
> > the internal Win 2003 server 192.168.0.1
> > -then comes the server 192.168.0.1 which shell forward all the mails
> > to the Exchange server 192.168.0.2
> >
> > Hope this makes it a bit clearer.
> > It's a bit complicated, but I dont see any other posibility.
>
> It's difficult for me to see how to make it more complicated - and I'm still
> not sure what the reasoning is.
>
> > I thought a non standard port would be better for security reason.
>
> No, not really - but that still doesn't explain why you aren't going
> straight from your first router directly to your Exchange server. I'm not
> sure what you mean by "forward the mails" anyway - what exactly is doing
> that? Port forwarding is one thing; mail forwarding requires a mail server &
> is quite different.
>
> > The Exchange server is listening on the standard port. There I didnt
> > change anything.
>
> > The telnet thing I havent tried yet. I will tomorrow.
>
> Yes, I would. I'd also simplify it considerably.
> > One problem is that I dont know where the messages get lost. Is there
> > a way to see if the messages reach the router 1.2.3.4?
>
> Only if your router logs these connections, I'd imagine.
>
> >
> > Regards,
> > Ralf
> >
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> ralf <(E-Mail Removed)> wrote:
> >>> Hello there,
> >>>
> >>> I hope this time it's the right forum for my question.
> >>
> >> Actually, no.....microsoft.public.exchange.connectivity might be
> >> better.
> >>>
> >>> I am having problems configuring a MS Exchange Server 2003. The
> >>> server is located in our LAN. The mail addresses first go to a
> >>> public server which is forwarding them to a router with a static
> >>> IP. This router is the entrance to our LAN. It should forward all
> >>> messages to another router in our LAN which then should process the
> >>> messages to the Exchange server.
> >>
> >> What's the reason for all these hops?
> >>
> >>> For example:
> >>> I have a mail address like (E-Mail Removed). All messages to
> >>> mylocalnet.com are forwarded from the public server to the router
> >>> with port 25000.
> >>
> >> Why a nonstandard port, out of curiosity?
> >>
> >>>
> >>> The router forwards them to a second router with port 25000.
> >>> This router forwards them to the Exchange server. Port 25 or 25000?
> >>
> >> I don't know; I can't see your server from here. But unless you
> >> changed your virtual SMTP server's listening port to 25000, it's 25,
> >> and it sounds like you want to change that.
> >>>
> >>> I dont know where exactly is the mistake, but the Exchange server
> >>> does not receive any messages. So I dont know to which port I have
> >>> to send the messages from the second router. I tried various.
> >>
> >> Elsewhere on your LAN, can you telnet to your Exchange server on
> >> port 25000?
> >>>
> >>> I can send messages from the Exchange server without problems. Just
> >>> receiving them does not work.
> >>>
> >>> Any ideas are appreciated?
> >>>
> >>> Greetings,
> >>> Ralf
> >>
> >> It might help if you could include a simple diagram (in text).
>
>
>
>

The Exchange server is now reachable via Telnet.


"Lanwench [MVP - Exchange]" wrote:

> ralf <(E-Mail Removed)> wrote:
> > Hi,
> >
> > The diagram may look like this:
> >
> > -server in internet: www.mydomain.com
>
> What kind of server?
>
> > -this server has a subdomain: exchange.mydomain.com
> > -this server shell forward all mails going to
> > (E-Mail Removed) to our router with the static IP 1.2.3.4
> > and port 25000
>
> What does the server *run* that it's doing this forwarding, and how?
>
> > -then comes our router 1.2.3.4
> > -this (3COM) router shell forward everything coming to port 25000 to
> > the internal Win 2003 server 192.168.0.1
> > -then comes the server 192.168.0.1 which shell forward all the mails
> > to the Exchange server 192.168.0.2
> >
> > Hope this makes it a bit clearer.
> > It's a bit complicated, but I dont see any other posibility.
>
> It's difficult for me to see how to make it more complicated - and I'm still
> not sure what the reasoning is.
>
> > I thought a non standard port would be better for security reason.
>
> No, not really - but that still doesn't explain why you aren't going
> straight from your first router directly to your Exchange server. I'm not
> sure what you mean by "forward the mails" anyway - what exactly is doing
> that? Port forwarding is one thing; mail forwarding requires a mail server &
> is quite different.
>
> > The Exchange server is listening on the standard port. There I didnt
> > change anything.
>
> > The telnet thing I havent tried yet. I will tomorrow.
>
> Yes, I would. I'd also simplify it considerably.
> > One problem is that I dont know where the messages get lost. Is there
> > a way to see if the messages reach the router 1.2.3.4?
>
> Only if your router logs these connections, I'd imagine.
>
> >
> > Regards,
> > Ralf
> >
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> ralf <(E-Mail Removed)> wrote:
> >>> Hello there,
> >>>
> >>> I hope this time it's the right forum for my question.
> >>
> >> Actually, no.....microsoft.public.exchange.connectivity might be
> >> better.
> >>>
> >>> I am having problems configuring a MS Exchange Server 2003. The
> >>> server is located in our LAN. The mail addresses first go to a
> >>> public server which is forwarding them to a router with a static
> >>> IP. This router is the entrance to our LAN. It should forward all
> >>> messages to another router in our LAN which then should process the
> >>> messages to the Exchange server.
> >>
> >> What's the reason for all these hops?
> >>
> >>> For example:
> >>> I have a mail address like (E-Mail Removed). All messages to
> >>> mylocalnet.com are forwarded from the public server to the router
> >>> with port 25000.
> >>
> >> Why a nonstandard port, out of curiosity?
> >>
> >>>
> >>> The router forwards them to a second router with port 25000.
> >>> This router forwards them to the Exchange server. Port 25 or 25000?
> >>
> >> I don't know; I can't see your server from here. But unless you
> >> changed your virtual SMTP server's listening port to 25000, it's 25,
> >> and it sounds like you want to change that.
> >>>
> >>> I dont know where exactly is the mistake, but the Exchange server
> >>> does not receive any messages. So I dont know to which port I have
> >>> to send the messages from the second router. I tried various.
> >>
> >> Elsewhere on your LAN, can you telnet to your Exchange server on
> >> port 25000?
> >>>
> >>> I can send messages from the Exchange server without problems. Just
> >>> receiving them does not work.
> >>>
> >>> Any ideas are appreciated?
> >>>
> >>> Greetings,
> >>> Ralf
> >>
> >> It might help if you could include a simple diagram (in text).
>
>
>
>

From inside on port 25.
And from outside our network I can reach it when I connect to the IP of our
router and port 25000.


"ralf" wrote:

> The Exchange server is now reachable via Telnet.
>
>
> "Lanwench [MVP - Exchange]" wrote:
>
> > ralf <(E-Mail Removed)> wrote:
> > > Hi,
> > >
> > > The diagram may look like this:
> > >
> > > -server in internet: www.mydomain.com
> >
> > What kind of server?
> >
> > > -this server has a subdomain: exchange.mydomain.com
> > > -this server shell forward all mails going to
> > > (E-Mail Removed) to our router with the static IP 1.2.3.4
> > > and port 25000
> >
> > What does the server *run* that it's doing this forwarding, and how?
> >
> > > -then comes our router 1.2.3.4
> > > -this (3COM) router shell forward everything coming to port 25000 to
> > > the internal Win 2003 server 192.168.0.1
> > > -then comes the server 192.168.0.1 which shell forward all the mails
> > > to the Exchange server 192.168.0.2
> > >
> > > Hope this makes it a bit clearer.
> > > It's a bit complicated, but I dont see any other posibility.
> >
> > It's difficult for me to see how to make it more complicated - and I'm still
> > not sure what the reasoning is.
> >
> > > I thought a non standard port would be better for security reason.
> >
> > No, not really - but that still doesn't explain why you aren't going
> > straight from your first router directly to your Exchange server. I'm not
> > sure what you mean by "forward the mails" anyway - what exactly is doing
> > that? Port forwarding is one thing; mail forwarding requires a mail server &
> > is quite different.
> >
> > > The Exchange server is listening on the standard port. There I didnt
> > > change anything.
> >
> > > The telnet thing I havent tried yet. I will tomorrow.
> >
> > Yes, I would. I'd also simplify it considerably.
> > > One problem is that I dont know where the messages get lost. Is there
> > > a way to see if the messages reach the router 1.2.3.4?
> >
> > Only if your router logs these connections, I'd imagine.
> >
> > >
> > > Regards,
> > > Ralf
> > >
> > >
> > > "Lanwench [MVP - Exchange]" wrote:
> > >
> > >> ralf <(E-Mail Removed)> wrote:
> > >>> Hello there,
> > >>>
> > >>> I hope this time it's the right forum for my question.
> > >>
> > >> Actually, no.....microsoft.public.exchange.connectivity might be
> > >> better.
> > >>>
> > >>> I am having problems configuring a MS Exchange Server 2003. The
> > >>> server is located in our LAN. The mail addresses first go to a
> > >>> public server which is forwarding them to a router with a static
> > >>> IP. This router is the entrance to our LAN. It should forward all
> > >>> messages to another router in our LAN which then should process the
> > >>> messages to the Exchange server.
> > >>
> > >> What's the reason for all these hops?
> > >>
> > >>> For example:
> > >>> I have a mail address like (E-Mail Removed). All messages to
> > >>> mylocalnet.com are forwarded from the public server to the router
> > >>> with port 25000.
> > >>
> > >> Why a nonstandard port, out of curiosity?
> > >>
> > >>>
> > >>> The router forwards them to a second router with port 25000.
> > >>> This router forwards them to the Exchange server. Port 25 or 25000?
> > >>
> > >> I don't know; I can't see your server from here. But unless you
> > >> changed your virtual SMTP server's listening port to 25000, it's 25,
> > >> and it sounds like you want to change that.
> > >>>
> > >>> I dont know where exactly is the mistake, but the Exchange server
> > >>> does not receive any messages. So I dont know to which port I have
> > >>> to send the messages from the second router. I tried various.
> > >>
> > >> Elsewhere on your LAN, can you telnet to your Exchange server on
> > >> port 25000?
> > >>>
> > >>> I can send messages from the Exchange server without problems. Just
> > >>> receiving them does not work.
> > >>>
> > >>> Any ideas are appreciated?
> > >>>
> > >>> Greetings,
> > >>> Ralf
> > >>
> > >> It might help if you could include a simple diagram (in text).
> >
> >
> >
> >

Hi,

first I have to say that I really don´t understand why you are doing it so
complicated?!
Anyway...
> The diagram may look like this:
>
> -server in internet: www.mydomain.com
> -this server has a subdomain: exchange.mydomain.com
> -this server shell forward all mails going to (E-Mail Removed) to
> our router with the static IP 1.2.3.4 and port 25000
> -then comes our router 1.2.3.4
Ok, so far so good.

> -this (3COM) router shell forward everything coming to port 25000 to the
> internal Win 2003 server 192.168.0.1
> -then comes the server 192.168.0.1 which shell forward all the mails to the
> Exchange server 192.168.0.2
Sorry, why this hop? It would make sense to foward it to a DMZ. But you are
routing inside the LAN->inside the LAN?
How is server 192.168.0.1 doing this forward???

> It's a bit complicated, but I dont see any other posibility.
Why not??

> I thought a non standard port would be better for security reason.
No it isn´t.

> One problem is that I dont know where the messages get lost. Is there a way
> to see if the messages reach the router 1.2.3.4?
The router should have a log.

Regards,
Tanja

ralf <(E-Mail Removed)> wrote:
> From inside on port 25.
> And from outside our network I can reach it when I connect to the IP
> of our router and port 25000.

That's fine, and is a good start, but you've still got a convoluted
configuration and I'm not sure why (or how you can fix it). This
"forwarding" doesn't make any sense to me, especially the stuff *inside*
your network.

You've got your own Exchange server - host your own mail. Even if you want
to prevent outside connections from coming in, you can put a server in a DMZ
(Postfix, etc) and have it set up to receive all your domain's mail via
SMTP - then have it directly relay that mail to your Exchange server in the
LAN. Or just have it come in directly! There is no point in changing the
listening ports - it is not adding any real security, and is creating
confusion.

I'd check out http://www.msexchange.org/tutorials/MF002.html and post a new
message (not identical to the original or this one - rewrite it!) in
microsoft.public.exchange.connectivity as suggested previously.



>
>
> "ralf" wrote:
>
>> The Exchange server is now reachable via Telnet.
>>
>>
>> "Lanwench [MVP - Exchange]" wrote:
>>
>>> ralf <(E-Mail Removed)> wrote:
>>>> Hi,
>>>>
>>>> The diagram may look like this:
>>>>
>>>> -server in internet: www.mydomain.com
>>>
>>> What kind of server?
>>>
>>>> -this server has a subdomain: exchange.mydomain.com
>>>> -this server shell forward all mails going to
>>>> (E-Mail Removed) to our router with the static IP 1.2.3.4
>>>> and port 25000
>>>
>>> What does the server *run* that it's doing this forwarding, and how?
>>>
>>>> -then comes our router 1.2.3.4
>>>> -this (3COM) router shell forward everything coming to port 25000
>>>> to the internal Win 2003 server 192.168.0.1
>>>> -then comes the server 192.168.0.1 which shell forward all the
>>>> mails to the Exchange server 192.168.0.2
>>>>
>>>> Hope this makes it a bit clearer.
>>>> It's a bit complicated, but I dont see any other posibility.
>>>
>>> It's difficult for me to see how to make it more complicated - and
>>> I'm still not sure what the reasoning is.
>>>
>>>> I thought a non standard port would be better for security reason.
>>>
>>> No, not really - but that still doesn't explain why you aren't going
>>> straight from your first router directly to your Exchange server.
>>> I'm not sure what you mean by "forward the mails" anyway - what
>>> exactly is doing that? Port forwarding is one thing; mail
>>> forwarding requires a mail server & is quite different.
>>>
>>>> The Exchange server is listening on the standard port. There I
>>>> didnt change anything.
>>>
>>>> The telnet thing I havent tried yet. I will tomorrow.
>>>
>>> Yes, I would. I'd also simplify it considerably.
>>>> One problem is that I dont know where the messages get lost. Is
>>>> there a way to see if the messages reach the router 1.2.3.4?
>>>
>>> Only if your router logs these connections, I'd imagine.
>>>
>>>>
>>>> Regards,
>>>> Ralf
>>>>
>>>>
>>>> "Lanwench [MVP - Exchange]" wrote:
>>>>
>>>>> ralf <(E-Mail Removed)> wrote:
>>>>>> Hello there,
>>>>>>
>>>>>> I hope this time it's the right forum for my question.
>>>>>
>>>>> Actually, no.....microsoft.public.exchange.connectivity might be
>>>>> better.
>>>>>>
>>>>>> I am having problems configuring a MS Exchange Server 2003. The
>>>>>> server is located in our LAN. The mail addresses first go to a
>>>>>> public server which is forwarding them to a router with a static
>>>>>> IP. This router is the entrance to our LAN. It should forward all
>>>>>> messages to another router in our LAN which then should process
>>>>>> the messages to the Exchange server.
>>>>>
>>>>> What's the reason for all these hops?
>>>>>
>>>>>> For example:
>>>>>> I have a mail address like (E-Mail Removed). All messages to
>>>>>> mylocalnet.com are forwarded from the public server to the router
>>>>>> with port 25000.
>>>>>
>>>>> Why a nonstandard port, out of curiosity?
>>>>>
>>>>>>
>>>>>> The router forwards them to a second router with port 25000.
>>>>>> This router forwards them to the Exchange server. Port 25 or
>>>>>> 25000?
>>>>>
>>>>> I don't know; I can't see your server from here. But unless you
>>>>> changed your virtual SMTP server's listening port to 25000, it's
>>>>> 25, and it sounds like you want to change that.
>>>>>>
>>>>>> I dont know where exactly is the mistake, but the Exchange server
>>>>>> does not receive any messages. So I dont know to which port I
>>>>>> have to send the messages from the second router. I tried
>>>>>> various.
>>>>>
>>>>> Elsewhere on your LAN, can you telnet to your Exchange server on
>>>>> port 25000?
>>>>>>
>>>>>> I can send messages from the Exchange server without problems.
>>>>>> Just receiving them does not work.
>>>>>>
>>>>>> Any ideas are appreciated?
>>>>>>
>>>>>> Greetings,
>>>>>> Ralf
>>>>>
>>>>> It might help if you could include a simple diagram (in text).