Personalize email disclaimer in exchange 2010 with alias?

Hello all,I would like to notify everyone in my email disclaimer that our email domain will be changing. I need the old email and the new email address for this. I can use %%Email%% but is there a way I can use the alias alone?
I think it can't be done unless I make a custom attribute or something or am I missing something?
some more info here: technet.microsoft.com/en-us/library/bb124352(v=exchg.141).aspx#ADAttributes (this is a link but I am not allowed to post it)
Thanks in advance!

Hi,
According to your description, I am not quite sure about your requirement. Could you please provide more information about your issue, such as why do you want to use %%Email%% or alias to filter the disclaimer as a condition?
Generally, if you want to notify everyone that the email domain will be changing by using email disclaimer. We can add a disclaimer to all domain messages by a transport rule. For example, the following rule can add “Our email domain will be changing” at
the start of the newest e-mail message for all messages which are sent and received inside the organization:
If you just want to add this disclaimer in a specific user’s message, we can do the following:
Apply this rule if…
The sender is Administrator,
Do the following…
Append disclaimer text and fallback to action if unable to appy…
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

BIS and Exchange 2010 with TMG

Dear all,
I stumped into this problem whereby my client has an Exchange 2010 with mixed-mode mobile users of Active Sync and BlackBerry.
They have this [url]https://mail.***.com.my[/url] as their OWA URL and credentials should be entered as:
Username: Domain\Username
Password: Password
This convention is the same irregardless users accessing from OWA or to setup Active Sync or BlackBerry.
Question are:
1. How do I setup BIS account on my BlackBerry? Method I use is log into my telco portal but the credentials I entered does not recognised by the system.
2. Alternatively, I tried to set it direct on my BlackBerry but was prompt the same error as above which is 'Username must be at least 4 characters'.
3. Does naming convention setup same for Active Sync users and BlackBerry users?
Any help would be greatly appreciated.

Hi and Welcome to the Forums!
rizauden wrote:
1. How do I setup BIS account on my BlackBerry? Method I use is log into my telco portal but the credentials I entered does not recognised by the system.
2. Alternatively, I tried to set it direct on my BlackBerry but was prompt the same error as above which is 'Username must be at least 4 characters'.
BIS itself is provided to you by your wireless service provider. With hundreds of different carriers in the world and dozens of different methods each, there's no way to be sure how to guide you with specifics. I suggest you ring them up and talk to them about how to enable BIS on your BB.
rizauden wrote:
3. Does naming convention setup same for Active Sync users and BlackBerry users?
I'm not sure how ActiveSync works, but the configuration instructions for OWA are here:
KB03133How to integrate a Microsoft Outlook Web Access email address with a BlackBerry Internet Service account
And here are some further helpful KBs on the topic:
KB15173Locate the mailbox name for a Microsoft Outlook Web Access 2007 email account
KB02858Unable
to integrate a Microsoft Outlook Web Access or IBM Lotus Domino Web
Access email address with a BlackBerry Internet Service account
KB04804Error message appears when attempting to integrate a Microsoft Outlook Web Access 5.5 or 2010 account
KB18567BlackBerry
Internet Service cannot connect to a Microsoft Outlook Web Access
account using Microsoft Exchange 2007 or Microsoft Exchange 2010
Good luck and let us know!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Unable open Project details or a project from PWA Project server 2010 with Alias name

Hi,
I am unable to open the Projects from Project center with the Alias name with the server name i am able to open the projects, version is project server 2010,
My system is ABC.DC.IN alias name i have given is DEF.AD.COM
With the system name i can able access PWA and all are working fine.
As i have observed with alias name i can able to login to pwa and all the server setting approval center all are working fine but only in the project center i am not able to open the projects (http://DEF.AD.COM/pwa/ProjectDrillDown.aspx .xxxx)
its is coming in the below of the ie.
But with Alias name these are the issues i am facing,
1.when longing with alias name its asking two times for user name and password
2.when i click on a project from project center its taking some time and asking for user name and password after i enter user name and password "PAGE cannot displayed" error i am getting.
can any one Help me.
vijay kommireddi

Hi Eric,
Thanks for your Reply.
As you said i have added in Manged Path as (Testpwa/projects.aspx as <Wildcard inclusion>) But still problem is there it is asking user
name password again if click on any project in project center and and showing page cannot be displayed error.
This is url its is showing in the below of the IE ( http://def.ad.com/testpwa/projectdrilldown.aspx?ProjUid=e28c6d43-85b6-478d-9542-2961cc81a69e)
I have observed one more thing if click on Project
details then only this issue is coming project schedule and project information
is also opening with Alias name.
My farm version is 14.0.7015.1000
Vijay Kommireddi

Unified Messaging Exchange 2010 with Jabber

Is anyone aware of a way to have Jabber integrate with Exchange 2010 for voice-mail?
I have CUCM trunked to the server, the calls are going to the server and you can leave a voice mail and phone MWI lights up.
I have the voice-mail icon on the jabber client and when I press it, it goes to the voice mail box.
The issue is that it says its not connected, and when people leave a voice-mail, Jabber does not indicate you have a message.
We are running CUCM 9.1, CUPS 9.1, Jabber4W 9.7
Any input would be greatly appreciated.
Thanks
Phil

Jabber for windows 9.7; only supports VMREST voicemail access. The only option for this is unity connection 8.5 and above. Connection to Exchange 2010 form of unified messaging (voicemail service through exchange server alone) is not supported.
Please refer to the following link;
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_7/JABW_BK_C4C679C9_00_cisco-jabber-for-windows-97/JABW_BK_C4C679C9_00_cisco-jabber-for-windows-97_chapter_01.html#JABW_RF_SEF029A0_00
On-Premises Servers for Cisco Jabber for Windows and Cisco Jabber for Mac
Cisco Jabber supports the following on-premises servers:
Cisco Unified Communications Manager version 8.0(1) or later
Cisco Unified Presence version 8.0(3) or later
Cisco Unity Connection version 8.5 or later

What is the best way to get activesync to work on Exchange 2010 with co-existing Exchange 2003?

I currently have all my mailboxes on my Exchange 2003 server and I introduced my first Exchange 2010 server into the same environment so they are running co-existent. The mailflow is functioning properly so now I need to test out the activesync. From
what I've read, you have to create a SSL certificate with SAN on the Exchange 2010 server and create a legacy.domain.com name to point to the Exchange 2003 server. Then replace out the existing SSL certificate on the Exchange 2003 server with the
new one that was created for the Exchange 2010 server. However, my question is that if this does not work could I easily revert back to the original settings where Exchange 2003 server is doing the activesync instead of Exchange 2010? That way
I would not disrupt activesync from working.

The legacy url is not important for activesync, but:
Enable Integrated Windows authentication on the Microsoft-Server-ActiveSync virtual directory on the
Exchange 2003 back-end server
http://technet.microsoft.com/en-us/library/ee332348(EXCHG.140).aspx
once you point your external url for active sync at your 2010 it should proxy the 2003 active sync

Exchange 2010 with Outlook 2007 Shared Contacts with Attachments

We have an Exchange 2010 server. There is only one Exchange server so all roles are on this server.
Found out that sharing contacts between users misses something.
If a user has Attachments or Notes in their contacts we can see via the Attachment column in Contacts that there are attachments.
But another user viewing the shared Contacts of the user above, cannot see if the Contacts have Attachments unless they open each one. The Attachment column states there are no Attachments. Is this how it is? Is it a syncing issue?
The image I have attached is what the user sees accessing a shared contact address book. It shows Notes and the Attachments columns. The contacts with partial words visible in the Notes column should have a Paper Clip Icon as they also have attached items.

Hi,
There is no related feature in Exchange server to manage Outlook view.
Additionally, I shared my Contact with another user in my Exchange 2010 SP3 with Outlook 2013 environment. And it showed the same results as yours. The attachments icon was not shown in the list view in another user’s Outlook but it appeared in my own Contact.
Thanks,
Winnie Liang
TechNet Community Support

Installing / Upgrading Exchange 2013 to Exchange 2010 with a o365 Hybrid environment

Hi
I am trying to install a new server with Exchange 2013 on an environment with an existing Exchange 2010 Sp3. Reason for that is that I have a o365 hybrid environment and need to disconnect my on-line and on-premise e-mail connection. I want to completely
run all my mailboxes on o365 no-longer dependent on on-premise exchange but the Exchange 2010 doesn't have a functionality to 'dismantle' the hybrid.. we need to have exchange 2013.
When I try to install Exchange 2013 I get an error message that I need to upgrade my o365 tenant. : my o365 tenant version is : AdminDisplayVersion : 0.20 (15.1.49.12) :IsUpgradingOrganisation : False.
Is there a better way of updating my environment.
Regards

Post the error from setup log for more information.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
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.

Cannot read message bodystructure from Exchange 2010 with IMAP

Hi,
I'm trying to read mails from MS Exchange 2010 that have multipart/mixed content type and contain only one text/html part. I'm using IMAP and the newest Javamail 1.4.3. The mail processing fails when trying to fetch the bodystructure. I can process the same message perfectly well from Exchange 2003:
BODYSTRUCTURE from Exchange Server 2003 (Works fine with javamail)
* 1 FETCH (BODYSTRUCTURE (("TEXT" "HTML" ("charset" "UTF-8") NIL NIL "7BIT" 242 5 NIL ("inline" NIL) NIL) "mixed" ("boundary" "----=_Part_28_1466852274.1263305065649") NIL NIL))BODYSTRUCTURE from Exchange Server 2010 (Does not obey specification, doesn't work with javamail)
* 1 FETCH (BODYSTRUCTURE ("multipart" "mixed" ("boundary" "----=_Part_1_1045289550.1263292469650") NIL NIL NIL 0 NIL NIL NIL NIL))Does anyone have same kind of problems? This seems to me like a bug in Exchange 2010, but does anyone know any work-around for this other than using POP3 that works with the same message?
Here's the message (slightly edited to protect the guilty):
Received: from XXX (10.1.2.152) by
YYY (10.1.3.154) with Microsoft SMTP Server id
14.0.639.21; Tue, 12 Jan 2010 12:34:29 +0200
From: "XXX@YYY" <XXX@YYY>
Reply-To: <XXX@YYY>
To: Receiver <XXXX@YYY>
Message-ID: <1765234390.11263292469652.JavaMail.XXX@YYY>
Subject: Phone order: Mobile phone for mobile employees
Content-Type: multipart/mixed;
 boundary="----=_Part_1_1045289550.1263292469650"
Return-Path: ZZZ@YYY
Date: Tue, 12 Jan 2010 12:34:29 +0200
X-MS-Exchange-Organization-AuthSource: XYZ
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0
------=_Part_1_1045289550.1263292469650
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 I would like to order the following phone:
 Mobile phone for mobile employees
 
 
 Best regards,
 XXX@YYY
 
------=_Part_1_1045289550.1263292469650--Cheers,
Kai

Yup, looks like a bug in Exchange 2010, please report it to Microsoft.
If Microsoft gives you a bug ID or any way to track this bug, please let me know.
Try this workaround:
[http://java.sun.com/products/javamail/FAQ.html#imapserverbug|http://java.sun.com/products/javamail/FAQ.html#imapserverbug]

Exchange 2010 with Forefront, can't receive large attachments from outside ONLY.

I am able to send and receive large files internally now. Also I am able to send large files to the outside. But I can't receive anything larger then defaulted 10mb. My Environment is 2 Edge boxes, 2 cas HT boxes, 2 mx DB boxes.
I was asked to increase the size of the emails my organization can receive, I went ahead and adjusted the following:
EDGE
1. Receive and Send connectors, set to 40mb.
2. Forefront -->Advanced Options--> Threshold Levels--> all max sized are at 50mb.
CASHT
1. Organization Configuration--> Hub Transport -->Send Connectors and GLOBAL SETTINGS
2. Server Configuration--> HUB Transport--> all the connectors
3. Recipient Configuration--> Mailbox --> users.
All sizes are set to 40mg!
I am able to send large files (24354K), but not able to receive
The following is output from Get-TransportConfig:
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 40 MB (41,943,040 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 40 MB (41,943,040 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo :
LegacyJournalingMigrationEnabled : False
MaxDumpsterSizePerDatabase : 60 MB (62,914,560 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : unlimited
MaxRecipientEnvelopeLimit : unlimited
MaxSendSize : unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
Rfc2231EncodingEnabled : False
ShadowHeartbeatRetryCount : 12
ShadowHeartbeatTimeoutInterval : 00:15:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowRedundancyEnabled : True
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Also my antispam cloud service sent me the following logs:
10:10:38.662 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: MAIL FROM:<[email protected]> SIZE=34140018
10:10:38.771 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 250 2.1.0 Sender OK
10:10:38.771 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY
10:10:38.896 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 250 2.1.5 Recipient OK
10:10:38.896 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: DATA
10:10:39.021 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 354 Start mail input; end with <CRLF>.<CRLF>
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
abort request
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
write failed. Error Code=socket aborted
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
[1959469085] failed to send. Error Code=socket aborted
AND
Also another error from Appriver:
08:48:34.798 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: MAIL FROM:<[email protected]> SIZE=34148430
08:48:34.907 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 250 2.1.0 Sender OK
08:48:34.907 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY
08:48:35.032 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 250 2.1.5 Recipient OK
08:48:35.032 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: DATA
08:48:35.157 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 354 Start mail input; end with <CRLF>.<CRLF>
08:53:34.718 3 SMTP-929371(workemail.com.smtpip.com:25)
write failed. Error Code=connection reset by peer
08:53:34.718 3 SMTP-929371(workemail.com.smtpip.com:25)
[1959495450] failed to send. Error Code=connection reset by peer
I am out of options here, wondering if anyone know's anything about this?
Vladimir

Cara,
Yes I have looked at smtp receive protocol logs, below is a log from one failed transmission, I don't see anything that jumps out at me:
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,MAIL FROM:<[email protected]> SIZE=24042643,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,08D0340D4EB7692B;2013-06-10T18:41:06.863Z;1,receiving message
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:06
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.0 Sender OK,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
+,,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:07
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
+,,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:07
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,,Ignored X-OriginatorOrg header value 'outside.com' because session capabilities do no
2013-06-10T18:41:07.457Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,,Ignored X-OriginatorOrg header value 'outside.com' because session capabilities do no
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,+,,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeader
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,<,EHLO YPICASHT1.YPI.com,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-SIZE 42949632,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-PIPELINING,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-DSN,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-STARTTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-AUTH,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-X-EXPS NTLM,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-8BITMIME,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-BINARYMIME,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-CHUNKING,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-XEXCH50,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250 XSHADOW,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,<,X-ANONYMOUSTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,220 2.0.0 SMTP server ready,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Sending certificate
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CN=YPIEDGE1,Certificate subject
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CN=YPIEDGE1,Certificate issuer name
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,7CERT#,Certificate serial number
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CERT,Certificate thumbprint
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,YPIEDGE1;YPIEDGE1.edge.local,Certificate alternate names
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Received certificate
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CERT,Certificate thumbprint
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Received DirectTrust certificate
Vladimir

Load Balancing Exchange 2010 with Citrix Netscaler

Hi All,
I have two exchange multirole server(cas/ht/mb) EXCH1 and EXCH2 both are configured in DAG (dag1.example.com) and also both are configured with CAS array (casarray.example.com)
We have Cirtix Netscaller hardware load balancer. I have to configure Load balancing for CAS array, ActiveSync, OWA, Outlook Anywhere.
Please guide me through the configuration for citrix netscaler as i am new with Citrix Netscaler.
Regards,
Pravin

Hi,
In order to resolve this issue more efficiently, I recommend you contact support from Citrix, you might get a better answer there. Thanks for your understanding.
https://www.citrix.com/community.html
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Unable to receive some emails in Exchange 2010

Hi,
Spent a few days on this and getting no where fast and out of ideas now.
We migrated a customer from SBS2003 running exchange 2003 to Server 2012 running HyperV with Exchange 2010 on a VM. So far the migration had gone through without many issues. We have 2 VM one AD/File server other Exchange 2010. with the old SBS2003 server
still online.
Basically after moving all the mailboxes from Exchange 2003 to Exchange 2010, some random users wont receive mail. Internal and sending is perfect. Port 25 was changed from the old SBS server and pointing to new EX2010 box.
After more testing pointing port 25 back to the old server solves the problem, all users receives emails instantly. So emails are routed via the old SBS box to the new Exchange.
On the new server both Send and receive connectors have been deleted and recreated. Checked the Default connector and Anonymous users has been ticked. Also this is ticked on the newly created receive connector.
I enabled SMTP logging and noticed the emails the wasn't getting delivered had the message below.
354 Start mail input; end with <CRLF>.<CRLF>,
,Remote
Found another person with something similar and tried the fix didn't work for me
http://social.technet.microsoft.com/Forums/exchange/en-US/da8a1fa4-0757-4ea5-8225-de15707d5a57/problems-receiving-mail-smtpreceive-is-set-to-verbose
Spoke with the ISP, all the email for our customer goes through a SPAM filtering service and they noticed their server would Telnet in and get "connection lost" after the Mail from: command, which matches the error on the SMTP log. Again it happens
to random users not receiving mail, but I did notice any new users that was created after the migration doesn't get any external emails when router via the ISP and Port 25 pointing to the new server.
So as a trial I bypassed the ISP by updating the MX record to point mail directly at new server, this fixed the problem! Everyone new and old users was receiving no problems. But speaking with the ISP they have 100+ customers on Exchange 2010 and never
experienced this issue. Only difference i can see we are using HyperV, could this be a networking issue?
PS our ISP uses a Watchguard device for Spam filtering.
Thanks!!!

X.400 potentially could be the problem.. got through this article
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/x400-addresses-exchange-2010-part1.html
Where Technology Meets Talent

HT5567 Iphones and Ipads with IOS 6.0.x and later getting Calendar invitation even so that Delegate access is enable on exchange 2010 and outlook 2010

I'm Running Exchange 2010 with outlook 2010 in my environment, since Apple OS went from 5.x to 6.x I been having issues where the Iphones and Ipads running OS version 6.x or higher do not acknowledge that the exchange user has a calendar delegate and are automatically accepting the invitations, not allowing the Delegate to acknowledge first, If this test is run on any Apple devices running OS Version 5.x but less than 6.x the issue is not there.. any one that may have encounter with this situation got a fix or a possible resolution on it.. Thanks

Ok, well after looking at everything, I decided that the best solution was to uninstall an App called "Tango", as it seemed to 'mess' with contacts directly, and I only use it with 1 person, so switching back to Skype (plus Tango sends/shares lots of personal
info, location, and keeps changing it's access rights and doing stuff when you're not looking - I'm sure some people love it, but for me, it's a belts and braces get rid of anything that might have 'contributed' to this issue).
Found my un-sync'd contacts and emailed them to myself, then deleted the Exchange active-sync account. Checked what was left, found google had managed to sync some stuff, cleared that up too!
RE-created the account on the S4 - only need the email and password, as it finds the server and sets itself up automatically (I guess it did that previously).
All is now working, after about 5mins the data had been re-populated and it sync's new changes instantly. But I will monitor from time to time to check that new contacts or added numbers etc do sync. My best guess is that some index or other data became corrupt.
Just one of those things (or had I been tango'd?!).
On the Truncating Notes Issue, the S4 (realised that it's running Android 4.3) does chop a note but only if edited, at 1001 chrs. However unlike others, it seems to only truncate the note if you actually edit the note field, so adding a phone number or removing
one, leaves the note field intact!
To summaries other devices behaviour with the Contact record Notes Field:
- iPhone 3GS (on iOS 6.1.3) truncates at 32,777 chrs (so pretty big notes!)
- Samsung Galaxy Note 10.1 (GT-N8020 - Android 4.1.1) chops at about 1,000chrs, even if just adding a phone number to the contact - so not even editing the notes field
- HTC One X (4.2.2) at 5,122 chrs (when editing any part of the contact)
I hope this might help someone in the future if they have similar problems ...
cheers

Exchange 2010 - Resource Mailbox won't send external notification email

Exchange 2010 with SP1. These mailboxes used to respond to outside booking requests, when we were running Exchange 2007. I've verified that -ProcessExternalMeetingMessages is set to $true. The mailbox responds to internal requests with an email.
All users are allowed to make "Resource In-Policy Requests".
I've tried booking from an email address that was setup as a Contact in Exchange - still no luck.
Any ideas?
Thanks.

Martin
Agency
Could you share what settings did you use for SMTP connectors?
I have tried:
Authentication – Externally Secured
Permission Group – Exchange Servers
I can send emails via these connectors, but Room Mailbox still deletes requests from external sender.
Both organizations have Exch 2010 sp3 RU6, and AD forest 2008R2 level.

Active sync on bionic will not work with exchange 2010

We recently upgraded our corporate email system to exchange 2010. Prior to this, while on exchange 2007 I had no issues with active sync. On the day we upgraded active sync no longer worked for me I have others at work running older Droid OS. 2.2.2 and 2.2.3. They have no issues with the new exchange. I am on 2.3.4. I am able to do the setup and the setup will detect the new server and act as if the account is setup correctly. When it tries to sync I get a "connection error" message.

Hi,
From your description, I recommend you use the following URL to check if you can access EAC. I see it works for several people about this issue.
https://<Exchange 2013 CAS FQDN>/ecp?ExchClientVer=15
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Problem with Exchange 2010, Q10 and attachment

Q10 & Exchange 2010; unable to download and forward attachment
Hi all,
i have a problem with Q10 phone, sync with Exchange 2010 with activesync (not BES) all seem ok but unable to download attach.
When press "download" didnt start. Unable also to forward same message but i think is a chainde problem.
Same message from desktop (outlook) or OWA is ok and attach downloadable.
This is the only Q10 present in company for test so i cannot compare to others BB.
All other users connected to the exchaneg server have iphone & ipad no issue result. Email service seem ok also for desktop.
Firmware was updateted about 10 day ago.
Any idea for me?
Thanks

Hi marcottt,
Could you provide more detail please so I can better assist?
Do you have this issue with all attachment types? If not, what type of attachment are you having this issue with and what size is the attachment?
What happens when you try to forward the message? Is any error received?
Does removing and re-adding the email account make any difference?
I look forward to your response.
-FS
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.
Click Solution? for posts that have solved your issue(s)!

Personalize email disclaimer in exchange 2010 with alias?

Similar Messages

Maybe you are looking for