Exchange 2013 Receiving Internet mail Issue

Hi,,
I am able to send mail to Internet,But i am unable to receive ,My local domain name is intra.mydomain.com
But my external domain name is mydomain.com.I enabled the MX record to mydomain.com and In My firewall router Port 25 forward to the exchange server.Still I am unable to receiving mail.
I tried the receiving connector.But something I missed.
Anyone help me what I missed here?
Thanks.

I tried Martien van Sijik.But I got
Attempting to find the SPF record using a DNS TEXT record query.
ExRCA wasn't able to find the SPF record.
Additional Details
No records were found.

Similar Messages

Is exchange 2013 support thunderbird mail

Is exchange 2013 support thunderbird mail?
Akhilraj

Yes. add imap account for email.
Add the following addon (or the latest version of the same add-on) for calendar
http://www.1st-setup.nl/extensions/exchangecalendar-3.2.0-Beta77.xpi

Exchange 2013 not delivering mails to Exchange 2010

I am upgrading exchange 2010 to exchange 2013 and currently in coexistence. I cutover the mx to deliver mail to 2013 cas VIP last night and no mail was being received by the 2010 mailboxes, it was all being queued on the 2013 mailbox servers (mailbox
and cas servers are separate in this deployment.) There are only a few 2013 mailboxes as I have not yet started migrating them. These 2013 internal mailboxes can not send to exchange 2010 either, but 2010 can send to 2013. 2013 to 2013 mail works
fine. I have read somewhere about an issue with a receive connector having the same ip range that includes the mailbox servers, but I'm not clear on really which mailbox servers it is alluding to.
All the exchange 2010 servers are all on the 10.1.1.* network. Exchange 2013 CAS servers are all on the 10.1.1.* network and the 3 exchange mailbox servers are on 10.1.1.*, 10.1.2.* and 10.30.5.*. Only 1 AD site. On one of the 2010 receive
connectors there is a scope of 10.1.1.0/24 I'm wondering if this is the culprit and by removing it should fix the problem. Any other ideas would be appreciated.

Exchange 2013 users are unable to send emails to exchange 2010 users then check your connectors on Exchange 2013 Mailbox server. and yes if you have overlapping of scopes in different connectors then this can happen.
Kindly mark this as answer if found helpful. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Modifying Connectors for Receiving Internet Mail - Anonymous setting?

I have a mail reflector for my domain to deliver mail on an alternate port, other than 25 because my ISP blocks port 25. I have the following default receive connectors:
Default Client Font End Transport (FrontEnd Transport) - TLS, Basic, Integrated, Exchange users, port 587
Default Client Proxy (Hub Transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange Server Auth, Exchange Servers, Exchange users, port 465
Default Front End Transport (FrontEnd Transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange server auth, Exchange Servers, Legacy Exchange Servers, Anonymous Users, port 25
Default Hub Transport (Hub transport) - TLS, Basic, Offer Basic after TLS, Integrated, Exchange Server Auth, Exchange Servers, Legacy, Exchange Users, port 2525
Default Outbound Proxy Frontend Transport (Frontend transport) TLS, Enable domain security, Basic, Offer basic after TLS, integrated, Exchange server auth, exchange servers, anonymous, port 717
Issue: When I initially had mail forwarded to port 2525, I received a mail delivery system message: host mail.skincdc.com[69.250.204.88] said: 530 5.7.1 .Client was not authenticated (in reply to MAIL FROM command).
I modified the “Default Hub Transport” connector to allow Anonymous Users in addition to what I already had selected in the security settings. Voila, email is delivered to my exchange server from external domains.
I wasn’t sure if adding Anonymous Users to this connector would pose any issues. In order to try an alternate port, I changed my registrar to port 2626 and created a new receive connector Hub Transport, with only Anonymous
Users and port 2626. I saw the initial connection in my TMG firewall logs, but mail never made it to my exchange server, and I wasn’t receiving the above error message right away as before. Disabling this new rule and modifying the firewall back to port 2525,
email immediately was delivered. So can I just leave my Default Hub Transport receive connector as is with the security settings and Anonymous set? Thanks.
Next….getting email to send out on a different port than 25 to external domains. Still having issues with this one.
-SK

Hi Slevin
According to your setup you would need to receive emails on different port apart from 25
You can do the following thing
1) Create a dedicated receive connector for your ISP domain
2) Grant relay permission only to your ISP subnet and IP ranges
3) Change the port to your desired number on which you need to receive emails from them
4) Disable the default receive connector since its not required anymore
So the mail-flow for inbound will be in the following type
Inbound
From Internet - Mails comes to your ISP - ISP delivers to your firewall on different port - then it comes to exchange server
Let me know if you have any confusions on this and i will be able to help you further
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange 2013 cannot deliver mails

Hello,
We purchased and installed an Exchange server 2013 and a domain name ''alaa.com''. Just before purchasing the domain name, we installed exchange, we kept almost everything in default setting and we added an MX INTERNAL Send Connector. We were able to send and
receive internal mails. However, when we purchased the domain name and configured the MX record to point to mail.alaa.com the following happened:
1/ we can send external mails
2/ internal mails leave the Drafts folder but never delivered (sent but not received).
3/ Cannot receive mails sent from the internet. However we receive an email from [email protected] that says this:
http://txt.do/138s
and sometimes this:
http://txt.do/138a
Please, this is urgent, We would really appreciate your help.

Hi,
I cannot see reverse DNS record for "sst.com.tn".
You must create reverse DNS record for delivery to external mail address.
Also, I cant open link http://txt.do/138s and http://txt.do/138a

Exchange 2013 ECP and DAG issue

Good Day,
We have Exchange 2013 setup in Coexistence with Exchange 2007. Everything is working well except for two small issues I have noticed.
Current Setup of 2013:
SiteA:
2x CAS Servers on Windows 2012 R2 configured with windows NLB (Internet Facing).
2x MBX servers Configured in a DAG also running on Windows 2012 R2.
SiteB:
2x CAS Server on Windows 2012 R2.
2x MBX servers Configured in a DAG also running on Windows 2012 R2.
Issues I am having:
Issue 1:
When working on the ECP:
I can do all tasks on servers in the same site but get some errors when trying to do tasks on servers in the other site.
When trying to Activate a DB copy on the DAG at SiteB I get "The Microsoft Exchange Replication service does not appear to be running on Server name"
And just trying to go to the properties of a server at SiteB "An error occurred while accessing the registry on the server servername"
This happens vice versa.
I can access all servers on the same site but not between sites with some tasks.
I have made sure firewall is disabled and remote registry is indeed running but no luck.
From a network perspective all ports are open between the sites.
Issue 2:
When I reboot a DAG member with the active mailbox databases for testing outlook connectivity I get two issues.
Then I cannot access ECP at all until the server is up again.
Outlook keeps staying on trying to connect until it is reopened.
Any Ideas?
I will gladly give more information if needed.
Thank You
Riaan Rourke
Senior System Engineer

Since I don't see this with Hyper-V I'll assume this is on ESX. Please let me know it that's not correct.
In terms of virtualization best practices - whose list was that :)
There are multiple configuration things that you *MUST* do when using WLBS on ESX. It will depend upon multiple things in the environment. I'd start with this
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1556
Fix that, and chances are the other item will be also remediated.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 Outlook Anywhere connection issues when using F5 VIP

Hello,
We are in the process of deploying Exchange 2013 into our Exchange 2010 Org. We are using an F5 to load balance all services. We are doing some initial testing and have not cut over autodiscover or other URLs yet to 2013. We are using host files
on the local testing machines to point the URLs to 2013. OWA, Activesync, ecp work with no issue through the F5 VIP. However, we are having issues with Outlook. If our host file entries point to a single server, Outlook functions
normally. If the host file entries point to the F5 VIP, it keeps prompting for creds and will never connect.
Just wondering if anybody has run into this or has any guidance as far as OA and F5 deployment.
Thanks

Hi,
Please check your Load Balance configuration and make sure the namespace used for Load Balance has been included in the Exchange certificate. For example: mail.domain.com and autodiscover.domain.com.
If possible, please share your load balance configuration with us for further analysis. Here are some references about the Load Balance Scenario:
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 Public Folder Accessability Issues

After migrating from Exchange 2010 to Exchange 2013 we are experiencing random issues accessing Public Folders. Issues range from a hung server requests to on-screen errors like this one:
“Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance”
We are using groups to manage permissions, verified that they are mail enabled, and have used the following PS command to re-propagate permissions:
./AddUsersToPFRecursive.ps1 -TopPublicFolder "%folder%" -User "%groupname" -Permissions %permissionlevel"
The odd thing is that if the user bounces between on of their Inbox folders then back to one of the Public folders or restarts Outlook it seems to resolve itself.
Ideas?

Hi Niko,
Firstly, apologies for the delayed update...
We are still experiencing random loss of access to Public Folders, I would think it would be so much easier if I could replicate the problem quickly and easily however that is not the case as I ran into this issue again this morning.
I am really at a loss for explanation, what I can offer is when we had migrated from Exchange 2000 to Exchange 2010 I had to export the PF out to a pst file prior to importing them on the new server installation. While migrating from Exchange 2010
to Exchange 2013 we did follow the migration process.
Here is what our current settings from Get-OutlookAnywhere -Server %Server%
RunspaceId                         : e2e4f324…
ServerName
: %server%
SSLOffloading
: True
ExternalHostname
: <set>
InternalHostname                   : <set>
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods
: {Basic, Ntlm, Negotiate}
XropUrl
ExternalClientsRequireSsl
: True
InternalClientsRequireSsl
: True
MetabasePath
        : IIS://%server%/W3SVC/1/ROOT/Rpc
Path
: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags
ExtendedProtectionSPNList
AdminDisplayVersion
: Version 15.0 (Build 775.38)
Server                             : %server%
AdminDisplayName
ExchangeVersion
: 0.20 (15.0.0.0)
Name
: Rpc (Default Web Site)
DistinguishedName
: CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=%server%,CN=Servers,CN=Exchange
                    Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=%company%
Software,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%domain%,DC=net
Identity                           : %server%\Rpc (Default Web Site)
Guid
: 0bf08d0e…
ObjectCategory
: %domain%/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass
: {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged
: 5/5/2014 3:08:31 PM
WhenCreated
: 2/20/2014 2:13:17 PM
WhenChangedUTC
: 5/5/2014 8:08:31 PM
WhenCreatedUTC
: 2/20/2014 8:13:17 PM
OrganizationId
OriginatingServer
: %server%
IsValid
: True
ObjectState
: Changed

Exchange 2013 Sp1 Test-PopConnectivity issues in coexistence

I'm having issues with Pop3 in a coexistence environment with 2007. The 2013 roles are split- cas servers and mailbox servers.
If I run "Test-PopConnectivity -ClientAccessServer:cas01 -MailboxCredential:(Get-Credential domain\test.exchange) |fl"
I get the error "Service MSExchangePOP3 was not found on <mailboxserver>" and a DR Watson is created.
Ok I know there is a front end and a back end component to Pop3. This error is expecting to find the front end component on a mailbox server? So is it just an issue because the roles are split or is it to do with proxying through the CAS not being enabled?
Pop3 does not use a send connector- just a receive connector right? So how would it Proxy- if it does
Confused
Tony

Hi,
Is “cas01” the front end server?
Did you use the exchange 2013 MailboxCredential to test the Pop Connectivity?
Make sure the pop is enalbed for users and the pop services are started.
Proxy and redirection for POP and IMAP:
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 user cannot mail 2010 user

Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7
Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.
I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere
on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed
- thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?
Cheers, db.

Hi Dennis,
if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".
1. run a Powershell or CMD
2. telnet exchange2013server 25
Does it connect using the Exchange 2013 CAS / Transport Server Name?
If no, please check
1. is there any anti Virus / Firewall Software blocking the Connection?
2. is there any Firewall on the Network blocking the SMTP Connection?
3. does your receive connector include the subnet of your Exchange 2013 CAS server?
If you cannot connect verify please the remote IP range includes your new servers , check it running
Get-ReceiveConnector | fl name,binding,remoteipranges
from Powershell. If required, use set-receiveconnector to Change it.
http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx
Regards,
Martin

Exchange 2013 Public Folders external issues

Hello,
I am having some issues with gaining access to my public folders externally.
OS: Windows Server 2012 Datacenter
Exchange: 2013 with SP1
Domain: i.client.local
External & internal hostname: ex01.client.dk
I have tried from Windows 7 with Outlook 2010, and Windows 8 with Outlook 2013. (I have also tried to apply patch from: http://support.microsoft.com/kb/2839517)
If I try to access public folders, I get this error:
Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange.
If I try to access public folders with cache enabled, I get this error: http://support.microsoft.com/kb/2788136
I have tried deleting all public folders, public folder databases, and the related mailbox database. And creating all again, however
with same result.
[PS] C:\Windows\system32>Get-PublicFolder | fl
RunspaceId : a90240df-5376-4397-8c2a-4291a924e911
Identity : \
Name : IPM_SUBTREE
MailEnabled : False
MailRecipientGuid :
ParentPath :
ContentMailboxName : Public
ContentMailboxGuid : d97cbc5c-4c39-47c7-8b56-764396dc32ca
EformsLocaleId :
PerUserReadStateEnabled : True
EntryId : 00000000134872D0905F3849B78B9128A8B0CBE30100DF9CA23E198A714AB68A74F2C09F11020000000000020000
DumpsterEntryId : 00000000134872D0905F3849B78B9128A8B0CBE30100DF9CA23E198A714AB68A74F2C09F110200000000000A0000
ParentFolder : 00000000134872D0905F3849B78B9128A8B0CBE30100DF9CA23E198A714AB68A74F2C09F11020000000000010000
OrganizationId :
AgeLimit :
RetainDeletedItemsFor :
ProhibitPostQuota : Unlimited
IssueWarningQuota : Unlimited
MaxItemSize : Unlimited
LastMovedTime :
FolderSize : 0
HasSubfolders : True
FolderClass :
FolderPath : {}
DefaultFolderType : None
ExtendedFolderFlags : SharedViaExchange
MailboxOwnerId : i.client.local/Public
IsValid : True
ObjectState : Unchanged
[PS] C:\Windows\system32>Get-PublicFolder \ -GetChildren
Name Parent Path
Mira \
[PS] C:\Windows\system32>Get-OrganizationConfig | FL RootPublicFolderMailbox
RootPublicFolderMailbox : d97cbc5c-4c39-47c7-8b56-764396dc32ca
[PS] C:\Windows\system32>Get-Mailbox -PublicFolder | FL Name,ExchangeGuid
Name : Public
ExchangeGuid : d97cbc5c-4c39-47c7-8b56-764396dc32ca
I can easily access the Exchange-server internally and externally.
XML from Outlook "Test autoconfiguration" tool.
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Alex Mathiasen</DisplayName>
<LegacyDN>/o=client/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=8cfd63e296ee4d6d99fa842a78584d43-Alex Mathiasen34410</LegacyDN>
<AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
<DeploymentId>823f5581-e9a1-4b8c-a79e-afcbe9900267</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<MicrosoftOnline>False</MicrosoftOnline>
<Protocol>
<Type>EXCH</Type>
<Server>[email protected]</Server>
<ServerDN>/o=client/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
<ServerVersion>73C0834F</ServerVersion>
<MdbDN>/o=client/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
<PublicFolderServer>ex01.client.dk</PublicFolderServer>
<AD>ex01.i.client.local</AD>
<ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
<EwsUrl>https://ex01.client.dk/ews/exchange.asmx</EwsUrl>
<EmwsUrl>https://ex01.client.dk/ews/exchange.asmx</EmwsUrl>
<EcpUrl>https://ex01.client.dk/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=i.client.local</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=i.client.local</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=i.client.local</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=i.client.local</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=i.client.local</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=i.client.local</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=i.client.local</EcpUrl-photo>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=i.client.local</EcpUrl-extinstall>
<OOFUrl>https://ex01.client.dk/ews/exchange.asmx</OOFUrl>
<UMUrl>https://ex01.client.dk/ews/UM2007Legacy.asmx</UMUrl>
<OABUrl>https://ex01.client.dk/OAB/fa8a9ffb-9d6c-4d66-acec-e23c2cbc63d1/</OABUrl>
<ServerExclusiveConnect>off</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>ex01.client.dk</Server>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
<EwsUrl>https://ex01.client.dk/ews/exchange.asmx</EwsUrl>
<EmwsUrl>https://ex01.client.dk/ews/exchange.asmx</EmwsUrl>
<EcpUrl>https://ex01.client.dk/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=i.client.local</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=i.client.local</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=i.client.local</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=i.client.local</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=i.client.local</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=i.client.local</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=i.client.local</EcpUrl-photo>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=i.client.local</EcpUrl-extinstall>
<OOFUrl>https://ex01.client.dk/ews/exchange.asmx</OOFUrl>
<UMUrl>https://ex01.client.dk/ews/UM2007Legacy.asmx</UMUrl>
<OABUrl>https://ex01.client.dk/OAB/fa8a9ffb-9d6c-4d66-acec-e23c2cbc63d1/</OABUrl>
<ServerExclusiveConnect>on</ServerExclusiveConnect>
<EwsPartnerUrl>https://ex01.client.dk/ews/exchange.asmx</EwsPartnerUrl>
<GroupingInformation>Default-First-Site-Name</GroupingInformation>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basic, Fba">https://ex01.client.dk/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://ex01.client.dk/owa/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>ex01.client.dk</Server>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
<EwsUrl>https://ex01.client.dk/ews/exchange.asmx</EwsUrl>
<EmwsUrl>https://ex01.client.dk/ews/exchange.asmx</EmwsUrl>
<EcpUrl>https://ex01.client.dk/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=i.client.local</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=i.client.local</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=i.client.local</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=i.client.local</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=i.client.local</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=i.client.local</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=i.client.local</EcpUrl-photo>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=i.client.local</EcpUrl-extinstall>
<OOFUrl>https://ex01.client.dk/ews/exchange.asmx</OOFUrl>
<UMUrl>https://ex01.client.dk/ews/UM2007Legacy.asmx</UMUrl>
<OABUrl>https://ex01.client.dk/OAB/fa8a9ffb-9d6c-4d66-acec-e23c2cbc63d1/</OABUrl>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>ex01.client.dk</Server>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<ASUrl>https://ex01.client.dk/ews/exchange.asmx</ASUrl>
<EwsUrl>https://ex01.client.dk/ews/exchange.asmx</EwsUrl>
<EmwsUrl>https://ex01.client.dk/ews/exchange.asmx</EmwsUrl>
<EcpUrl>https://ex01.client.dk/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=i.client.local</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=i.client.local</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=i.client.local</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=i.client.local</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=i.client.local</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=i.client.local</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=i.client.local</EcpUrl-photo>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=i.client.local</EcpUrl-extinstall>
<OOFUrl>https://ex01.client.dk/ews/exchange.asmx</OOFUrl>
<UMUrl>https://ex01.client.dk/ews/UM2007Legacy.asmx</UMUrl>
<OABUrl>https://ex01.client.dk/OAB/fa8a9ffb-9d6c-4d66-acec-e23c2cbc63d1/</OABUrl>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
<PublicFolderInformation>
<SmtpAddress>[email protected]</SmtpAddress>
</PublicFolderInformation>
</Account>
</Response>
</Autodiscover>

I can't access the public folders at all. Trying to access the public folders, result in the error from the following page: http://support.microsoft.com/kb/2788136,
or "Cannot expand the folder..."
It is affecting all users using this Exchange-server. I am actually having this error on two different Exchange-serverens at two different companies at the moment.
And it is a fresh Exchange 2013 environment in both cases.
PS: I discovered that the public folders works inside the same domain as the Exchange-server, however users can't access the public folders externally.
I also tried to use the Exchange-server as DNS, in order to be able to resolve i.client.local:
<PublicFolderInformation>
<SmtpAddress>[email protected]</SmtpAddress>
</PublicFolderInformation>
however I am still unable to open the public folders, even after being able to resolve the DNS name i.client.local.

Exchange 2013, scan-to-Mail, Attachments broken down to mime tipes

Good day
I recently installed Exchange 2013 to our domain.
The problem i'm facing is that any scan to email document gets delivered as the following :
This is a multi-part message in MIME format.
--DC_BOUND_PRE_<1361347488.00267327e1cb>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
--DC_BOUND_PRE_<1361347488.00267327e1cb>
Content-Type: application/pdf; name="20130220090448407.pdf"
Content-Transfer-Encoding: base64
Content-Dis;
filename="20130220090448407.pdf"
JVBERi0xLjQKJeLjz9MKNCAwIG9iago8PC9UeXBlL1hPYmplY3QKL1N1YnR5cGUvSW1hZ2UK
L1dpZHRoIDE2NTYKL0hlaWdodCAyMzM5Ci9CaXRzUGVyQ29tcG9uZW50IDEKL0NvbG9yU3Bh
Y2UvRGV2aWNlR3JheQovRGVjb2RlWzEgMF0KL0xlbmd0aCA0ODQxNzMKPj4Kc3RyZWFtCgAA
AAAAAAAAAAAAAEAl+3vv///+gAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF9
gAAAbgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFZK26AAAAAAAAAAAAAAA
And it goes on for this for a couple hundred more lines.
I have tested the following
Scanning to any email address outside my domain, work 100%
Any scanner sending mail-to-pdf from outside my organization it get delivered as above
I have changed smtp servers to our ISP and that also delivered as abve
I change the sending address of scan-to-mail machine to gmail account, also delivered as above, but to my non domain email address it works perfectly
Please help

one of our clients had the same problem before, he have Richo printer with scanner witch is scanning to pdf file attached to email , this printer is working fine by using Exchange 2010 but has that problem after the migration to exchange 2013, this
problem is totally fixed after installing Exchange SP1 (CU4). I found others say this problem is fixed by just installing CU1.
for more information about content conversion
http://technet.microsoft.com/en-us/library/bb232174.aspx#External

Outlook 2013 / Exchange 2013 : Shared mailboxes - Mail stuck in outbox (non-cached), Mail sends but doesn't get received (cached).

Hello,
We are currently experiencing some weird behaviour in Outlook 2013 since we added Shared Mailboxes.
When we run Outlook 2013 with cached mode
enabled:
- I create a new e-mail and send it.
- The e-mail goes to the outbox, and get's 'send'.
- None of the recipients receives the e-mail.
When we run Outlook 2013 with cached mode
disabled:
- I create a new e-mail and send it.
- The e-mail goes to the outbox, but remains there.
Now to make things even more bizarre:
When I switch from 'cached'-mode to 'non cached'-mode, I see all the e-mail that were 'send' in cached-mode stuck in the outbox.
Note: The DNS server configuration in Exchange is correct.

Hi,
How about sending on OWA? Does the issue exist?
To troubleshoot the issue, let's run Outlook in Safe Mode to determine if 3rd-party add-ins are related:
Press Win + R and type “outlook.exe /safe” in the blank box, then press Enter.
If there’s no problem sending emails in Safe Mode, disable the suspicious add-ins to verify which add-ins caused this issue.
Please also disable the firewall and anti-virus program to send the emails again, in many scenarios the protection may cause the issue.
Please also keep Exchange and Outlook patched to the latest.
Regards,
Melon Chen
TechNet Community Support

Exchange 2013 - Cannot sent mail warning to user (Quota)

Hi all,
I have an enviroment with Exchange Server 2013 SP 1 (Version 15.0 (Build 847.32)). (DAG)
My problem is that my users not recieve mail of notification (warning).
I did a lot search, but i didnt found any solution.
I already moved a mailbox to another database, but the user received mail once.
Any idea?
I see in forum MS that it can be a problem of Exchange.
Marco

Hi Marco,
From your description, I recommend you use the following cmdlets to verify the quota status of mailbox.
If you want to verify the status of individual mailbox quota, use the following cmdlet:
Get-MailboxStatistics DisplayName | ft *quota*,*size -AutoSize –Wrap
If you want to verify the status of the mailbox quota for all the mailboxes that are hosted on a database, use the cmdlet below:
Get-MailboxStatistics -Database DatabaseName | ft displayname,*quota*,*size -AutoSize –Wrap
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Internet/Mail issues

I have searched through this (and other) forums but haven't been able to find an answer.
I have just upgraded to ADSL2 in australia.
Here are my issues.
I can browse (Safari 2.0.4 and 3beta) bou only SOME pages. Even www.apple.com.au will only load text (no images)
iTunes will NOT access the music store.
Now here's the interesting bit.
I am runnung parallels and ALL sites can be accessed IN FULL. no probs at all.
What can I do to my OS (or anything for that matter) so that I don't have to use parallels to surf??
any help would be AWESOME
Am using D-Link DSL 504-T modem/router via new Airport Extreme

all sorted.
My ISP gave me DNS servers for regular ADSL.
ADSL2 had different DNS servers and all sorted.

Exchange 2013 Receiving Internet mail Issue

Similar Messages

Maybe you are looking for