we have Exchange server 2013 4 mailbox servers and 4 CAS server in two sites there is between 10 to 20 Minutes delay in mail flow between internal users.
hass
↧
Exchange 2013 Email delay
↧
All inbound mail stuck in Submission Queue with a delivery type of Unknown and error A Local Loop was Detected
All inbound mail stuck in Submission Queue with a delivery type of Unknown and error A Local Loop was Detected
My email organization consists of two email servers: Exchange 2013, Oracle Messaging. The servers are in two different geographic locations.
The Oracle messaging is the primary email server (orc1.MyDomain.com)
The Exchange server (loc2-ex.MyDom2.local)
A routing rule on the Oracle messaging server forwards MyDom2 user email (changes the email address from @MyDomain.com to @loc2.MyDomain.com) to the remote Exchange server.
On the Exchange server, the domain MyDomain.com is set for internal relay. MyDom2.local and loc2.MyDomain.com are set at Authoritative.
Users on the Exchange server can send Internet bound email that is delivery as expected to outside domains. Email between exchange users and inbound internet email gets delivered to the Exchange server but is not posted to the user's email. Instead it remains in "Submission queue" (delivery type "undefined", status "ready") Each message's last error is "A local loop was detected" (SCL "-1", Queue ID "Loc2-EX\Submission", Message Source Name "SMTP: Client ProxyLoc2-EX")
How do I get Exchange to deliver emails?
Here are the settings for Accepted Domains, and the Send and Receive Connectors:
*************************************************************************************************************************
************* Accepted Domains
*************************************************************************************************************************
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : MyDom2.local
CatchAllRecipientID :
DomainType : Authoritative
MatchSubDomains : False
AddressBookEnabled : True
Default : False
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyDom2.local
DistinguishedName : CN=MyDom2.local,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyDom2.local
Guid : 1ae7e6e6-1747-4d7b-bfb1-d3998a34bc6f
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:29 PM
WhenCreated : 3/10/2015 5:16:06 PM
WhenChangedUTC : 5/6/2015 5:24:29 PM
WhenCreatedUTC : 3/10/2015 9:16:06 PM
OrganizationId :
Id : MyDom2.local
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : MyDomain.com
CatchAllRecipientID :
DomainType : InternalRelay
MatchSubDomains : False
AddressBookEnabled : False
Default : True
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyOrganization relay domain
DistinguishedName : CN=MyOrganization relay domain,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyOrganization relay domain
Guid : 35e58252-49fd-4048-abf6-4213f4eb0fa4
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:29 PM
WhenCreated : 3/26/2015 3:29:13 PM
WhenChangedUTC : 5/6/2015 5:24:29 PM
WhenCreatedUTC : 3/26/2015 7:29:13 PM
OrganizationId :
Id : MyOrganization relay domain
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : loc2.MyDomain.com
CatchAllRecipientID :
DomainType : Authoritative
MatchSubDomains : False
AddressBookEnabled : False
Default : False
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyOrganization relay sub-domain
DistinguishedName : CN=MyOrganization relay sub-domain,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyOrganization relay sub-domain
Guid : 867dc53e-574f-4324-916e-9853718568fc
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:19 PM
WhenCreated : 3/30/2015 11:10:38 AM
WhenChangedUTC : 5/6/2015 5:24:19 PM
WhenCreatedUTC : 3/30/2015 3:10:38 PM
OrganizationId :
Id : MyOrganization relay sub-domain
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
My email organization consists of two email servers: Exchange 2013, Oracle Messaging. The servers are in two different geographic locations.
The Oracle messaging is the primary email server (orc1.MyDomain.com)
The Exchange server (loc2-ex.MyDom2.local)
A routing rule on the Oracle messaging server forwards MyDom2 user email (changes the email address from @MyDomain.com to @loc2.MyDomain.com) to the remote Exchange server.
On the Exchange server, the domain MyDomain.com is set for internal relay. MyDom2.local and loc2.MyDomain.com are set at Authoritative.
Users on the Exchange server can send Internet bound email that is delivery as expected to outside domains. Email between exchange users and inbound internet email gets delivered to the Exchange server but is not posted to the user's email. Instead it remains in "Submission queue" (delivery type "undefined", status "ready") Each message's last error is "A local loop was detected" (SCL "-1", Queue ID "Loc2-EX\Submission", Message Source Name "SMTP: Client ProxyLoc2-EX")
How do I get Exchange to deliver emails?
Here are the settings for Accepted Domains, and the Send and Receive Connectors:
*************************************************************************************************************************
************* Accepted Domains
*************************************************************************************************************************
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : MyDom2.local
CatchAllRecipientID :
DomainType : Authoritative
MatchSubDomains : False
AddressBookEnabled : True
Default : False
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyDom2.local
DistinguishedName : CN=MyDom2.local,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyDom2.local
Guid : 1ae7e6e6-1747-4d7b-bfb1-d3998a34bc6f
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:29 PM
WhenCreated : 3/10/2015 5:16:06 PM
WhenChangedUTC : 5/6/2015 5:24:29 PM
WhenCreatedUTC : 3/10/2015 9:16:06 PM
OrganizationId :
Id : MyDom2.local
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : MyDomain.com
CatchAllRecipientID :
DomainType : InternalRelay
MatchSubDomains : False
AddressBookEnabled : False
Default : True
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyOrganization relay domain
DistinguishedName : CN=MyOrganization relay domain,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyOrganization relay domain
Guid : 35e58252-49fd-4048-abf6-4213f4eb0fa4
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:29 PM
WhenCreated : 3/26/2015 3:29:13 PM
WhenChangedUTC : 5/6/2015 5:24:29 PM
WhenCreatedUTC : 3/26/2015 7:29:13 PM
OrganizationId :
Id : MyOrganization relay domain
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
RunspaceId : efac3445-3304-446a-ac62-d308f1a3b0a6
DomainName : loc2.MyDomain.com
CatchAllRecipientID :
DomainType : Authoritative
MatchSubDomains : False
AddressBookEnabled : False
Default : False
AuthenticationType :
LiveIdInstanceType :
PendingRemoval : False
PendingCompletion : False
DualProvisioningEnabled : False
FederatedOrganizationLink :
MailFlowPartner :
OutboundOnly : False
PendingFederatedAccountNamespace : False
PendingFederatedDomain : False
IsCoexistenceDomain : False
PerimeterDuplicateDetected : False
IsDefaultFederatedDomain : False
EnableNego2Authentication : False
InitialDomain : False
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : MyOrganization relay sub-domain
DistinguishedName : CN=MyOrganization relay sub-domain,CN=Accepted Domains,CN=Transport
Settings,CN=Loc2-EXchange,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=MyDom2,DC=local
Identity : MyOrganization relay sub-domain
Guid : 867dc53e-574f-4324-916e-9853718568fc
ObjectCategory : MyDom2.local/Configuration/Schema/ms-Exch-Accepted-Domain
ObjectClass : {top, msExchAcceptedDomain}
WhenChanged : 5/6/2015 1:24:19 PM
WhenCreated : 3/30/2015 11:10:38 AM
WhenChangedUTC : 5/6/2015 5:24:19 PM
WhenCreatedUTC : 3/30/2015 3:10:38 PM
OrganizationId :
Id : MyOrganization relay sub-domain
OriginatingServer : Loc2-DC.MyDom2.local
IsValid : True
ObjectState : Unchanged
↧
↧
Disable unauthorized SMTP Relay within Domain
Hi All,
We have Exchange 2013 SP1 infrastructure on top of Windows Server 2012 R2. We have a DAG and CAS NLB clusters.
Anyone can relay Emails from my SMTP to all users within my domain without authentication.However no one can send emails outside my domain (external Emails without authentication).
All these emails are sent through Default Front end Receive Connector, and we cannot Disable Anonymous Users from connector security settings as by doing this we will not receive emails from External World. Please refer the attached snapshot.
Need your suggestion to implement SMTP security to restrict Unauthorized SMTP Relay.
Thanks
VN
↧
Mail Exchange Server
Hi tech,
I have a problem, everytime my clients uses his ip 41.79.10.106 he gets the error message
The mail system
<>: host [65.55.37.88] said: 550 SC-001
(COL004-MC2F14) Unfortunately, messages from 41.79.10.106 weren't sent.
Please contact your Internet service provider since part of their network
is on our block list. You can also refer your provider to
. (in reply to MAIL
FROM command)
Kindly help me delist this from your network.
Mike
Technical Engineer.
↧
Suppress Exchange 2013 moderation notifications
Hello All,
I have an Exchange 2013 environment where I have just enabled message moderation. So far so good. However, I would like to suppress all notifications to the moderated recipients and the sender of messages to this recipient. I have created a transport rule that deletes all emails containing "Your message was rejected by a moderator for these recipients" which is what the system sends when a message is rejected by the moderator. However if the moderator doesn't approve or reject a notitication, another message is sent to the sender (and maybe the moderated receipent). I have found a good bit of MS reference material for the message (If the approver either deletes or ignores the approval message, an expiration message is sent to the sender. This happens after two days in Exchange Online, and after five days in Exchange Server 2013....# 3 in how the approval process workshttps://technet.microsoft.com/en-us/library/dd297936.aspx) I need to know exactly what the message says so I can create the transport rule to delete it and not bounce a message back to the sender.
I basically have 2 questions:
1. Is it possible to configure Exchange so it doesn't generate these notifications to begin with?
2. What are the contents of the various notifications sent by the system when moderating messages? I have one listed above but don't know what else gets sent. I need to create a transport rule to delete/redirect the message so that it's not sent to the sender, moderated recipient, etc.
I have only a few days to figure this out. Please help.
JPC0706
↧
↧
Exchange 2007/2013 Migration / Intra-Organization SMTP Send Connector
Hi.
We are currently migrating from Exchange 2007 to Exchange 2013. We have Exchange servers across 3 AD Site (A, B &C). Right now, all our users are on Exchange 2007 except 2-3 test users. Exchange 2013 was installed in site A without any issue. At that moment, mail flow between users from site A to site B keep using Exchange 2007 hub servers in both directions; Exchange 2013 Transport Servers in site A were not used at all.
When we installed Exchange 2013 in site B, mailbox flow between Exchange 2007 users from site A to Exchange 2007 users in site B start using site B Exchange 2013 Transport servers. Why?
Right now, when site A users are sending email to site B, it’s using site B Exchange 2013 Transport Servers (Site A 2007 Mailbox Server, Site A 2007 Hub Server, Site B Exchange 2013 Transport Server, Site B 2007 Hub Server, Site b 2007 Mailbox Server). When site B users are sending email to site A, it’s keep using Exchange 2007 hub. (Site B 2007 Mailbox Server, Site B 2007 Hub, Site A 2007 Hub, Mailbox, Site A 2007 Mailbox Server).
Can someone explain why Exchange 2013 transport services are only used in site B and not A? Any documentation I can read that explain the result?
Thank you.
↧
Rules are crazy
I added a rule to block email with the word Cialis in it.
However the domain I send email to is is.co.za and the rule blocks it. How daft is this. The rule should look for the whole word not parts of it
Is there a way to make it look at the whole word, or am I going to be inundated with adverts for Cialis?
TIA
Glyn
↧
Sending mail from new domain through 365 SPAM filter gives SPF error
Setting up an internal relay from one exchange forest to another. E-mail is flowing fine from a to b and going to the correct mailbox. The problem lies in sending from the mailbox in domain b with domain a address on it. Domain B uses Office 365 SPAM filter and when a message is sent out from domain A from Domain B it blocks it. We added domain A to the domain list on 365 and it seemed to fix it. Then after a few hours anyone sending to domain A from domain B were getting bounce backs (error below) : I'm guessing it is as simple as not setting the SPF record correctly to allow mail from domain a to be allowed to originate from domain b? Once I migrate all users from Domain a to b I will redirect the MX record to point to office 365 but I want to keep it where it is for now. Anyone have any experience with this?
cas1.domainb.com #<cas1.domainb.com #5.7.1 smtp;550 5.7.1 Unable to relay> #SMTP#Original message headers:
Received: from sever.protection.gbl (xxx.xxx.xxx.31) by
BN1BFFO11HUB039.protection.gbl (xxx.xxx.xxx.186) with Microsoft SMTP Server
(TLS) id xxx.xxx.xxx.14; Tue, 19 May 2015 01:42:55 +0000
Authentication-Results: spf=permerror (sender IP is xxx.xxx.xxx.17)
smtp.mailfrom=domainb.com; domaina.com; dkim=none (message not signed)
header.d=none;
Received-SPF: PermError (protection.outlook.com: domain of domainb.com used an
invalid SPF mechanism)
↧
Add a dynamic group to Message Delivery Restrictions
Hello,
We can add a dynamic distribution group to "Message Delivery Restrictions" in Exchange 2010 but what i worry about that is performance. Is that cause a problem in a big organization (more than 1 million daily mail traffic)?
It's a good solution for a group to restrict receiving mails from everywhere. but it may cause performance problem if we generalize for more mail groups or mailboxes. Because when i add a dynamic group, mails delay more than normally.
Thanks in advance.
↧
↧
Transport rule applied false positive
Hi everyone,
In my Org. I have Exchange 2010 and 2013 servers.
I have created two transport rule:
- Block spesific attachments extensions (on Exchange 2010 - for mailboxes located on that server).
This rule also is applied on 2013 Mailbox servers.
Now I'm getting some requests from my users - the rule is applied where it should not.
Could you please explain, how can I track, WHY the rule is applied? It rejects the messages where no attachments at all..
↧
Exchange 2013 Attachment Size Issue
Hi everybody,
I'm having some trouble with an Exchange 2013 server.
The users are not able to receive messages with a size bigger than 10MB, i tried with serveral attachments.
I already did te following:
Changed the maximum receive size through the ECP to 60MB (on the default frontend Exchange), and restarted te transport service.
Set the receive size through PowerShell with the following command.
set-transportconfig -maxreceivesize 35MB
when i check the receive size properties, it accepts 35MB messages. (get-transportconfig -property maxreceivesize)
Also restarted serveral Exchange transport services.
Checked the router if there are any special firewall rules, but there are none.
When I send an email with an attachment (PDF about 4 meg), it receives like it should.
Once I send a same email but with an 11meg PDF file, it is not delivered.
When sending this e-mail and attechment, i checked the box to notify me when the message has been deliverd.
I don't get any response, no NDR, nothing...
Tried e-mail tracking but there is no trace of my message.
Am I missing anything?
Kind regards,
Tim
↧
Exchange 2013 unable to relay to external adress
I'm having a hard time getting Exchange relaying the mail from my applications to external domains.
I have setup a recieve connector as Hub Transport Custom connector.
- Externally secured (for example, with IPsec)
- Exchange Servers
- Anonymous Users
I have no clue what i did wrong.. I can send to internal Accepted domains but not outside of my company.
Thanks in advance,
Kevin
↧
Set-Mailboxautoreplyconfiguration LINE BREAK issue
Hi all, I'm trying to set up an auto reply message for a mailbox, but I'm unable to include the break lines.
I tryed several methods:
1. just pasting the text:
[PS] C:\Windows\system32>Set-MailboxAutoReplyConfiguration -identity testexchange -ExternalMessage "This is an auto reply message.
>> this is the second line"
>>
i receive a mail like this:
This is an auto reply message.this is the second line
2. with a variable in power shell and adding exchange 2013 snapin:
PS C:\> $reply = "first line
>> second line"
>>
PS C:\> Add-PSSnapin Microsoft-Exchange.Management.Powershell.snapin
PS C:\> Set-MailboxAutoReplyConfiguration -Identity testexchange -ExternalMessage $reply
Again, i receive a mail like:
first linesecond line
3. I tried fetching the text from a file:
[PS] C:\>$reply=Get-Content reply.txt
[PS] C:\>Set-MailboxAutoReplyConfiguration -Identity testexchange -ExternalMessage $reply
4. I also tried with a powershell script:
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.snapin
$x = @"
this is the autoreply
second line
third line
"@
set-mailboxautoreplyconfiguration -identity testexchange -externalmessage $x
again, i receive a mail like: this is the autoreplysecond linethird line
Thank you all,
↧
↧
ERROR:0x80070005-00000000-00000000 after movement of mailboxes to Exchange 2013
Dear all,
I have users with 2nd mailbox attached to their Outlook, after movement the mailboxes to Exchange 2013 they're no longer able to send any e-mails from the 2nd mailbox
And they also get this ERROR:0x80070005-00000000-00000000
If I attach the same mailbox to my Outlook, I have no problems with sending e-mails.
Does anyone know what might that be?
Thank you
↧
Get Support to apply new rule with attach file in Mail exchange 2013
I need create a new rule in my Exchange 2013 system to resolve my company's demands
1. Send mail to outside if (have attach file => must to input manager in CC field)2.Send mail to outside if (have attach file)=> Must to manager approval
I checked this link but don't enough information to do that, anybody can help me ? Thank so much !
https://technet.microsoft.com/en-us/library/jj919236%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
↧
Subject Alternative Names in the certificate purchasing
Hi all,
I have a question regarding the SAN and the domain names that will be included in certificate's SAN. The case is as follows:
Server is Exchange Server 2013. Accepted domains are domain111111.com and domain222222.com.
MX record points to mail.domain111111.com, on the public DNS I nave created CNAME record for Autodiscover
autodiscover.domain111111.com. All users have an email account, which is set at @domain222222.com.
I need to create new certificate request and I wonder whether to include domain domain222222.com in the SAN or to create the
request only with mail.domain111111.com as a common name and autodiscover.domain111111.com as a SAN.
I have a question regarding the SAN and the domain names that will be included in certificate's SAN. The case is as follows:
Server is Exchange Server 2013. Accepted domains are domain111111.com and domain222222.com.
MX record points to mail.domain111111.com, on the public DNS I nave created CNAME record for Autodiscover
autodiscover.domain111111.com. All users have an email account, which is set at @domain222222.com.
I need to create new certificate request and I wonder whether to include domain domain222222.com in the SAN or to create the
request only with mail.domain111111.com as a common name and autodiscover.domain111111.com as a SAN.
↧
Spam past 2 weeks
Has anyone else been getting hit with more than normal spam the past 2 weeks? I have checked all my FIPS updates are running as expected, but it's just non-stop.
I also wanted to create a rule to block certain top level domains like .ru or .ga or .eu
Does anyone have any suggestions on how to do that? I haven't found a way to do a wildcard
thanks!
↧
↧
Exchange 2013 - block advertisment emails
Hi, I have four exchange servers, 2 mailbox servers in a dag and 2 CAS servers.
users are receiving multiple advertisement and junk emails.
I block one by one using set-senderfilteringconfig
how to eliminate unneeded emails from Exchange before it reach user mailboxes.
Mashhour Faraj
↧
Some of the users can't connect to the mailbox after migration to Exchange 2013
Dear all,
I have the issue with number of the users who can't connect to the mailbox after migration from 2010 to 2013 Exchange server.
If I go to Exchange Proxy settings in Outlook it still points to old URL records, when I change URL to the Exchange 2013 it works ok, but after closing the Outlook the problem appears again.
Mailboxes are copied to Exchange 2013 without any problems
Please, help
Thank you in advance
↧
IMAP Search with UTF-8
Hi,
Does Exchange 2013 support UTF-8 charset for IMAP Search?
Cheers,
Saaj
↧
