Anyone familiar with Server 2003 SBS Pro Exchange Server?
I have a client who insists on using this AND our POP mail. His server is not and Internet Domain, and it sends mail out marked as sender@windowsdomainname.local.
We went way the hell up there and set up the POP Connector so it GETS mail from our server, and as it logs in to get mail first, it sends mail to domains on our POP server. It doesn’t actually RELAY as there’s nothing in the mail.log showing to other domains, so the damn thing is not relaying thru POP just sending mail to our POP from .local
He wants it to send local mail to .local and external mail through POP as sender@internetdomainname.com and access everyone’s calendars.
I know jack shit about Exchange, and it’s not an ISPs job to set your fucking local network up for you.
Ideas?
Normally you would set an AD user with an SMTP address with the desired outbound address. For example, if the internal domain in wanker.local, then internal addresses will take the form of user@realdomain.com, and then set it as primary. The primary will appear on the outbound. Having the internal domain not the same as the external domain is correct behavior and setup by the way (hard to convince linux folks of this for some reason, haha). You can do bulk changes using ADModify.
But, if you are bouncing out, and you’ve configured the POP connector for exchange, you need to make sure the POP server is going to permit the relay (typically you would restrict it by at least two criteria, either IP/reverse lookup and an TLS/SSL login).
I know how customers can be though, spend the time and convince them to get their own domain. There is a reason why people like exchange so much (its easily the most slick collaboration platforms out there for Outlook Addicts and the reason why everyone wants to emulate or connect to it). Once you commit them to getting their own domain, put something infront of the exchange server though (ISA firewall, linux or BSD PF, etc). Sell it to them from a mobility standpoint (OWA, Activesync for Mobile, etc) and they’ll be all over it.
Cheers,
Tim (<-- Exchange dude since 5.5)
ADmodify is that part of SBS/Exchange or a 3rd party add-on?
I didn’t setup the server, but helped the guy who did find the POP connector. Didn’t notice any SMTP settings and when I left I couldn’t figure out how/why the thing could send without any…
(No reason other than user’s stubborn refusal that mail.actualdomain.com couldn’t be set on this thing instead of my offsite server, its behind a Cisco router/firewall and connected to an 10/10 Mb circuit.)
Remember that since Exchange 2000, there is only a single directory (Active Directory), so all objects are stored there, including users. It’s developed by MS so is not third party per se, think more like a powertoy!
Not sure if this board supports links, but try this:
technet.microsoft.com/en-us/libr … 6(EXCHG.65.aspx
If the link doesn’t show in the post, google for “technet introduction to admodify.net”
For a one off change, crack open a user account, there should be an exchange tab on the user, and withing there you should have an option to specify addresses. There will probably be some legacy x.400 address, and at least the .local smtp address. You have to create a new one before you can delete the .local, and you should not delete the .local anyways, just set the proper SMTP as primary.
The cisco firewall is very good, but I was thinking more of threat management protection (spam, ndr injection attacks, etc). There are third party exchange protections, but they are all pricey. There are some very good open source threat management tools for this (Maia mailguard, mailscanner, etc). Some of them can even be configured as a smarthost directly in exchange which is super slick.
Cheers,
thx tj
[quote=“herbie_popnecker”]ADmodify is that part of SBS/Exchange or a 3rd party add-on?
I didn’t setup the server, but helped the guy who did find the POP connector. Didn’t notice any SMTP settings and when I left I couldn’t figure out how/why the thing could send without any…
(No reason other than user’s stubborn refusal that mail.actualdomain.com couldn’t be set on this thing instead of my offsite server, its behind a Cisco router/firewall and connected to an 10/10 Mb circuit.)[/quote]
Several days ago I heard about one tool. Which I have downloaded from the Inet. It astonished me solved my old troubles for minutes. Moreover it may help in such proposition - exchange server 2007 recovery.