Two Servers Running Exchange - Microsoft Exchange |
- Two Servers Running Exchange
- Build number remains the same after updating Exchange 2000 SP3...
- Server upgrade?
- Mail rerouting???
- Exchange 2003 Installation
- Exchange Auditing
- Tool to extract the Signature Block from a message
- Exchange 2007 Message Tracking Parameters
- Documentation JV.
- "Meeting Request" Strange Behavior
- cheap backup solution for e2k7 on server 2008?
- Exchange 2007 is mad at us and our "distinguishedName" generation says MSFT PSS, any way to customize it?
- email bounced if sent to group of people
- Optimizing SBS 2003 Excange? Intermittent Connection Issues!! HELP
- Can Excange 2007 handle thousands of emails at once?
- RPC over HTTP Exchange 2003
- Firewall Ports Require behind firewall port
- Event IDs 7031 & 7034 on Exchange 2003 Server
| Posted: 02 May 2008 01:57 PM PDT Thanks Bharat When installing would I follow the normal setup or is there anything special I should look out for? Thx "Bharat Suneja [MSFT]" wrote: |
| Build number remains the same after updating Exchange 2000 SP3... Posted: 02 May 2008 11:43 AM PDT > Where are you checking that? Ok, calm returns to me, I was checking on the Exchange System Manager console... Thanks a lot Sammy |
| Posted: 01 May 2008 08:46 PM PDT If you have not purchased any licensing yet, I would seriously look at Essential Business Server. http://www.microsoft.com/windowsserver/essential/ebs/default.mspx -- John Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2008 Microsoft Certified Partner "Lar" <org> wrote in message news:com... |
| Posted: 01 May 2008 05:54 PM PDT BobS wrote: You need to look at the full set of headers, not just the ones Microsoft thinks you should see. Outlook will grudgingly show them in a tiny window if you select Options for the message. The important ones are the various 'Received:' headers, which will show all the legitimate mail servers which have handled the message. It should be easy to see if your client's server is named in one of the entries. Note that the destination of an SMTP message is *not* shown in the headers, unless one of the intervening servers has added an 'Envelope-To:' header, and that's normally done on delivery to a POP3 server. The 'To:' header is *not* what is used by SMTP for delivery. As to the original problem, it's a bit difficult to see what's going on when no NDR is produced. This is why the email RFCs require NDRs, which make SMTP a reliable (i.e. accountable) protocol. These days, if email disappears silently, it's usually being eaten by a spam trap somewhere. If the sending company are keeping SMTP logs, they can confirm whether another mail server accepted the message, and can then ask the owners of that server what happened to it. |
| Posted: 01 May 2008 04:06 PM PDT So far so good, you can now use the Exchange Task Wizard to Move Mailboxes from AE to AEC. When finished follow, http://mchangeteam.com/archive/2006/11/16/431531.aspx. Turn off AE for about one week to insure everything is working properly then you can uninstall Exchange from the Server. No need to change the server name. -- John Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2008 Microsoft Certified Partner "msw" <com> wrote in message news:phx.gbl... |
| Posted: 01 May 2008 01:32 PM PDT Thanks Mark "Mark Arnold [MVP]" wrote: |
| Tool to extract the Signature Block from a message Posted: 01 May 2008 11:02 AM PDT On Fri, 2 May 2008 07:43:00 -0700, Bob C. <microsoft.com> wrote: Gosh, I can't help you with that. I don't think even the most intelligent of event sinks would say "On an inbound message take away the last n lines (because that's the disclaimer) and then read the next 5? lines going upwards and try to make sense out of it based on the fact that: the bottom line is a mobile number, or a fax number, or, err a corporate logo etc. etc up and up the 4th, 3rd etc lines. Why do YOU want to extract this information? Can't you just create a PF for the people to store contact information in that then gets shared? WHat's your higher purpose here? |
| Exchange 2007 Message Tracking Parameters Posted: 01 May 2008 04:28 AM PDT SEND and RECEIVE events will contain the UTC timestamps of the time when Exchange first received the message. Other events may contain other values. 03 and 04 can be seen in RECEIVE events from StoreDriver source. -- Bharat Suneja Microsoft Corporation ------------------------ This posting is provided "AS IS" with no warranties, and confers no rights. Please do not send email directly to this alias. This alias is for newsgroup purposes only. "IT" <com> wrote in message news:phx.gbl... |
| Posted: 01 May 2008 12:52 AM PDT Dear Bharat Suneja, Thanks for your swift reply. I will study the various hints you marked. However, the simple fact that I have to search for the answer(s) on various locations does indicate that I am correct with my statement that (regarding malware) Exchange lacks a "comprehensive set of doentation bringing all points together". That is a pity because it is so important. Jan "Bharat Suneja [MSFT]" wrote: |
| "Meeting Request" Strange Behavior Posted: 30 Apr 2008 07:02 AM PDT Cool, thanks James! Clayton "Jamestechman" <com> wrote in message news:googlegroups.com... Can occur when the delegated account is deleted prior to removing the delegate from Outlook. There is a hotfix. Members of your organization may receive a non-delivery report if your delegate's mailbox object is removed from Active Directory before you can remove the delegate in Outlook 2003 http://support.microsoft.com/kb/909638 James Chong (MVP) MCITP | EMA; MCSE | M+, S+, Security+, Project+, ITIL mchangetips.blogspot.com On Apr 30, 11:38 am, "Clayton Sutton" <com> wrote: |
| cheap backup solution for e2k7 on server 2008? Posted: 29 Apr 2008 10:51 PM PDT cool, thanks. I'll try it maybe over the weekend and report back... "Martin Blackstone" <com> wrote in message news:Osrj%phx.gbl... |
| Posted: 29 Apr 2008 06:19 PM PDT Sorry for the late update! Thankfully you guys were right and my coworker had unintentially misinformed me. It was the alias causing part of the issue because the directory sync was originally setup using our display names to generate the alias on the other AD system, which obviously wouldn't work as we have spaces in the displayname. The other part was DNs were/are getting changed after a user import causing subequent updates to not work and it would duplicate people in the GAL of our partners as the original user was no longer their so any import with a change in it essentially created a whole new contact in AD. This is still being investigated, but it looks like every forest with the problem was or is running the Active Directory Connector. Knowing that and reading this... http://support.microsoft.com/kb/269843/en-us [Begin Cut/Paste] SYMPTOMS When the Active Directory Connector (ADC) matches a Microsoft Exchange Server 5.5 mailbox to a user account in the Microsoft Active Directory directory service, the user account becomes a mailbox-enabled user account. After the mailbox and user are matched, if any attribute is modified on the Microsoft Exchange Server 5.5 mailbox, the ADC updates the active user. It automatically overwrites the CN of the Active Directory user with the Exchange Server 5.5 display name. The CN attribute is also known as "Full Name." This attribute appears on the General tab on the properties of a user object within the Active Directory Users and Computers Microsoft Management Console snap-in. [End Cut/Paste] .... it seems like it not only applies to Exchange 5.5 mailbox, but potentially also Mail Enabled Contacts. PSS is investigating if this is true or not. I probably botched the explanation, but I've not been involved in the troubleshooting so I am doing the best I can here. :) Thanks for keeping me honest, I'm glad it wasn't what I originally thought it to be. "Brian Day" <net> wrote in message news:com... |
| email bounced if sent to group of people Posted: 28 Apr 2008 09:34 AM PDT well, here is why this is happening very strange (see link) but at least we know there is nothing we can do until this is resolved by easydns and Bell. I originaly said "email send to group" because this is how it looks like as we were troubleshooting this but now we know it is random regardless how meny email addresses is included in TI or CC http://blog.easydns.org/archives/206-Bell-Canada-Bellnexxia-mail-delivery-problems-return.html "John Oliver, Jr. [MVP]" wrote: |
| Optimizing SBS 2003 Excange? Intermittent Connection Issues!! HELP Posted: 28 Apr 2008 08:22 AM PDT To clairfy sluggishness, by this I don't mean network wise i mean when i'm logged into the server it can be quite slow. That's because Exchange is eating quite a bit of memory. I did run the Exchange BPA and will do the SBS one today as well. Thanks to the BPA for Exchange I was able to tweak the heck out of Exchange, and from what I've seen it seems to be running a bit better now. One of the bottlenecks was that the # of connections for SMTP in/out was set quite low (like 20 or so) and we have 30 people connecting at any given time. So I bumped some #'s up to the reccomended settings, and also turned off reverse dns as that seemed to be an indicated bottleneck. So far, so good! We'll see what the big guy says when he comes in next. "John Oliver, Jr. [MVP]" wrote: |
| Can Excange 2007 handle thousands of emails at once? Posted: 28 Apr 2008 04:11 AM PDT On 28 apr, 16:24, Michael Dragone <no.e-mail=less_spam> wrote: Thank you for your answers. I'm sending the emails one by one (batch-driven), because every email will have a different body. That's why I wanted to be sure that my Exchange server won't crash, or "terminates unexpectedly" when it receives that many e-mails at once. Therefore I don't think the emails will be recognized as spam, but nevertheless I will do a test mailing to 500 customers to make sure they don't. Thanks again for your fast responses. Christian |
| Posted: 28 Apr 2008 02:40 AM PDT efeb <microsoft.com> wrote: I'm not sure what that tickbox does in Outlook, but AFAIK it still requires SSL to connect. You need to use it. |
| Firewall Ports Require behind firewall port Posted: 26 Apr 2008 12:29 PM PDT You are not understanding this fully so I will explain further, only ports that should be open on your Firewall to your Exchange Server is port 25 and 443. VPN has nothing to do with this. If you decided to have remote VPN Clients connect to your LAN to use Outlook then your VPN tunnel should be passing all traffic so the clients will connect with RPC, similar to local Outlook Clients on your LAN. If this is working properly you should be able to ping your Exchange Server by FQDN and get a reply. As I suggested in my last post, you can eliminate the VPN Client all together if you implement RPC over HTTPs. -- John Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2008 Microsoft Certified Partner "news.microsoft.com" <com> wrote in message news:phx.gbl... |
| Event IDs 7031 & 7034 on Exchange 2003 Server Posted: 24 Apr 2008 11:13 AM PDT Andy, I do, both just the normal AV Client and the SMSME mail AV. I have excluded the proper directories, I believe, from the AV client Realtime scanning. "Andy David {MVP}" wrote: |
| 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., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
