Exchange 2010 mail storing Architecture

hi I just need to know what is the method that exchange server 2010 use to store the mail,
if I elaborate more when one user sends a mail to few people in the same organization does that mail copies to every users mail box or exchange just uses the referencing method to one single mail.
please help one of my clients using DAG in exchange 2010 and their mail box sizes increasing rapidly. I need to provide a solution to them. please let me know if you want more details
please help me with some links that reveals about these in detail.
thanks In Advance.

Every mailbox will get a copy of the message. Single Instance Storage (SIS) is history.
Dude, Where's My Single Instance?
http://blogs.technet.com/b/exchange/archive/2010/02/22/3409361.aspx
Martina Miskovic

Similar Messages

  • My macbook air cannot sync with my office microsoft exchange 2010 mail server

    My macbook air cannot sync with my office microsoft exchange 2010 mail server.
    It used to work perfectly, and then I lost connection and was never able to establish one. I re-istalled my e-mail account several times, no success.

    I am sure all of you got your email issues sorted out by now but i was having trouble settings up exchange email on my Iphone 5S, and the problem i found was to go to settings, icloud, then log into icloud with your apple id first (before setting up the exchange email).  Once i logged into my icloud account on my Phone 5S, the exchange server email starting working and synching right away.
    to confirm this worked, i even deleted my email account and deleted my Icloud accounts both from my iphone was able to simulated the same exact problem (exchange server would not sync with my Iphone 5S) until i logged back into my Icloud account on my 5S.
    Again once i logged into Icloud, the exchange server issues went completely away.
    Just wanted to post this so anyone else having the issue could see.

  • SPAM and Exchange 2010 Mail-enabled Public Folders

    Is there a way to determine if mail sent to our Exchange 2010 mail-enabled Public Folders by our customers is ever rejected because it was tagged as spam? The concern is that we might not be receiving some email. We rely on the mail-enabled PF's
    heavily, but since they aren't a mailbox there is no Junk E-mail folder to check. We do not have the resources to check EOP on a regular basis throughout the day, and the customer would not get an NDR or anything like that.
    HDL

    Hi,
    You can consider to use Message Tracking tool under EMC -> Toolbox to track these messages.
    Understanding Message Tracking
    https://technet.microsoft.com/en-us/library/bb124375%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
    Search Message Tracking Logs
    https://technet.microsoft.com/en-us/library/bb124926(v=exchg.141).aspx
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Exchange 2010 mail routing

    How did you migrate to Exchange 2010?  Did you not migrate the groups or did you set everything up from scratch?

    Hi,
    We have a new exchange server installed in our domain and we are moving all our mail transmitted through epicor to this server, and I am experiencing this error
    There is problem sending customer order confirmations by email. The
    message says the mailbox is unavailable. The server response was 5.7.1. Unable
    to relay
    Now I know there is nothing wrong within Epicor, What is wrong with the Exchange server? 
    Is it something to do with the receive connectors in the HUB transport I have got set up?
    All other mail flow is working correctly
    Regards,
    Ian
    This topic first appeared in the Spiceworks Community

  • Exchange 2010 Mail Submission Service Logging

    Hi,
    Is there a way to log all submitted messages from outlook clients (online mode) so I can see what is happening to messages that are getting stuck in the Outbox from the server's perspective?
    Thank you.

    If you look at the logging section in this post
    http://blogs.technet.com/b/rmilne/archive/2013/11/20/exchange-2010-tweaks.aspx
    add key="LoggingTag" value="ConnectDisconnect, Logon, Failures, ApplicationData, Warnings, Throttling" />.
    You can also add ROP logging, which are the individual Outlook commands sent, by adding the tag to the above line.
    This gets *VERY* busy.  *VERY* quickly, so maybe try this out on a test box first to see what that gives you.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 - Mail redirect

    Hello,
    i want to set up my Exchange Server 2010 to pass ALL e-mails he recives on 192.168.137.102:25, to the "Filter" which is listening on IP address 192.168.137.103:25, then after it filters the email (for example delete some vulgarisms) it will
    send them to my Exchange listening on 192.168.137.102:10025 and then the email will be send to users mailbox.
    I've already Set up:
    - send connector: Address space: SMTP *,  Smarthost: filter.<my_domain>, Source server: <my exchange>
    - recive connector: listening All Available IPv4 on 10025, Recive mail from: 192.168.137.103 (my filter IP).
    However it don't work propperly. My Filter don't see any traffic, so no data is passed to it from the Exchange. Could you please tell me what else i should configure to have this thing works as i want it to?
    Thanks,
    Michael

    Here you go:
    http://blogs.technet.com/b/exchange/archive/2013/01/21/how-to-write-an-exchange-2013-transport-agent.aspx
    https://msdn.microsoft.com/en-us/library/office/dd877033%28v=exchg.140%29.aspx
    http://www.c7solutions.com/2012/10/creating-simple-exchange-server-html
    DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

  • Exchange 2010 - Mail Database Recovery after Database Portability Applied

    Background:
    We had a city-wide power failure  at Office A and as a result Exchange Server A (ES-A) was taken offline for an extended period of time.  The last good backup of ES-A-DB was from the previous business day.  The DR plan was enacted and the
    ES-A mailbox database (ES-A-DB) was recovered to Exchange Server B (ES-B) as ES-B-DB2.  Keeping in mind that a days worth of emails still reside on ES-A-DB.
    Process:
    I employed the database portability method when restoring the ES-A-DB to ES-B-DB2 at Office B.  I rehomed the exchange users in active directory to now use ES-A-DB2.  Users are working fine, activesync worked without issue.  All is well.
    I now face the situation where power has been restored to Office A and the server is available.  I have NOT turned this server on yet as I am not sure what the net affect will be on ES-A and ES-A-DB.
    The primary goal of the business is to recover the mail items from the missing day that was not backed up and recovered to ES-B-DB2.  What would be the best way to do achieve this objective?  
    This is what I am thinking, though its all theoretical since I've never been in this situation.
    - boot the Exchange Server with the network card disconnected
    - Dismount ES-A-DB from ES-A
    - Remove ES-A-DB from Exchange Org on ES-B
    - Process logs and put the ES-A-DB in a Clean state
    - mount as recovery database
    - copy differential mail items to ES-B-DB2 mailboxes
    Anyone have insight on this?
    Thanks for your help in advance.

    No need to dismount , remove from the org or boot the server w/o a NIC. The association between Exchange and the user is in AD and you already changed that when you set the new database with database portability.
    I would just follow the instructions for restoring back to their current production mailboxes (DB2).
    http://exchangeserverpro.com/restoring-mailbox-exchange-server-2013-recovery-database/
    Try it with a sample mailbox or two and see how it handles the conflict resolution for duplicates.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2010 Mail Enabled Distribution Group Won't Receive from External Address

    Let me pre-empt the usual first response: yes, I've unchecked "require that all senders are authenticated" on the Message delivery Restrictions properties of Message Delivery Restrictions. I cannot get a message from an external mail server to
    send to an internal mail-enable distribution group. It's working internally. I've checked our ironport and the message is being sent to exchange (at least I think it is).
    How can I troubleshoot this?!
    tfgeorge

    Ironport is definitely sending this email to exchange. Please read:
    06 Jun 2011 08:53:20 (GMT -05:00)
    Protocol SMTP interface Main Interface (IP Gateway IP) on incoming connection (ICID 17720578) from sender IP 65.54.190.154. Reverse DNS host bay0-omc3-s16.bay0.hotmail.com verified yes.
    06 Jun 2011 08:53:20 (GMT -05:00)
    (ICID 17720578) ACCEPT sender group UNKNOWNLIST match sbrs[-1.0:6.0] SBRS 3.0
    06 Jun 2011 08:53:20 (GMT -05:00)
    Start message 2136865 on incoming connection (ICID 17720578).
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 enqueued on incoming connection (ICID 17720578) from
    [email protected].
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 on incoming connection (ICID 17720578) added recipient ([email protected]).
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 contains message ID header '<[email protected]>'.
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 original subject on injection: TEST
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 (1471 bytes) from
    [email protected] ready.
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 matched per-recipient policy DEFAULT for inbound mail policies.
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Spam engine: CASE. Interim verdict: Negative
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Spam engine CASE. Interim verdict: definitely negative.
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Spam engine: CASE. Final verdict: Negative
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Virus engine Sophos. Interim verdict: CLEAN
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Virus engine. Final verdict: Negative
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 queued for delivery.
    06 Jun 2011 08:53:20 (GMT -05:00)
    SMTP delivery connection (DCID 1658840) opened from IronPort interface 100.100.100.100 to IP address 100.100.100.100 on port 25.
    06 Jun 2011 08:53:20 (GMT -05:00)
    (DCID 1658840) Delivery started for message 2136865 to
    [email protected].
    06 Jun 2011 08:53:21 (GMT -05:00)
    (DCID 1658840) Delivery details: Message 2136865 sent to
    [email protected]
    06 Jun 2011 08:53:21 (GMT -05:00)
    Message 2136865 to
    [email protected] received remote SMTP response '2.6.0 <[email protected]> [InternalId=919833] Queued mail for delivery'.
    tfgeorge

  • Exchange 2010 Mail Security TLS with HSBC

    Dear all,
      I have setup an all-in-one exchange server without edge server role. However, it is needed to have TLS mail communication setup with HSBC. May I know what exactly configuration do I need? Do I need to implement an edge server with public cert?
      Can I enable TLS without edge server and with self-signed cert?
    Thanks a lot
    Best Regards,
    Elroy

    Hi,
    it's not possibile to connect on TLS with HSBC without a public CA certificate. Not selfsigned is permitted.
    No edge server it's mandatory.
    Import certificate on Exchange computer store and set it to use with SMTP service:
    Enable-ExchangeCertificate
    -Thumbprint CERTTHUMBPRINT -Services SMTP
    You need to create a custom send connector, complete domain scope with all HSBC domain and set bridgehead Exchange server. After the send connector creation set the Enforce TLS:
    Set-SendConnector CONNECTORNAME -RequireTLS $true
    Be careful to default internet receive connector that accept TLS connection.
    This is a good site for testing: https://www.checktls.com/
    Bye bye.
    Raffa!

  • Exchange 2010 - Mail contacts - Set as Reply property

    As mail contacts will probably use an external and unknown server to send replies for their mail. I don't understand the purpose of this property for mail contacts ?
    Is it only here because one console developer have missed to gray it out or is there a real utility ?
    Thank you for that clarification !

    Hello,
    Based on your description, I understand that you create mail-contact with two e-mail address:[email protected] and
    [email protected] (set as external address). You want to understand that if the mail-contact reply to these mail from his private mail system, the sender mail will be
    [email protected] and not
    [email protected]
    If so, I consider when the mail-contact reply to these mail from his private mail system, the sender is
    [email protected]
    Based on my experience, you can set any SMTP address as external address, but the address must be resolved.
    If I have any misunderstanding, please free let me know.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Exchange 2010 coexist with exchange 2013

    Hi All ,
    Planning to have a coexistence scenario in my environment which is mentioned below
    Exchange 2010 - ambiguous url in place - OA enabled 
    For mapi/rpc traffic - mail.domain.in -  exchange 2010
    For https traffic - mail.domain.in - exchange 2010
    mail.domain.in will get resolved in to cas array in exchange 2010 .
    After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
    exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
    just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
    Note : 
    On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
    Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
    Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
    exchange server via exchange 2013 server.
    question : I would like to know above mentioned scenario is possible or not ?
    On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
    So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
    All of you tell me your valuable suggestions.
    Regards
    S.Nithyanandham

    Hi,
    Going Straight to the point... and answering your question...
    The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
    As per Exchange Team...
    In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
    breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
    their DNS cache expires after the shared FQDN is moved to CAS 2013.
    As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
    change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
    URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
    on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
    fix existing Outlook clients with the old value in the server field. 
    So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
    Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
    Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
    Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
    Outlook 2013: 15.0.4420.1017 (RTM or later)
    I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
    As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
    Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
    From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx> 
    Hope it can help you!
    Cheers,
    Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

  • Disater Recovery for exchange 2010 plan.

    Hi All,
    Happy New year 2014 ....
    we have running with exchange 2010 R1 with DAG enabled. we have below mentioned setup in our exchange server.
    Main site.
    Active directory server ( Primary DC, additional DC in our main site)  installed in Hyper V  host. installed exchange 2010 mail box role in another Hyper V host.  installed the CAS& Hub role in another virtual host and installed the Exchange
    edge role in another physical server.
    DR Site
    Active director server( ADC) installed in Hyper V host. installed the Exchange 2010 mailbox,Hub,Cas server role in a physical server. installed the Edge Server in another physical server.
    At present we have enabled the failover DAG  for both our Mail box servers and its working perfectly when the primay mail box server down. we have run some commands to transfer all my exchange 2010  to point through our DR Site. so its take
    some of the minutes of down time happened in our mail flow.  we are planning to avoid that downtime. we  are find for the solutions like  if the primary site down  the DR will need to automatically up. it will be appreciate that any
    one  provide your suggestion to achieve this without affecting the  our current setup.
    Jags

    Hello,
    Kindly find the 3 types of plan for Exchange 2010 DR site. You can check all 3 plans and select as per your requirement.
    1. Rebuild an Entire Database Availability Group plan
    http://technet.microsoft.com/en-us/library/gg513521.aspx
    2. Site Resiliency in Exchange 2010
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html
    3. Exchange 2010 Cross Site DAG Disaster Recovery: Data Center/AD Site failure Part 1
    http://msexchangeguru.com/2012/10/25/exchange-2010-dag-dr/
    Deepak Kotian. MCP, MCTS, MCITP Exchange 2010 Ent. Administrator

  • Exchange 2010 Edge Transport - Not being detected by SCOM agent?

    All,
    I recently installed the SCOM 2007 R2 agent onto our Edge Transport server for Exchange 2010.  Our architecture is pretty simple.  We have a DMZ network where I have a SCOM 2007 R2 Gateway server and our Edge Transport server.
    Essentially it goes like this:
       Edge Transport Server Agent <-> Gateway Server <-> SCOM RMS server
    I have the Exchange 2010 and the FOPE for Exchange 2010 MP's loaded on our RMS server.  When I loaded the SCOM 2007 R2 agent onto our Edge server, the agent discovered it had FOPE and does reflect as such on the RMS server, but it did not seem to pick
    up that it was also the Exchange Edge Transport role.
    I looked on the RMS server in the Authoring -> Object Discoveries and the Edge transport is set to discover, so I am a little stumped as to why the agent didn't discover the role.
    Any suggestions where to look next?

    Just a little more detail on this.  I've been working on this exact issue for probably 3 weeks with an engineer. 
    This issue is actually a bug in the Exchange 2010 MP. 
    How is it a bug exactly?  Well, the MP is looking for the Active Directory site that the Edge Server is a member of... let's think about this, the Edge server is NOT domain joined, and as such, shouldn't have an active directory site. 
    Additionally, the regkey path referenced above is incorrect, though it seems that numerous others have figured that out on their own as well.  The correct regkey path should be:
    hklm>system>currentcontrolset >services>netlogon>parameters
    So sure, this "fixes" the issue - but the real issue is that the MP is looking for an Active Directory site, on servers that aren't a member of an active directory site. Kind of a BIG oversight by the MP authors in my opinion.
    I'm sure there are plenty of orgs relying on SCOM to monitor their Exchange 2010 implementations that don't even realize that their Edge servers aren't being monitored for the Exchange roles.

  • Apple Mail 6.2 Exchange 2010 Delete Fail

    When deleteting an email in Apple Mail 6.2 setup to use Exchange 2010 with MAPI, the following error message is displayed:
    The message "X" could not be moved to the mailbox "Trash folder name".
    An error occurred while moving messages to mailbox "Trash folder name".
    To reproduce this problem I loaded a mailbox with 30k of emails. I then deleted 4000 messages, and while the client was still syncing (visibly you could see it syncing the activity window) - I deleted some of the same messages again.
    The sync process stopped, the activity window stopped showing any activity and my emails which were previously marked for deletion remained visible.
    Now when I try to delete the emails I previously deleted, I receive the error as above and the messages are not deleted.
    If I delete other messages that were not previously marked for deletion I do not receive the error.
    To remove the messages that were causing the error I had to "Command-X" to cut them from the folder and bypass the trash.

    Hi Andrew,
    I tried to understand your message but failed to. I'm sorry. Just clicking "rebuild" worked for me to restore behavior that hadn't been working. It only took a few seconds.
    That said, it was only days later that all of my correspondance stored on the Exchange server disappeared, and 123Together, my Exchange service provider, said "Since you are on a Mac the database may gotten corrupted and synched to the server that is why the data in the mailbox and subfolder you may not see. We can have our admin do a restore of the mailbox as we can go back for a restore point up to 5 days, there is a admin fee of 160.00 hr anywhere from 1-3 hours of work please let us know if you would like to proceed." I was not happy.
    So I probably agree with what you are saying!
    Larry

  • Unable to SEND mail using Activesync in Exchange 2010 server on iPhone or Windows Mobile 6.1

    Hi All,
    We've been setting up a new SBS 2011 server for a client this week. Everything is working, except the staff have 4 x iPhones to connect with Exchange ActiveSync.
    There are 2 x iPhone 4's and 2 x iPhone 3Gs's. We can setup the Exchange accounts on each of the phones and they are all able to sync mail and calender etc with the server.
    The problem we have is when any of them try to send mail from the phone, it gives an error : "Cannot Send Mail - An error occurred while delivering this message" and it sits in the outbox on the phone.
    The newsgroups and forums are littered with people having issues with IOS4 and Exchange 2010 but most of these are from June-August 2010 when IOS4 version was around 4.00 or 4.01
    A lot of these people had iPhone 3 handsets running with IOS 3.1.3 which worked with Exchange 2010 but when they upgraded to IOS 4, they had this problem sending mail.
    It seems that for most of them, the fix came in the form of IOS version 4.1 which fixed the send issue for them.
    We have a variety of Hansets and IOS versions (including an iPhone 3Gs running IOS 3.1.3) but are unable to send mail from any of them:
    iPhone 3Gs    IOS 3.1.3
    iPhone 3Gs    IOS 4.3.3
    iPhone 4       IOS 4.3.3
    iPhone 4       IOS 4.3.5
    I was surprised that the iPhone 3Gs running 3.1.3 was unable to send either as nearly all the forums etc I read with this issue said the iPhone 3's worked with that IOS version.
    Today we used a test iPhone 4 handset from our office to connect to an almost identical Small Business Server 2011 we setup two weeks ago for another client.
    The test iPhone 4 was able to connect, Sync and Send email on that server but when set it to connect to this SBS 2011 server, it gets the "Cannot Send Mail" message the same as the others. So clearly the handset is working (on the other server at least),
    it must be something misconfigured in this Exchange server right?
    We ran the Exchange Remote Connectivity Analyser on the Exchange server and got green ticks across the board.
    Outlook Web App and Outlook Anywhere both work normally. Everything we can test on the Exchange server works except sending from any iPhone.
    Having said all that, I just setup a Windows Mobile 6.1 handset to sync with the Exchange 2010 server as a test, and it appears to have the same issue.
    It will connect & Sync Mail, Contacts and Calendar but if trying to send an email from the phone, it will just sit in the outbox.
    Does anyone have some insight into what the problem may be?

    Further to this .. I found the solution on a MS Exchange 2010 support forum.
    It was not a certificate or firewall issue, looks as thought the “Accepted Domains” in Exchange Mgmt Console –
    Org Config – Hub Transport cannot have any spaces in the name field.
    I had some spaces and the emails were not downloading fully and able to send. Once I removed the spaces from the Name field and
    restarting the Exchange and IIS services emails were now being sent and received ok.
     Check
    out :
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrmobility/thread/321eae51-9cbd-4a5e-85c1-68d8f7b523c3
     This
    is good one to add to your knowledge bank in case you come across it in the future.
    Rgds Gerry

Maybe you are looking for