Unity 4.2 voice mail only with Exchange 2003

Hi Team,
we are replacing window 2000 OS with Win 2003 for unity 4.2. This is a single box solution. Exchange 2000 is installed on same unity server. Now we are upgrading the OS from 2000 to 2003. With window 2003 we have to installed the Exchange 2003. In unity installation 4.0(5) following paragraph is mentioned which means we need separate hardware for Exchange. Kindly advise whether we need a separate server for Exchange 2003 or we can install on the on unity box.
If you are using Exchange 2003, install Exchange 2003 administration software on the Cisco Unity server. (Exchange 2003 is installed on a separate server.)
If you are using Exchange 2000, you can install Exchange 2000 either on the Cisco Unity server or on a separate server. If you install Exchange 2000 on a separate server (typically for systems with a large number of subscribers), install Exchange 2000 administration software on the Cisco Unity server.
BR
Muhammad Irfan

Thank you Javalenc,
I can understand from following that Exchange 2003 can be installed on same server.
Voice Messaging
•Exchange 2003 on the Cisco Unity server or on a separate server. If you want to install Exchange 2003 on the Cisco Unity server, note the following:
–The Cisco Unity server must be running Windows Server 2003.
–Exchange 2003 can be installed only on the currently shipping servers supported for use with Cisco Unity 4.2 (MCS-78xx-x2, MCS-78xx-x3, or later, including IBM and HP equivalents). Currently shipping servers are listed in the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/
As you know we are just replacing the OS, from win 2K to 2k3. So any thing I need to take care to back up the existing Unity with win 2000 and exchange 2000..
I am taking the back up of my unity 4.2 installed on window 2000 with DiRT and will restore on unity 4.2 with win 2003 and Exchange 2003.
Kindly advise.
BR

Similar Messages

Unity Connection 8.5 single inbox with Exchange 2003 - Access denied

Hi,
I'm using CUCMBE 8.5.1.12900-7 Unrestricted. i'm following Unified Messaging Guide for Cisco Unity Connection Release 8.5 and Later for configuring single inbox. I have successfully setup and tested unified messaging service when I subscribe this service to a particular user and test it, I get following error:
Issue: Failed accessing [email protected] on 192.168.0.10
Recommendations: Some possible reasons for 401: Incorrect service account name or password. Service account password expired. Proper permissions not granted to service account. Exchange mailbox uninitialized.
Details: HTTP status=[401 Unauthorized] diagnostic=[Bad response from server, HTTP code returned: 401] url=[http://192.168.0.10/exchange/
[email protected]] request=[<?xml version="1.0"?> <D:propfind xmlns:D="DAV:" xmlns:fh="urn:schemas:httpmail:" xmlns:h="http://schemas.microsoft.com/repl/"> <D:prop> <fh:msgfolderroot/> </D:prop> </D:propfind> ] response=[<html><head><title>Error</title></head><body>Error: Access is Denied.</body></html>]
I have verified above mentioned recommendations but no such issue exists. Any ideas?

Hi Muhammad,
I am having exactly the same issue in configuring sinlgle inbox with unity connection 8.6 and exchange 2003. I have checked everything but no result. Could you please help in configuring?
Thanks
The validation results for the user unified messaging service account [email protected] with service E2K302 are the following:
Service "E2K302": AuthenticationMode=NTLM [use HTTP] Server=[E2K3-02.chelloit1.local] Type=[Exchange 2003] Username=[chelloit1.local\agokharu]
Failed accessing [email protected] on E2K3-02.chelloit1.local
Some possible reasons for 401: Incorrect service account name or password. Service account password expired. Proper permissions not granted to service account. Exchange mailbox uninitialized.
HTTP status=[401 Unauthorized] diagnostic=[Bad response from server, HTTP code returned: 401] url=[http://E2K3-02.chelloit1.local/exchange/[email protected]] request=[<?xml version="1.0"?> http://schemas.microsoft.com/repl/"> ] response=[ErrorError: Access is Denied.]

Unity: Voice-mail for non-Exchange subscribers

Hi everyone!
I have this issue: customer wants to enable voice-mail for non-Exchange users, I've created them as Internet subscribers for using with auto attendant, but I can't enable voice-mail for these extensions, basically the customer does not want for this users to receive the messages in their mail just only check it on IP phones. Is there a possible way???
Thanks in advance for your help

To add to Hailey's comment, here's the documentation that explains the behavior/limitations of Internet Subscribers in case you're interested in checking it out:
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/5x/networking/guide/ex/5xcunet040e.html#wp1050583
Hope that helps,
Brad

Unity Connection Voice Mail Only- NO MWI template

I am deploying a site with 8,000 mailboxes. 4,000 of those users are voice mail only without a telephone and will NOT require MWI.
I can manually remove the MWI setting from each mailbox, but I am looking at either a BATCH CSV setting or a TEMPLATE that I can turn OFF mwi when creating the users.
Any ideas?
TIA

Hi there,
This setting change is available via Bulk Edit
Bulk Edit> Messages> Disable MWI functionality for this user
Bulk Edit changed in 8.x from where it was accessed in 7.x.
Here's a clip that speaks to how this is run now. You first search and select all
the users you want to change and then choose Bulk Edit;
To Edit User Account Information in Bulk Edit Mode (some editing from original > this example
is for Caller Input settings but you'll see the point)
Step 1 In Cisco Unity Connection Administration, on the Search Users page, check the applicable user check boxes, and select Bulk Edit.
If the user accounts that you want to edit in bulk do not all appear on one Search page, check all applicable check boxes on the first page, then go to the next page and check all applicable check boxes, and so on, until you have selected all applicable users. Then select Bulk Edit.
Step 2 On the Edit Caller Input page, change settings as applicable.
Note The Status message at the top of the Edit Caller Input page tells you how many user accounts are being edited. Also note that the page is populated only with the fields that you are allowed to edit in bulk mode, and that the fields available for edit also depend on whether all of the user accounts reside on the local server.
Step 3 If applicable, set the Bulk Edit Task Scheduling Fields to schedule the Bulk Edit operation for a later date and/or time.
Step 4 Select Submit.
Step 5 If applicable, continue to change settings for these user accounts on the related pages available from the Edit menu. As you make changes on each page, select Submit before going on to the next page to make additional changes.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/user_mac/guide/8xcucmac090.html#wp1049545
Try a couple of test users first to come up with the exact plan.
If you prefer you can also use Bulk Edit via .csv
As a test here I tried the Bulk Edit and chose;
User with Voicemail > Users referenced in this CSV file > Next
This then allowed me to browse to an existing "basic" .csv that I had
used to create a test user recently when playing with BAT. In this .csv
I had one user named Bob Uncle with DN/ext 5126. So when I used this method
the Bulk Edit tool (smart puppy ) selected only Bob Uncle for my edit choices
and I was able to change the Disable MWI functionality for this user
Again, please try manipulating some test users to perfect
your methodology.
I have attached the test .csv I used
Cheers!
Rob
Attachments: buncletest Mailboxes.csv.zip (255 bytes)
"Show a little faith, there's magic in the night" - Springsteen

Voice mail issue with CUCM or CUCME

Hi,
I want to know a basic information regarding voice mail configuration in CUCM or CUCME.
With the very basic configuration of CUCM or CUCME without any unity or unity connection, is it possible to have basic voice mail features with the system. Say, I have configured call manager server with voice gateway connected to PSTN. Now is it possible to have voice mail for the system without cisco unity or unity connection configured.
Same goes for CUCME. We have CME bundled router configured. Can we configure voice mail with unity express without having separate license?
Please help ,e to get the answer for this query.
Regards,
Sagar

Hi Amer,
Thanks for your help. Is this same for both CUCM & CUCME?
For welcome greetings, I have configured its-CISCO.2.0.2.0.tcl in the VG. Can you please guide me about basicAA.tcl script, i want to give it a shot.
Regards,
Sagar

When opening my Outlook 2010 with new added e-mail account with Exchange Server, I have to click manually on my standard e-mail account for checking mail

When opening my Outlook 2010 with new added e-mail account with Exchange Server supplied by my employer, I have to click manually on my standard e-mail account for checking mail. Do I have to upgrade my Microsoft Office 2010 or how can I make my Outlook
2010 check all my four e-mail accounts without manually click on my accounts?
Sincerely
Ketil Hothorp

Hello Ketil,
Good Day...
Seems to be the Issue is Syncing emails, now I would recommend you to Remove and Add the Account and try and check if the emails are getting synced automatically.
Hope this is with Single User. If it is with Multiple Users then we need to check the permissions assigned.
Regards,
Praveen

Has anyone managed to create an email account on the OS X mail client with Exchange 2007?

Hi guys,
the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
Thanks
Juergen

jthurner wrote:
Hi guys,
the IT chaps of my new employer tell me that it is impossible to use the OS X mail client with Exchange 2007 servers. Is that correct? If so, does anyone know a workaround?
Thanks
Juergen
No workaround needed, open Mail, Contacts and Calendars (in System Preferences) select Exchange, enter your email address and password, opt to setup Contacts and Calendars as well as mail and hit enter. That should set it up (assuming your apparently witless IT dept has setup the autodiscover record correctly at their end)

Daily Problems with Mail Synchronizing with Exchange Server

Our office uses Comcast Business Class Service, which uses 2007 Exchange Servers, for internet access and email. I upgraded my MacPro from 10.5.8 to Snow Leopard 10.6.2, using the Upgrade DVD. The upgrade process kept my original Leopard Mail settings, which were using POP. At that time, I had not problems with email.
Unfortunately, awhile ago my Mail Preferences became corrupt, and I had to delete them. Upon relaunching Mail, the application wanted to use the new Autosync method to connect to the Comcast Exchange Server. Using POP was not an option.
I must say that I am less than impressed with the way Mail integrates with Exchange Servers. I have daily problems, and experience these problems multiple times per day. When they happen, they slow my email communication down to a crawl; sometimes for as much as an hour.
Specifically, the problem appears to be with Mail's ability (or inability) to properly synchronize with Exchange Servers. I get he spinning pizza icons next to the two Exchange email accounts I have in my Mailboxes source column. Opening the Activity window shows that the synchronizing process has slowed everything down. This results in not being able to send or receive email until the synchronizing is complete. And as I said, that can sometimes take as long as an hour.
Stopping the process in the Activity window does not resolve the issue. Nor does quitting and relaunching Mail. Because the next time Mail attempts to connect to the Exchange Server, it will try to synchronize yet again. The problem has become so chronic, that I often have to resort to using Webmail while waiting of the synchronizing process to complete.
Incidentally, the mailboxes that are synchronizing are empty! I am meticulous about keeping my Inbox, Sent, Drafts, and Trash mailboxes empty at all times. I do not use To-Do's, Notes, or Calendars of any kind on the Exchange Server, so there is no data to even sync!
Has anyone else experienced this problem and found a fix? Other email accounts I have, which use POP or IMAP, do not have this issue. There does not appear to be away to abandon the Autosync Mail setup and revert back to POP. If there is, I will do it in a heartbeat.
Thanks.

Found a solution that works for me. Delete the problem account that's using AutoDiscover to sync with the exchange server. Before doing that, however, you will want to clear out the Inbox, Sent and even Trash folder for that account, as deleting it will remove the messages that currently reside in those folders. Just simply move them to another folder. You can move them back after re-creating the account.
The second step is to re-create the account. Do this as you would normally, and enter in your name, username and password. THE TRICK: Press and hold the Option key when you click Continue. After Mail connects to the server and verifies your account information, you will then have a pull down menu that will allow you to choose Exchange Server, IMAP and POP. Simply select POP or IMAP, then fill out the rest of the fields.
Viola! No more problematic Exchange Server syncing issues.

Require Passcode Immediately with Exchange 2003 and iPhone 3.0?

Before I upgraded to iPhone 3.0 I was syncing with Exchange 2003 SP2 and I had set my passcode to be required after 1 hour, which was changed from the default of 4 hours. On the Exchange server we have a policy in place to have a max of 12 hours before a passcode is required which works on my WM phones.
After upgrading to 3.0, the phone now immediately requires a passcode every time I turn it on. I went into the settings to change it to be a little longer, but the only option is to have it Immediately and I have lost all of the other options. Is there a way to get back at least 1 hour or something that reflects the 12 hour setting on my Exchange server?

I can confirm that you just need to turn OFF Mail, Contacts and Calendar sync within the Exchange account, set the timeout 4 hours (or whatever - it will automatically shrink down if your Exchaange administrator's policy is more restrictive), and then turn back ON Mail, Contacts and Calendar sync.
Note you'll get a scary warning that says all your Contacts and Calendar data will be deleted from the phone - Outlook users can ignore if you're syncing with Outlook, since it will re-sync when done.

Outlook 2013 not compatible with Exchange 2003

Hello
Some of my customers bought SBS 2003 R2 just before SBS 2008 was released so they have systems which are only 4+ years old. SBS 2003 came with Exchange 2003 pre-installed. Outlook 2013 does not support Exchange 2003. So they cannot upgrade their Outlook
clients to 2013 version.
Microsoft, is this correct?!

If this post is hard to read, it's because of Dragonsoft!! (sometimes it is like auto-correct on the phone - "I said WHAT!??")
Overall I think this is the most interesting thread that I have ever read on Microsoft.com.
As a computer for professional for over 30 years, I've always followed the context that software products are designed for a three to five-year term, to have more is a luxury.
When I was first in the industry (1983), Microsoft had a tendency to change the software versions every year to two years. As we approached the era of Windows XP there was an expected lifetime use of three years. Every two years a new product would appear.
So, when windows XP lasted well beyond the three-year term, it was pretty exciting to not have to spend money on new product, and we all enjoyed the decade of Windows XP.
The new generation of IT professionals has somehow believe that software products should live more than five years, and it just blows my mind!
The reason that I make this post, is because I've used SBS ever since Back Office Server 4.5, and the versions of small business server (now called Small Business Server) have always appeared on the market 1 to 3 years after the primary versions of
Windows for which they are named. So I always felt that there was a disadvantage to using small business server in that the products appearing inside of SBS had been on the market for a few years before being incorporated into the SBS package. It
made me feel, at first, that Microsoft was waiting on the level of maturity within the product before creating the SBS package. Now that I look back on the whole process it made me think that the SBS team had some difficulty merging the products into a install
package which could handle the intricacies of the licensing limitations on the SBS system.
SBS 2003 was a great tool when it came out, but I found that it was riddled with security holes. To say the least some of my first SBS 2003 servers had their exchange system hacked by outside influences. (These were external facing servers who had websites
and exchange server running with public domain names, even though there were firewalls!) After a few patches, DNS modifications, reverse DNS entries, and some changes in the exchange system, I was finally able to make the system secure and solid.
My first real nightmare with SBS was when upgrading to SBS 2003 R2, which, yes, appeared around 2005. You cannot simply upgrade a machine from SBS to a new version. You must purchase a new server, install the new SBS version, and migrate your
entire installation to this new host. (While running SBS 2003 for several years and making backups on a tape, I realized that the new hardware on the market would not support a restore from my tape backup!) The whole process is rather daunting as not
all of the detailed steps to upgrade work as expected. I had to call, and pay, Microsoft to complete the process because exchange had trouble during the migration.
So off we went with our new installation of SBS 2003 R2. Then along came SBS 2008! I went through the same steps again... new hardware, new software, and, yes, paid Microsoft, again, for support to migrate.
When SBS 2011 appeared on the scene I was willing to upgrade again. Having gone through this, twice now, I fully prepared the client to purchase a new system and to purchase the new software. But because I was faced with the whole entire
nightmare of new hardware, migration, and having to call Microsoft to complete the process, I decided on a new approach. This time we were going to buy server which would run VMware. (I was not going to get stuck in a hardware box that I could not replace
if I ever needed to restore the operating system due to a massive failure.) So off I went, purchasing a new box, installing VMware, and installing my favorite operating system, Microsoft SBS!
Well, to say the least, it wasn't exactly as exciting as I had expected. Had some trouble getting VMware to settle into the new hardware, as there seemed to be some compatibility issues, but was able to work it out. Eventually, I was able to get started
on the migration. Things went well up until the point that I got to the exchange migration, and ran into a similar problem as before! A call to Microsoft revealed that it was even a little daunting for the support personnel, but as I documented the things
that they modified, and even performed a little cleanup, after they performed their cleanup! I can happily say that I'm no longer worried about hardware issues, when it comes to restoring my SBS server in case of a failure!
Overall I'm pleased with having used Microsoft SBS solutions over the past 10 years, but I would never expect, nor would I lead my customer to expect, that a product should last 10 years!
Previous comments have indicated that server should last seven years because they can be depreciated that way, I believe that to be entirely false! I live in Texas, and the state of Texas DIR program has adopted standards which state that
you should replace your hardware every five years! State agencies have this as a requirement, and it is not optional! Many state agencies have gone to leasing their equipment, which is a three-year term. (Where do you think off-lease equipment comes
from, anyway?)
One of my primary clients looked at me one day, and directly ask, "Okay, if we spend the $10,000 on the new server and software, how long should it last?"
Obviously, I wanted to say, "Forever!" But, remembering something that my mother had said (always plan for the worst and you always come out on top!), I said back to them, "I believe we should plan for a three-year lifespan, and if we get
any more than that, it will be a luxury." Needless to say, there have been some upgrades which lasted well more than three years, but there have been some which have been spot on.
The SBS server is a huge savings over purchasing the individual products separately. But there have always been some drawbacks during the upgrade process which makes the entire feasibility of the installation top-heavy when it comes to support costs.
I have noticed is that the SBS servers require more labor to keep them running smooth, especially with backup procedures and backup software, as SBS always requires a third-party product to make a "real" (restorable) backup.
A client's expectations should be that you are taking care of their business without them having to worry about what takes place in the tech room. They understand, and realize, that they can pay you a specific amount of money for your support without necessarily
having to purchase new hardware. But a good, healthy relationship with your client means that they should always be willing to upgrade, whether it is a workstation or server.
If you allow a client to be painted in a corner, then it's not their fault, it's your fault! Because, they have no idea what the new technology can do, and don't realize what's on the market. It's your job to keep up with what's current and to deliver
expectations which make them realize that each year has a dollar value attached to it, whether it is spent, or not.
If you have a client is unwilling to spend money to upgrade their equipment, then there's something else wrong with their business, and you should probably consider that they may not be in business for very long. So don't make it your problem when
they are unwilling to spend money. You don't work for free.
One last, quick example of the conversation that I had with a client who was unwilling to upgrade because things seem to be working so well. I put it like this, "You pay me to make certain that your business operates in good times and in
bad. Right now, everything is fine. If your building were to burn, and the only thing we had were the backups, I cannot go out and purchase new hardware and restore your system successfully. The equipment that we have operating here is no longer
available on the market. If I were to find the equipment, it would be out-of-date, and most likely, used, and I cannot guarantee its compatibility or functionality. So, if I can't restore your system to an operational status, then what would you do?
I don't believe there are any number of man-hours you can use to recover the information lost. You would probably have to go out of business! If your business becomes my business, then I would try to move to a position where my data is safe and my business
can continue in the case of catastrophe. The only way I can do this, is to purchase new hardware, new software, and put you back in a position of compatibility with the market. One of the things I always try to do is keep your business operations at a point
where if I die, someone else can come in and take my place. The whole idea here is to keep your business going."
It didn't take them long to come back and surprise me, "Make a list of what you need. Don't give us a list of what we need to get by, tell us what we need to be productive for several years. We don't want to patch this together
and always have problems."
And just as a note, your customer can write off $10,000+ per year for new equipment purchases. I think the number may be higher now. I had one customer who purchased a $15,000 system in December and wrote off $10,000 in one year and the other $5000,
a month later, in the next year!

Will Microsoft Exchange2000 Portlet work with Exchange 2003

Hi All,
Has anyone tried using Microsoft Exchange2000 Portlet with Exchange 2003 ? Or is there any Portlet available for Exchange 2003 ?
Thanks in Advance.
Dipak

I'm facing problem with Exchange 2003 portlet which is not working with all users. it's working good only with the one user. I mean it doesn't allow the other users to put there user name & Password .
Please help me with this portlet or is there other portlet for exchange 2003
Thanks
Waleed

Jabber call to voice mail fails with fast busy over VPN

I have an issue that I ran into with CIPC phones over a VPN. If a CIPC phone called over a VPN and started ringing a phone the call would fail with fast busy at the time the call would be forwarded to voicemail. I found the issue was when remote the CIPC phone would negotiate the g.729 codec, when forwarded to a voicemail pilot over a SIP trunk set to g.711 the call would fail due to codec missmatch when no transcoders are present.
So now I am running into what I believe to be the same issue with Jabber, when on premise the calls to voice mail work just fine, but when remote they fail. I can directly call the voicemail pilot without error, but if calling a phone the call gets fast busy at the point we are forwarded to voicemail. Even though all my regions are set to talk to all other regions on G.711 and the voicemail SIP trunk is set to G.711, I believe with the new features in CUCM9 that a lower speed codec has been negotiated since the we are going over the VPN, or Jabber has done this as it knows it's over VPN (not sure). WIth CIPC I could go into the settings and turn off the Optimize for Bandwidth check box and the call would negotiate G.711. With Jabber I can't find anything that would tell my Jabber client to stay on G.711 and I can only imagine this is a codec missmatch as the following are true.
1. CIPC and Jabber share the same line
2. VPN established and CIPC optimised for low bandwidth un-checked
3. Over the same VPN the CIPC phone can leave a voicemail
4. Over the same VPN the Jabber client gets fast busy once forwarded to voicemail
5. Voicemail environment is Exchange-UM over SIP trunk
6. SIP trunk is assigned a Device Pool, that is assigned to a region that all other regions communicate G.711 to
7. On CIPC if optimised for low bandwidth is checked I get the exact same issue as I get with the Jabber client (fast busy when forwarded to voicemail)
Would anyone know what I can do in CUCM 9 to fix this issue, as said no issue when all devices are on premise. Wondering if there is a service parameter or a way to change the codec selection so the Jabber client attempts to always negotiate G.711. The correct answer would be to get some PVDM DSP resources and kick up a transcoder in my resource group, and that may be what I talk them into doing if I have no other options.

We have been getting the exact same thing for almost a year now... since switching to FiOS Digital Voice in May of last year! Every time I call in to report it they 'escalate' the issue but it never gets resolved. The problem seems to be in the initial connection. Most of the time it works fine but, several times a month, after I call to get messages and it starts to play the new message it goes dead and I get the busy signal. I get the same message when I call back: “I’m sorry – that account is in use at this time. Please try again later!” I have even called in with my cell phone and get the same message! I HAVE EVEN used the Internet to see if I could get my messages and, when I hit Play, I get a pop-up saying: “Your Voice Mail box is currently in being accessed; please try again later. If the problem continues, please contact our Customer Support Center at 1-888-553-1555. We apologize for any inconvenience.” This is obviously a software bug that Verizon has no clue on how to troubleshoot OR fix!!! I wonder how many people have the problem and just don’t bother reporting it because of the hassle? When it first started happening they destroyed my entire mailbox and I had to re-enter the complete mailbox setup again – 3 times!!! NEVER let them talk you into that!!! It’s their problem and they need to fix it!!!!!!! I wish I could go back to the ‘normal’ voicemail we originally had… they want hundred$ to switch back because I’d be breaking my #$@%^&* contract! Good luck if you have Verizon………

Yosemite Mail crashing with Exchange account

I'm running OS X Yosemite 10.10.1 on a 2014 Macbook Pro.
On startup Mail crashes immediately with the following error:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'An EWS folder ID string didn't have a corresponding mailbox name'
I have three email accounts (Exchange, iCloud, Gmail) and have disabled each one in turn and Mail opens and works fine with the iCloud and Gmail accounts. So it's definitely a problem with Exchange. In the Mail accounts pane the 'Advanced' tab has a listing for Internal Server Path with 'EWS/Exchange.asmx' listed in the box, so I'm guessing it has something to do with that (given the EWS bit in the error message)?
I've moved the com.apple.mail folder to the desktop and re-opened Mail but that didn't help (I've moved the folder back to where it was).
I can access my Exchange mail from both iPhone and iPad, so the problem seems to be restricted to OS X Mail rather than a problem with a specific email (seems logical?).
Any help appreciated.
Cheers,
Grant.

Thanks. I had tried that already but it seems that the account was only 'deactivated' rather than deleted. Anyway, I tried again and chose the option to delete the account from all devices. I've now added a new Exchange account and all seems to be working.
Thanks again.
Cheers,
Grant.

Send E-Mails with large attachmenst with exchange 2003 Mailbox

Hi!
I have the following setting:
Exchange 2003 for one Domain an two mailboxes with two different iPhones. One Mailbox/iPhone can send Mails with large attachments (500kB-5000kB) without any problems.
The other mailbox has the problem, that i can only send with attachments sized about 50 kB. Larger Attachments are blocked by the phone and this mail stays in the Out queue.
Has anybody a hint for me, where i can change this? I think it must be a user paramter, because one mailbox can send those large attachmenst. The Server it self must be ok - i think.
Server: Windows 2003 with SP2; Exchange 2003 SP2
Kind Regards
Martin

I agree with you - i think it must be a problem with the mailbox on the server side. But i don't know what to change there?
I also configed on one iPhone those two mailboxes. One box can send large attachments - the other not.
Martin

Apple Mail problem with exchange server

Hi
I configure my both Apple Mail and Entourage to link with my work's MS outlook exchange server. Apple Mail is using Exchange and Entourage is using SMTP. Both work fine receiving and sending while i am in the office. However, when i am home or using USB modem, it will only receive and will not send. Can anyone advice what is the issue?
Thanks

well your work IT guy "should" know which IP address is needed to access from within the work network and from without depending on how he has set up that Exchange server... else it is time to find another IT guy It really is an exchanger server issue, not an Apple Mail issue.
For example, I have been given two IP addresses to use for the outgoing server, and I toggle between one and the other when I want to send email via my exchange account.
hope this helps

Unity 4.2 voice mail only with Exchange 2003

Similar Messages

Maybe you are looking for