Exchange server malarkey

[motorollin]

Another overly elaborate and complex problem :-D

The Exchange server at uni (lets call it exchange.xxx.ac.uk is not accessible from outside the uni intranet. But the university provides Outlook Web Access on the web server owa.xxx.ac.uk. I wanted to configure a mail client on my home computer to connect to the Exchange server instead of using Outlook Web Access (which is horrible). I made an assumption that owa.xxx.ac.uk was an alias to a web server running on the Exchange server itself, and I was right: if I configured my mail client with the Exchange server address "owa.xxx.ac.uk" it worked. I could see all my Exchange folders, read emails, move them around, delete them etc.

The problem comes with sending. owa.xxx.ac.uk does not work as an outgoing mail server, so I had to use my ISP's SMTP server for sending. Of course, my ISP's SMTP server doesn't know how to resolve exchange.xxx.ac.uk, so if I want to send an email to somebody@exchange.xxx.ac.uk, it bounces saying it can't resolve the host.

Short of convincing the university to expose the exchange.xxx.ac.uk to the Internet, is there any way around this? Maybe a local SMTP server which has exchange.xxx.ac.uk in its hosts list so that it can be resolved to the IP address of owa.xxx.ac.uk. I don't actually know if this would work though, since although owa.xxx.ac.uk seems to allow access to the user's mailbox, I don't know whether it is running an inbound mail service.

:crazy: :crazy: :crazy: :crazy: :crazy:

[bloodline]

I deeply suspect with the upcoming iPhone 3G... I'm going to need whatever help this thread offers...

[motorollin]

Indeed :-) I have had some additional thoughts about this. It would be absurd if the Exchange server did not allow messages to be sent from outside the university network. That would mean people could only receive emails from other people with accounts on the Exchange server, not from outside. That can't be the case.

I think the problem is that existing messages in the mailbox are being viewed by a user who is logged on to the Exchange server (IOW I am viewing the mailbox on the server). That means the sender address it shows me is the Exchange address, not the SMTP address. If I could get it to display the SMTP address instead of the Exchange address, then it might reply to that address (which must be accessible from outside the university network)

[bloodline]

motorollin wrote:
Indeed :-) I have had some additional thoughts about this. It would be absurd if the Exchange server did not allow messages to be sent from outside the university network. That would mean people could only receive emails from other people with accounts on the Exchange server, not from outside. That can't be the case.

I think the problem is that existing messages in the mailbox are being viewed by a user who is logged on to the Exchange server (IOW I am viewing the mailbox on the server). That means the sender address it shows me is the Exchange address, not the SMTP address. If I could get it to display the SMTP address instead of the Exchange address, then it might reply to that address (which must be accessible from outside the university network)

If you just need an SMTP server, then use mine...  :-?

[motorollin]

I have an SMTP server provided by my ISP, but the problem is that it doesn't know how to resolve exchange.xxx.ac.uk (because it is not published in public DNS servers). The idea behind running a local one is that I can force it to resolve exchange.xxx.ac.uk using a hosts file. The alternative is to try to get the mailbox to show the sender's external (SMTP) email address instead of the internal (Exchange) address, which should be resolveable by public DNS servers.

[bloodline]

Holy Poop!!! I just popped the exchange webmail address into the exchange server field of entourage... and it's bloody working!?!?! I've never bothered before... I can't wait for my iPhone 3G!!! :-)

[motorollin]

But you won't be able to send...

[bloodline]

motorollin wrote:
But you won't be able to send...

I'm still not 100% sure why you specifically want to use Exchange to send... But I'll look into this later, myself and see what happens :-)

[motorollin]

I can't use SMTP to send because the reply address provided by the Exchange server is an address which is only valid within the Exchange. It doesn't work if you send from outside (i.e. through SMTP) So I either need to send through the Exchange server, or send to an SMTP server which has a host entry to allow it to resolve the address of the Exchange server.

[bloodline]

motorollin wrote:
I can't use SMTP to send because the reply address provided by the Exchange server is an address which is only valid within the Exchange. It doesn't work if you send from outside (i.e. through SMTP) So I either need to send through the Exchange server, or send to an SMTP server which has a host entry to allow it to resolve the address of the Exchange server.

I see...

[bloodline]

Unfortunately the send and global address list features work fine on my Exchange server... so I guess your uni exchange server is playing nasty :-(

[adolescent]

@Moto

It's quite possible, and normal, for the SMTP gateway to be seperate from the OWA.  And, in fact you're probably hitting a front end server not the actual Exchange server itself.  (Putting an Exchange server, or any private mail store on the internet is asking for trouble...)

Two easy options.  Ask your network administrator for the SMTP server address, or send yourself an email from inside and you may be able to discover the gateway name by inspecting the mail headers (provided they use the same SMTP gateway for incoming and outgoing messages).

[motorollin]

adolescent wrote:
It's quite possible, and normal, for the SMTP gateway to be seperate from the OWA.  And, in fact you're probably hitting a front end server not the actual Exchange server itself.

Ahh, so the OWA server is a separate box which acts as a gateway to the Exchange, right?

adolescent wrote:
Two easy options.  Ask your network administrator for the SMTP server address, or send yourself an email from inside and you may be able to discover the gateway name by inspecting the mail headers (provided they use the same SMTP gateway for incoming and outgoing messages).

Just tried it. There are quite a lot of "Received:" lines in the headers, presumably where the message is getting passed from one server to the next. The first ones in the chain resolve to 10.x.y.z addresses so are only accessible from inside. The last server before it gets to my ISP is mailcluster.xxx.ac.uk, which resolves to 193.x.y.z. AFAIK this is a public IP address, so I tried to telnet in on port 25 to see if there's an SMTP service running, but it timed out.

--
moto

[motorollin]

Ok, I sent a message *to* my Uni account and examined the headers of the message which was delivered, and found some different servers. One of them, lets call it server1.xxx.ac.uk, is running an SMTP server which is accessible from outside. I can Telnet in to it:

$ telnet server1.xxx.ac.uk 25
Trying xxx.xxx.xxx.xxx...
Connected to server1.xxx.ac.uk.
Escape character is '^]'.
220 server1.xxx.ac.uk ESMTP ready; send us your mail, but not your spam.
HELO
250 server1.xxx.ac.uk Hi [xxx.xxx.xxx.xxx] [xxx.xxx.xxx.xxx]; I am so happy to meet you.


But when I configure it as the outbound server in my mail client, I can't send messages through the server and it asks me to verify the settings. If I use the "Connection Doctor", it checks it and says "Connection to server succeeded, no login required".

:-?

[bloodline]

/Me watching thread with interest... and trying to mirror Moto's actions with my work exchange server...