C:\ExchSrvr\mdbdata\Priv.edb - VBS.Bagle.X worm. - Microsoft Exchange |
- C:\ExchSrvr\mdbdata\Priv.edb - VBS.Bagle.X worm.
- 9GB of exchange logs in MDBDATA folder.
- configuring Exchange 2003
- Priv.mdb
- UN-INTENDED EMAIL
- Rejected Mail
- Unable to reply in OWA
- Changing the Sent From Field in Exchange Outlook 2003
- Badmail problem
- NUL characters are not allowed
- Delayed and bounced mail woes AAaaarrrrghh
- OWA Stops working
| C:\ExchSrvr\mdbdata\Priv.edb - VBS.Bagle.X worm. Posted: 06 Sep 2004 06:09 AM PDT You are scanning the priv.edb with flat-file AV software? On Mon, 6 Sep 2004 06:09:39 -0700, "Kay Kay" <microsoft.com> wrote: |
| 9GB of exchange logs in MDBDATA folder. Posted: 06 Sep 2004 03:38 AM PDT Do you have the Exchange agent installed? What version of Exchange are you using? "Leon" <ap76_at_email.com> wrote in message news:ugUG$phx.gbl... |
| Posted: 06 Sep 2004 12:45 AM PDT Not without third party software called a POP connector...not recommended. Do you have a registered domain name? You can host your own mail on the Exchange server very easily....perhaps want to wait til you decide to go with Exchange or not. http://www.msexchange.org/tutorials/MF002.html is written for E2k but will work with E2003 as well. Read it for an overview of how this works. alanwforbes wrote: |
| Posted: 05 Sep 2004 10:39 PM PDT try ontrack ... cheap and speed, in the site you find a demo to recover data from exchange, without log file.... only with a copy of your db. "Cold_Boot" wrote: |
| Posted: 05 Sep 2004 12:36 PM PDT <microsoft.com> wrote in message news:65f601c49384$89f30db0$gbl... No. BCC doesn't show up - that's why it's 'blind". Not sure what you mean. If you had/have service-account level access, you have access to everything in a mailbox. If your company is serious about security, they will have enabled audit logging, though. And probably not allow people to have full mailbox access. How are they saying you got access to this message? |
| Posted: 05 Sep 2004 07:12 AM PDT You can still have a copy of undeliverable mail sent to whatever mailbox you like - set in the properties of your SMTP server. I personally don't bother - I think it's the recipient's responsibility to address mail correctly and if they get an NDR, they'll try again. If you have a user with a commonly misspelled email address, you can add another email address with the misspelling if you want. Postmaster Bob wrote: |
| Posted: 05 Sep 2004 05:02 AM PDT No pop-up blockers and XP SP2 not installed yet. returns me to the inbox |
| Changing the Sent From Field in Exchange Outlook 2003 Posted: 03 Sep 2004 12:30 PM PDT dankim wrote: Correct his Display Name in Active Directory Users & Computers. This one's fine - but note that a lot of things in SBS are different, so m.p.windows.server.sbs may be a better place in the future. |
| Posted: 03 Sep 2004 09:35 AM PDT The sender did not get anything back. As far as I can tell the events must have been as follows: 1. Our Exchange 2003 server go the message for the 3 users but did not deliver it to them. 2. It generated the exact NDR yoiu see below in the .BAD file but did not send it to the original sender. This concerns me because I see this message which should have been delivered, but was just dumped in the badmail folder. I find it strange that it also tried to create an NDR, but failed to send it to the valid sender. "Lanwench [MVP - Exchange]" <donotsendme.unsolicitedmail.atyahoo.com> wrote in message news:phx.gbl... |
| NUL characters are not allowed Posted: 02 Sep 2004 02:02 AM PDT Yes, the email was sent in HTML format. But if we would to send the html format to another domain eg yahoo.com, there is no problem. So we are trying to find out how to check if there is a NUL character in the email. Cheers, May the articles were message for not |
| Delayed and bounced mail woes AAaaarrrrghh Posted: 01 Sep 2004 03:19 AM PDT Thanks Glen. |
| Posted: 30 Aug 2004 10:06 AM PDT "Mike" <microsoft.com> wrote in message news:5f5d01c49223$30c34230$gbl... We have had extremely good luck with owa in about 15 installations, as well as our own. These, however, are small installations < 150 users. We always use ssl, denying access through port 80 at the router or firewall, and typically do forms based authenticaion. OWA 2003 is, in my opinion, a good selling point due to its unified look and field when compared to OL2003. Honestly, I can't remember a single crash, or even having to do iisreset. I wonder how many others out there have owa horror stories. |
| 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 | |
