I have a user who is having few *.DBX files. I need to move these DBX files onto another system and point Outlook Express on this system to read these DBX files so that the user can see his emails from this new system. Outlook Express has few wizards to import and export messages, but all these require some means of other client ( ex: Outlook, other POP3 Client etc ) to do this job.
Recommended resources; MS KB document Q262118 and http://www.slipstick.com/outlook/olexpr.htm .
How do we allow a user to OWA without giving him administrative rights?
Grant "Log on Locally" rights to all that you want to have access to OWA.
Does IIS use port 80 when running OWA or something else?
By default IIS uses port 80 (assuming you're not using SSL) but you can change that to any port you want. (Recommended avoiding any of the ports already listed in your services file). Make sure that in the redirect, or port redirection, or whatever method you use to locate it, you add ":" to your URL (as in :8080 if you set it up for port 8080)
Is it possible to have Exchange to connect to an LDAP server and perform a DIRSYNC? I need to pull in names from a remote system that uses LDAP. I want these names to appear to my users in our GAL. Is this possible with Remote DIRSYNC connector?
Compaq offer a utility called LDSU http://www5.compaq.com/services/message/mc_ldsu_fact.html which will help you in this regard.
I have one exchange server that is currently sitting on our public wire which is handling all our mail traffic. I have a new server setup on the inside network behind the firewall as a mailbox server. 2 servers in the same site. All works well. One user who I've migrated to the new mailbox server was using IMAP from home. Since no public IP is passed to the mailbox server is there any way for him to connect to the outside mail server via IMAP and still get to his mailbox? OWA works fine and essentially does the same thing. I've read that exchange 2000 can do this since IMAP is now handled by IIS 5 but have had no luck finding anything on 5.5.
You'll need to upgrade to Exchange 2000 and implement an FE/BE scenario to get protocol proxying. It is highly suggested and recommended to implement a VPN (Virtual Private Network) which is probably easier and a better solution for the long term in such cases.
Is there a way to strip off attachments from messages coming from the internet without using a third party utility? If not what third party utilities would do this?
This can be achieved though third party software only. Most antivirus and email content checking software available on the market today can be configured to do this. Some references http://www.mailessentials.com , http://www.mimesweeper.com , http://www.trend.com/products/smex
Is it possible to make anonymous postings to an Exchange Public Folder?
It's best accomplished via OWA (Outlook Web Access), which can be truly anonymous. You can't log onto Outlook anonymously unless you create an "anonymous" mailbox. You can also check the following resource http://www.cdolive.com/anonymousposting.htm on the subject.
I have to make sure that ALL our users have a firstname.lastname@... smtp address. Currently, we have a mix of first_inital lastname@, etc. as well as the firstname.lastname@. Are there any potential problems with trying to add a redundant smtp address? E.g. E-mail Addresses list SMTP:john.smith@... and I add a Secondary-Proxy-Addresses of john.smith@...?
Import will bounce duplicates. You get a related message in the event log.
We are running Exchange 5.5 sp3 w/ IIS 4.0 on the same server. Viewing contacts within OWA (IE browsers). Only the primary folder can be displayed, no subs. Any fix or workaround? The error message states this version of Outlook Web Access only supports viewing your primary contact folder. Even if the sub contact folder is moved to an email folder, OWA still knows the difference. All other sub folders (email) are working fine.
This function is not provided in OWA with Exchange 5.5. It is available in the Exchange 2000 version.
I would like to have my http web access for exchange server to https using SSL. What are the pros and cons for the same?
Please check the following document from the MS KB
http://support.microsoft.com/support/kb/articles/Q234/0/22.ASP