Event ID 9098 - Microsoft Exchange |
- Event ID 9098
- aha! wrong mailbox store
- Standard to Enterprise upgrade
- AD Schema and default Send and Receive Limits
- Junk Email Policy
- Exchange e-mail box not created
- Unable to connect to OWA after email address change
- How to set Default Mailbox Limits
- Exchange 2003 Outlook Web Access
- DL Membership export
- SMTP connector with outbound security enabled, enables authentication for all other connectors!!?!
- POP3 - not deleting deleted messages from server
- E-mail not sending to particular address
Posted: 10 Jun 2005 07:52 PM PDT Have you heard of anyone experiencing adverse affects from installing this hotfix? We currently do not have a development environment on which to test this update. "Todd J Heron" wrote: |
Posted: 10 Jun 2005 11:16 AM PDT On Fri, 10 Jun 2005 10:26:39 -1000, "Jim McBee \(MVP\)" <spambegone.net> wrote: You can't mapi connect to the RSG. There are no cobwebs in that toned Mid-Pacific mind. |
Standard to Enterprise upgrade Posted: 10 Jun 2005 06:54 AM PDT Doesn't get much easier, hey? One more question - does the move from standard to enterprise constitute an 'upgrade' in that you are still using the license from the standard or is it such that the purchase of the Enterprise Server media constitute a seperate purchase allowing for the installation of the original Standard version on another seperate server thus allowing you to have two seperate Exchange organizations? "Jim McBee (MVP)" wrote: |
AD Schema and default Send and Receive Limits Posted: 09 Jun 2005 02:20 PM PDT "Fred Yarbrough" <com> wrote: The same way we already do. :) For message sizes, place the maximum upper limit at the "global" level and the smaller limits on the individual objects that are the exception to those limits. You can only increase the individual upper-limits to equal the size of the global limit. For mailbox sizes, place the general limit on the database (and, if you have many of those, apply the limits in a policy). Make exemptions at the individual mailboxes. Here you can exceed the default limit you set in the database properties. I wouldn't set limits on the indivual mailboxes for the receive sizes, just the send sizes. Why not? If the other users need them to accomplish their jobs they should be able to receive them. But that brings up the question of why one internal user would use e-mail to share a file of that size with another internal user. A file share, ftp server, web site, or sharepoint server would be a lot better for this. There are probably commercial tools that would provision your users according to one classification or another. -- Rich Matheisen MCSE+I, Exchange MVP MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm |
Posted: 09 Jun 2005 12:51 PM PDT Hi, Question regarding the GPO for junk email. Are we supposed to see the list of safe senders we had in the text file appended in the Safe senders tab of the outlook client? Thanks in advance "Nebojsa Seslija" a écrit : |
Exchange e-mail box not created Posted: 08 Jun 2005 06:03 PM PDT Okay. This is what I did. I went to another user and sent the new user an e-mail. When I look in the exchange administration, it shows her e-mail box. When I open her Outlook, it still can not resolve her name. If a use a diffrent name, no problem as it underlines the name. So this tells me that it is communicating with Exchange. You mention a filter in Exchange but I am not sure where to fix if that is the problem. Thanks againn for any assistance. "Ilse Van Criekinge" wrote: |
Unable to connect to OWA after email address change Posted: 08 Jun 2005 11:15 AM PDT This was great. Thanks for your help. CB "Ilse Van Criekinge" wrote: |
How to set Default Mailbox Limits Posted: 08 Jun 2005 09:43 AM PDT Hi If you have an exchange ENT edition, you can create a new store fore those users and set up limit in the store level -- "Fred Yarbrough" wrote: |
Exchange 2003 Outlook Web Access Posted: 08 Jun 2005 09:26 AM PDT Thanks Paul... The IIS lockdown tool was run against this server prior to the Exchange installation. urlscan was running and was indeed what was causing the problem. As soon as I turned off urlscan all worked well. There was an article on support.microsoft.com (I didn't save the article number) that helped, but ultimately, I contacted Microsoft for help and they helped me modify the urlscan.ini file to include all of the components necessary for OWA. OWA is working fine now. "Paul Ford" wrote: |
Posted: 08 Jun 2005 08:09 AM PDT ahhh, thanks. I saw that post elsewhere, but didn't notice the DL membership portion of the tool. Thanks. "Iv Borissov" wrote: |
SMTP connector with outbound security enabled, enables authentication for all other connectors!!?! Posted: 08 Jun 2005 07:24 AM PDT Hi guys, We only have the 1 virtual SMTP server on the Front End servers. and just to confirm I haven't enabled outbound security here. I have simply enabled it on the 'Admin users' SMTP connector found under \Routing Groups\First Routing Group\Connectors in ESM. It's a really weird problem isn't it.. Oliver |
POP3 - not deleting deleted messages from server Posted: 07 Jun 2005 03:30 PM PDT In news:com, Compcond <microsoft.com> typed: Hmmm - then I'm confused. |
E-mail not sending to particular address Posted: 07 Jun 2005 03:19 PM PDT In news:com, Henry Case <microsoft.com> typed: Yep - just doesn't sound like it's YOUR server. |
You are subscribed to email updates from TextNData Forums - Microsoft Exchange To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google Inc., 20 West Kinzie, Chicago IL USA 60610 |