Symantec Mail Security with Exchange 2007 (Emails with Attachment missing)

HI, i need help here
I have Win 2008 with Exchange 2007 and Symantec Mail Security. Symantec was working fine until the license expired but it was still fine until yesterday, we realize that we cannot receive email with attachment. after stopping the symantec services, mail
flow went back to normal. We then remove the program from the control panel.
Then i found that i cant retrieve or find those emails that was sent to us during a period of ard 6 hours. i tried looking the the Symantec quarantine folder but it is not there.
Can someone point to me where should i look for the missing mails? When i do a mail flow troubleshoot i can see the logs that it is sent to the mailbox, but from users's outlook inbox, there is no email ??
Much Appreciated

Symantec's support group should be able to tell you what happened.
--- Rich Matheisen MCSE&I, Exchange MVP

Similar Messages

Spam Protection for Email showing Critical for Exchange Server 2007 after installing Symantec Mail Security for Microsoft Exchange

Hi there,
I have SBS 2008, and I have recently installed Symantec Mail Security for Microsoft Exchange version 7.5 but when I take a look on Windows SBS Console under Security, it shows "Spam Protection for Email Critical Exchange Server 2007" However,
when I open the SMSME it shows running well with no problem..
Any Suggestions???
Thanks

Hi,
Would you please let me confirm whether all functions (which are related to Exchange Server) run as normal? Just
a confirmation, thanks for your understanding.
Please run
SBS BPA and check if find relevant issues. In addition, please refer to GaryD9’s suggestion in following thread and check if can help you.
SBS
2008 & Forefront Protection 2010 for Exchange - SBS Console Error
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

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)

Does anyone know how to get apple mail in Lion to connect with Exchange 2007?

Does anyone know how to get apple mail in Lion 10.7.2 to connect with Exchange 2007? It worked perfectly with Snow Leopard... upgraded to lion and it won't work. We use Exchange 2007 with SP 3 and Rollup 4. Won't connect... and I can't get Apple to give me any direction.

We finally got it to work today. We had to call and pay for the microsoft support service, but the issue was on the server end. We had to go into the iis manager... went to sites... when to default website...and changed the SSL settings for Auto Discover, EWS Exadmin, echange, exchweb, owa... and the rest..
Change the settings to ignore client certificates.
Problem solved. Can finally send and receive.

Outlook 14.4.8 not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox"

Outlook 14.4.8 on iMAC Retina and Yosemite 10.10.2 is not synchronizing with Exchange 2007 anymore (shows "downloading" but no new messages shown in inbox".
Accessing Mails with Webbrowser and from Windows Outlook is working correctly.
All Macs (also the ones with OS 10.6.8) do not anymore show any new messages in inbox.
Restarted Server, tried to disable autodiscover on macs and deleting/adding account and repairing database does not fix the problem. Also restarted server several times.
We have the same problem on 2 imacs retina with yosemite and on 2 mac pro with 10.6.8 and different office 2011 versions.
i tried to configure the exchange account in apple mail on yosemite and it also states "connected" and does list some folders but no new mails are getting in.
Windows clients and outlook on them works and syncs fine, and also when connecting via webbrowser at owa it must be a mac-specific/webdav issue.
exchange 2007 Sp3 Version 8.3 (bild 83.6) and Update Rollup 15 for sp3 (automatic updates "HIGH" for server and clients)
there is one update popping up again and again even after everytime successull installation: Windows Mlicious Software Removal Tool x64 - October 2010.
i tried to configure a new user with empty mailbox and configured it with microsoft mail (mac - yosemite) as exchange and was able to send a mail from there (even if quite delayed).
but there are not coming in any mails.
same exchange accounts triggered by imap do work and also via owa.
Exchange Accounts in Outlook for MAC and also in Mail (Yosemite) do show the folder structures but there is no mails showing up. I can send mails from the exchange accounts created but they seem to be processed with a delay of like 15minutes and outlook
is giving error "end of file reached" but messages are send after some time.
Does seem like EWS is extremely slow, to slow perhaps to sync and therefore ending in timeout.
Also i cannot reach the server from externally over ssl https 443. if testing port 443 of exchange from outside the port seems closed even firewall settings of sbs 2008 and sonicwall ports are correctly open.
could it be there is something in regarding webdav which is very slow and leading to timeouts ?
in application log i do have the following two information events every few minute:
The Exchange Web Services started successfully. Event ID 1
and
Process STORE.EXE (PID=3688). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
SERVER.org.local CDG 1 7 7 1 0 1 1 7 1
Out-of-site:
Errors in Application log:
The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section
The entry <C:\WSUS\WSUSCONTENT\CONTENTFOLDERACLSCHECK.TXT> in the hash map cannot be updated.
An exception Microsoft.Exchange.Data.Storage.ConversionFailedException occurred while converting message Imap4Message 69447
Also outlook 2011 clients are asked by time to time to reenter pwds and errors like "connection is closed. 13"
Faulting application taskeng.exe, version 6.0.6002.18342, time stamp 0x4cd34898, faulting module ntdll.dll, version 6.0.6002.18881, time stamp 0x51da3d16, exception code 0xc000071b, fault offset 0x0000000000082445, process id 0x3288
Certificate Services Client Provider pautoenr.dll raised an exception. Exception code 3221225477.
Backup Exec:
FULL_BACKUP -- The job failed with the following error: A failure occurred querying the Writer status.
Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The
error returned from CoCreateInstance
Exchange VSS Writer (instance 2d932ef8-6319-4ab8-a45f-1242480b44ad:15) failed with error code 1295 when processing the backup completion event.

Hi,
Since Outlook running on Windows works well, it seems an issue on the Mac side. I suggest ask Mac for help so that you can get more professional suggestions.
More information for your reference:
Please try to verify whether there is any expired certificate from the computer personal store.
If it is the case, please remove them.
Thanks
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]
Mavis Huang
TechNet Community Support

Migrate SBS 2008 with exchange 2007 to office365

Hi, we have a sbs 2008 with exchange 2007 the boss got the idea to move the E-mail to office 365, i have done some research but still have some questions, now i am not an expert on exchange, could some one tell me if this is a straight operation going from
exchange 2007 to office 365, is it supported or do we have to move to exchange 2010 and then to office 365?
Thank you very much in advanced.

Yes, going from Exchange 2007 to Office 365 is supported. You want to run a Migration.
Check out this link for exact instructions on what to do for the migration:
http://help.outlook.com/en-US/140/ms.exch.ecp.emailmigrationwizardexchangelearnmore.aspx
Then, when you are ready to setup Outlook with Office 365, check out this link to make Outlook use the public Autodiscover rather than SBS Autodiscover:
http://www.mcbsys.com/techblog/2011/08/using-office-365-in-an-sbs-2008-environment-take-2/
I just did a cutover migration from SBS 2008 to Office 365 using both these websites and it went off very nicely.
Good luck on your migration.
Oh, and if you only use Office 365 for email, it is $4 a month per user.

Migrate SBS Server 2008 with Exchange 2007 to Exchange 2013

I have looked at the documentation to co exist 2007 and 2013. However I am concerned as it talks about changing the dns name to something like legacy, as the dns name that is used for outlook to connect is the name of the server. So here
is my question. Would I have to change the name of the actual server itself? and if I choose not to, and use a new name for the 2013 server, such as mail, would the users that get migrated, would they automatically update the
name change? Also note the SBS server with exchange 2007 is also their file server at present but will be changing.

Hi ,
Thank you for posting your question in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback
on our support quality, please send your feedback here.
Andy Qi
TechNet Community Support

ICal still does not sync with exchange 2007 in Lion

Dear,
In Snow Leopard, iCal was not syncing with Exchange 2007. I read a lot of things on this and it all led to recurring events. Indeed, after deleting them, things started to work. But I cannot delete recurring events! I need them!
Seeing that there was soo much talk on this all over on apple, I assumed that Apple would fix it. Instead, all we're seeing is some enhanced UI.
Can somebody at Apple please make sure that this thing finally gets fixed? Really, how hard can it be, knowing that the hardware based i devices can sync without any trouble?
Just for extra information, so you know what direction to look for:
I have Windows SBS 2008 in Dutch language. Timezone is Brussels. Exchange 2007 and all updates.
The system is running a self signed certificate
Outlook works fine on the Mac. I don't want to use Outlook on the Mac but am forced to at the moment.
Mail/Addressbook sync fine. Only Outlook doesn't!
I did try deleting recurrent events and this worked for a day. Basically stopped working I think when I added again those recurring events.
There are some errors in the console:
21/07/11 11:42:36,563 iCal: Couldn't find an NSTimeZone to match the SerializableTimeZone
21/07/11 11:42:36,563 iCal: WARNING: Failed to find TimeZone Identifier for Windows MeetingTimeZone: (GMT+01:00) Amsterdam, Berlijn, Bern, Rome, Stockholm, Wenen
21/07/11 11:42:36,580 iCal: error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal kan de activiteiten in de agenda 'Agenda' niet bijwerken." UserInfo=0x7fbe94adb8b0 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7fbe94102d40>, NSLocalizedDescription=iCal kan de activiteiten in de agenda 'Agenda' niet bijwerken., NSLocalizedFailureReason=De account 'Exchange' kan momenteel niet worden bijgewerkt.}
Please fix this,
Guido
Message was edited by: guido4096. Added error message

Hi all,
I do have exactly the same problem.
But I am adding a new flavor, but I can not understand it.
I've setup two Exchange calender connections. Both servers are inhouse. The setup of the Exchange servers are most likely the same.
But one works and one not! How could this be explained?
I like to express my deep disappointment about iCal and partly Apple Mail. It is unbelievable for me, that years after Apple's cooperation with Microsoft there are still such problems.
I like my Macbooks and I certainly have the absolutely full bandwidth of all Apple products in my household and companies. But I think I have to go back to Microsoft and Sony Laptops in the near future.
Although this kind of bugs are small one's, but the hurt constantly. Apple - please fix that.
Here just for the interested reader is my console error message:
3/15/12 11:51:29.819 AM iCal: error = Error Domain=CalExchangeErrorDomain Code=-11 "iCal can’t refresh events in the calendar “Kalender”." UserInfo=0x7f856d4bddb0 {CalFailedOperationKey=<CalExchangeSyncFolderItemsOperation: 0x7f856c5ca060>, NSLocalizedDescription=iCal can’t refresh events in the calendar “Kalender”., NSLocalizedFailureReason=The account "DR InfoDyn" currently can’t be refreshed.}

Exchange 2007 EXCDO 8206 error in Exchange 2007 SP2 with Rollup 4

Dear sir,
    We have a problem on Exchange 2007 Server. When user use OWA to access web mail calendar, server event log will show EXCDO error 8206:
Calendaring agent failed with error code 0x8000ffff while saving appointment
Type: Error
Event ID: 8207
Category: General.
     Moreover server becomes working in very slow web mail response during any user click web mail calendar.   Server performance return back after error message appeared in event log.
It doesn't has problem if using Outlook to access mailbox calendar.
Any suggestion to fix it ?
Joe

Hi Joe,
We are also finding the same issue with getting that EXCDO error. The problem stemmed when users noticed some previously accepted appointments disappeared (As I suspect you discovered with your users).
The workaround has been to get the user to accept the appointment again by going into deleted items, this seems to add the appointment as it should have the first time.
We have done the following but it didn't fix the problem:
Disabled extra SEP features on the clients - No Change
Disabled non-essential Outlook add-ons - No Change
Removed BES Express and CDO MAPI From Exchange server - No Change
Disabled MS Defender on Exchange - No Change
Fixed any Public folder errors - No Change
Disable Window services WSS and UNC sharing feature in Active Sync - No Change
Also ensured Autoupdate and auto process was enabled for affected users - No Change
I'm going to try the reg change mentioned in this thread but other than the built in MS Defender we don't have anti-virus on our mail server.
At first we thought it was Active Sync as it only seem to impact those with a A/S device, but now it's intermittent for other users using Outlook.  We are currently using Exchange 2007 SP3 with RU13. We are looking at trying an update
to RU14 but I am doubtful it will fix the problem. Did you have any luck finding a solution?
Thank you in Advance.

Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Team,
I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp. However, we have a coexistence environment with exchange 2007. When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
mailbox is still within exchange 2007, you get a blank login page. If you mailbox is in exchange 2013 then you successfully get the owa page for 2013. The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed. Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
the much needed mailbox lookup for a coexistance environment? A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.

Hi,
Try using AD FS claims-based authentication with Outlook Web App and EAC
http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2007 OWA with S/MIME installed Context Menu Disspear

Hi Guys,
We are experiencing the following issue with Exchange 2007 SP3 OWA when S/MIME control is installed:
Context Menu and Email Format are grey out
Does anyone know if this behavior is by design??
Best Regards
Federico Giampietri
Federico Giampietri Latamsupport IT Infrastructure Services

Hi,
I tested in my lab, Exchange 2007 SP3. The result is the same with you.
Without the S/MIME
control, Cut, Copy, and Paste from the Context Menu worked as expected and I could change email format . When I installed the
S/MIME
Control, the behavior with the Context Menu was reproducible, and email format is greyed out, but I could use Ctrl +X/C/V to cut, copy and paste.
I searched through internal channel and found this behavior is by design. However, as a workaround for choosing Cut, Copy, or Paste from the Context Menu, we can use Ctrl +X/C/V to cut, copy and paste.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2010 co-existence with Exchange 2007 issue NDR size Four Times then we send

Hi All,
I am facing some strange issues of NDR size four times then we send like if I send 1 MB message to internal OR external recipient then we receive 4 MB NDR.
Even we send one black mail with subject Test mail of 4 kb then we receive 16 kb NDR is it due to architecture change or something else.
Everything was fine with Exchange 2007 but facing this issues after we change the mail flow to Ex2010.
Any help really appreciated
Regards
Anand S
Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

Hi Anand,
From your description, the NDR size is four times than original message size. I would like to verify the following thing for troubleshooting:
How many people has this issue, only one or all the people?
If only one user has this issue, I recommend you move the user's mailbox to another mailbox database and check the result.
If all the people have this issue, please enable Pipeline tracing and see if there is any hint. If the issue persists, please install the latest Service Pack and Rollup and check the result.
Here is an article for your reference.
Enable Pipeline Tracing
http://technet.microsoft.com/en-us/library/bb125018(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Mail transport rule to block email with recipients in 2 different domains

Is it possible to set up a mail transport rule (Exchange 2007) to block or put on hold emails that are sent to recipients in more than one domain?
Eg if the recipients /cc/bcc are
[email protected];[email protected]
then the email is held for approval before sending
Can this be limited to only process from certain sending addresses?
If it can't be done in 2007 can it be done in a later version or can it be done in a non microsoft product eg Postfix
This topic first appeared in the Spiceworks Community

Hi,
From your description, you want to prohibit retired users from sending emails to
[email protected] If I have misunderstood your concern, please let me know.
In your case, these retired users are hosted on Exchange Online, this is Exchange 2013 forum. I would like to tell you how to achieve it on Exchange 2013.
I recommend you verify it on Office 365 forum. For your convenience:
https://community.office365.com/en-us/f/158.aspx
What's more, I would like to clarify the following thing:
If you prohibit A from sending email to B, B send an email to A and C, when A reply all this email, C still can receive this email, only A can't receive it.
Hope my clarification is helpful.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

I dont know my security questions and the email with those questione is not correct

i dont know my security questions and the email with those questione is not correct

I would contact Apple ID Support.
Apple ID Support

Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

I have exchange 2013 and 2007 set up in a coexist environment. At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007. I found an article
that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.) I would like someone to confirm
if the change I am about to make from doing research will help me in my situation.
Current Setup:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: NTLM
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod: Negotiate
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
New Settings I am considering based on research:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {NTLM}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {Basic}
Will this work and eliminate my popups?

Hi,
The following TechNet article indicates that:
“In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
Exchange Deployment Assistant. Specifically,
you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
Client Connectivity in an Exchange 2013 Coexistence Environment
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Regards,
Winnie Liang
TechNet Community Support

Symantec Mail Security with Exchange 2007 (Emails with Attachment missing)

Similar Messages

Maybe you are looking for