We have a split SMTP domain. Email from the outside world is delivered to a central mail platform at our Geneva office. Mail is the routed to the correct mail server. A freshly built 2013 server has been deployed for a group of users. The 'Accepted Domain' has been configured as an 'Internal Relay' domain and we have a dedicated 'Send Connector' set up to route unknown email addresses to Geneva; this has been working during testing for internal>external tests and internal>internal (relay to other mail server) tests. However when we came to open up SMTP Geneva>Ex2013 for mail delivery emails are getting bounced back to the sender with the following NDR:

Delivery has failed to these recipients or groups:

<user@domain.com>

The email address you entered couldn't be found. Please check the recipient's email address and try to resend the message. If the problem continues, please contact your helpdesk.

The following organization rejected your message: <London Mail Server>.

Diagnostic information for administrators:

Generating server: <Geneva Mail Server>

<user@domain.com>

<London Mail Server>

Remote Server returned '<<London Mail Server> #5.1.1 smtp; 550 5.7.1 Unable to relay>'

I have verified the users exist and mailboxes are online, sending email out works, but a reply fails. I have bypassed the Geneva server and performed a manual telnet into Ex2013 from outside the network and I was successfully able to send a test email to a Ex2013 mailbox from an external email address that would have failed using a normal email.

Any assistance in understanding why Ex2013 would not be accepting the mail from Geneva and just delivering it to the mailbox would be appreciated and it sounds like it's perhaps trying to relay that email back to Geneva and failing.

Thanks,

PT

Because of a reorganisation I have to migrate all my mailboxes to a different domain and exchange server. The migrating isn't the real problem.

1st problem

My boss wants an auto-reply on all mailboxes saying we are using a new mail adress. I thought of doing this using a DL and forward to a new mailbox on which I would set an auto-reply using outlook but he also wants everyones mail forwarded to the new mailbox.How can I manage this without manually setting this on every mailbox? If I script the mailbox to forward to the new mailbox will the forward to the DL still work with the auto-reply?

2nd problem

I have a lot of mail enabled users. Can I also set an auto-reply and forward on these users?

Thanks in advance for the help

Hello all,

I am dealing with a strange case where sending messages from my personal account (office365) to multiple recipients inside the same organization (Exchange on-premise infrastructure) it seems that this message is split into multiple copies (different network-id).

Example

Sender: user@office365.com

Recipient: user1@domain.com ; user2@domain.com

The message comes inside the organization in two instances with two distinct network message id. Only thing I can think of is a UTM from Sophos controlling the mail flow in a way (building queues as far as I am aware) but could this be case?

Any ideas are welcome, thanks.

We are using Exchange 2013, trying to use message tracking to determine if a message that was sent to us was rejected, I can run the messagetracking powershell command and I get reslults. would there be a "reject" event id for these messages?

Thanks

Pat

hi,

I'm not enjoying Exch2013, the lack of a "proper" admin console is a pain and I'm having trouble getting the required diagnostic/tracking information out of PShell to fix my problem.

I've installed Exch2013 RC1 on a new 2012r2 Domain, the install went OK and there were no obvious issues however internal email's wouldn't deliver, they appear in Sent Items but aren't received in the internal rcpt's inbox.

while trying to fix the problem, I installed ExchCU7 and bingo everything sprang to life and mail was working, inbound/outbound & internally - so I assumed the service pack/update had fixed it but the next day I rebooted the server and to my horror, I'm back where I started - no mail flow.

One single test message which I sent outbound using the Web mail, rather than Outlook did arrive but hours after I sent it?  confused.com

this is running on a HV-2012r2 as a VM, with a dedicated Nic and plenty of Fixed VD storage.

Any help/advice would be greatly appreciated.

I'm very close to removing Exch2013 and re-installing but I worry this would cause more issues.

Thanks Iain

Dear all,

Maybe you could help to resolve this issue:

For some reason I can't send e-mails from 2nd Exchange server when 1st is disabled.

At the first look all settings are similar between those two servers, but the problem still exists

Please, help

Thank you in advance

Hey Guys,

since we upgraded from Exchange 2010 to Exchange 2013 (SP1) any SMTP Receive Connector we create (including the default one) show the same strange behavior. When you send an email (no matter if internal or external) it sometimes takes up to 30 seconds for the exchange server to acknowledge the message. Using the SMTP log I see the following entries:

2014-08-08T08:58:29.053Z,                       MAIL FROM:<test@test.de>,

2014-08-08T08:58:29.053Z,                       SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions

2014-08-08T08:58:29.053Z,                       receiving message

2014-08-08T08:58:29.053Z,                       250 2.1.0 Sender OK,

2014-08-08T08:58:29.053Z,                       RCPT TO:<fake@mail.de>,

2014-08-08T08:58:29.053Z,                       250 2.1.5 Recipient OK,

2014-08-08T08:58:29.053Z,                       DATA,

2014-08-08T08:58:29.053Z,                       354 Start mail input; end with <CRLF>.<CRLF>,

2014-08-08T08:58:29.068Z,                       Proxy destination(s) obtained from OnProxyInboundMessage event

2014-08-08T08:58:40.960Z,                       "250 2.6.0 <5160cd2a-9160-4a35-9007-1f9c17761bc0@--------> [InternalId=17776869639170, Hostname=-----------] Queued mail for delivery",

As you can see there’s a delay between 08:58:29 and 08:58:40 where nothing happens. The sending smtp service waits for the server to acknowledge the message – at least that’s what I guess. Since we use this kind of connector a lot for internal mail traffic with non-Outlook clients it is essential to get rid of this issue. For example using Trac Ticket system or Subversion also leads to slow or delayed responses. Creating a ticket in Trac sometimes takes up to a Minute since several emails are created and sent in background processes. We didn’t have this issue with Exchange 2010 and I actually couldn’t find much using google. 

Since there's no error showing it's quite difficult to track down the issue. After I did some researching I tried configuring the receive connector to change this behavior but nothing helped. I tested the following options:

-         MaxAcknowledgementDelay 00:00:00

-         TarpitInterval 00:00:00

-         MessageRateSource None

-         MessageRateLimit unlimited

-         MaxInboundConnectionPercentagePerSource: 20

-         MaxInboundConnectionPerSource 100

 I Also took a look at the Throttling Policies with no luck either. 

Calling the Microsoft support simply led to the typical “we do not support 3^rd party issues”. In fact this is NOT a third party issue but arguing didn't help. I tested every possible solution I found and after weeks I simply dont' have the slightest idea any more, how to solve the problem.

Some information about our Exchange environment:

-         Exchange DAG with 2 servers

-         Windows Server 2012 (latest updates)

-         Exchange 2013 SP1 installed

Disabling DAG members also didn’t help and all the members show the same behavior no matter which connector I choose to use.  

Any hint or idea would be very much appreciated.

Thanks,

Christoph

I am having an issue with setting the max send and receive size on Exchange 2013.  I keep getting the following error when I attempt to send a 20 meg file server to an internal exchange account OR if I attempt to send a 20 meg file from the exchange server to an external account:  #550 5.3.4
ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##

I have checked the mail sizes and below is the report.  I currently have both send and receive set to 100MB.  Is there some other setting in 2013 that I am not aware of?

AnonymousSenderToRecipientRatePerHour                       : 1800
ClearCategories                                             : True
ConvertDisclaimerWrapperToEml                               : False
DSNConversionMode                                           : UseExchangeDSNs
ExternalDelayDsnEnabled                                     : True
ExternalDsnDefaultLanguage                                  :
ExternalDsnLanguageDetectionEnabled                         : True
ExternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
ExternalDsnReportingAuthority                               :
ExternalDsnSendHtml                                         : True
ExternalPostmasterAddress                                   :
GenerateCopyOfDSNFor                                        : {}
HygieneSuite                                                : Standard
InternalDelayDsnEnabled                                     : True
InternalDsnDefaultLanguage                                  :
InternalDsnLanguageDetectionEnabled                         : True
InternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
InternalDsnReportingAuthority                               :
InternalDsnSendHtml                                         : True
InternalSMTPServers                                         : {}
JournalingReportNdrTo                                       : <>
LegacyJournalingMigrationEnabled                            : False
LegacyArchiveJournalingEnabled                              : False
LegacyArchiveLiveJournalingEnabled                          : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling                : False
MaxDumpsterSizePerDatabase                                  : 18 MB (18,874,368 bytes)
MaxDumpsterTime                                             : 7.00:00:00
MaxReceiveSize                                              : 100 MB (104,857,600 bytes)
MaxRecipientEnvelopeLimit                                   : 500
MaxRetriesForLocalSiteShadow                                : 2
MaxRetriesForRemoteSiteShadow                               : 4
MaxSendSize                                                 : 100 MB (104,857,600 bytes)
MigrationEnabled                                            : False
OpenDomainRoutingEnabled                                    : False
RejectMessageOnShadowFailure                                : False
Rfc2231EncodingEnabled                                      : False
SafetyNetHoldTime                                           : 2.00:00:00
ShadowHeartbeatFrequency                                    : 00:02:00
ShadowMessageAutoDiscardInterval                            : 2.00:00:00
ShadowMessagePreferenceSetting                              : PreferRemote
ShadowRedundancyEnabled                                     : True
ShadowResubmitTimeSpan                                      : 03:00:00
SupervisionTags                                             : {Reject, Allow}
TLSReceiveDomainSecureList                                  : {}
TLSSendDomainSecureList                                     : {}
VerifySecureSubmitEnabled                                   : False
VoicemailJournalingEnabled                                  : True
HeaderPromotionModeSetting                                  : NoCreate
Xexch50Enabled                                              : True

We have a policy where certain administrative staff need to be blind copied on all emails sent to certain distribution groups. Since this could be either a traditional or dynamic distribution group, and because the people copied could change at any given time, we decided that achieving this functionality via Transport Rules seemed to make the most sense. The rule (in Exchange 2010, by the way) was:

"When any of the recipients in the To or Cc fields is 'group1@domain.com,group2@domain.com,group3@domain.com' Blind Carbon Copy 'manager@domain.com'"

This worked fine for the most part, until we discovered that if someone BCCs one of those groups, then of course the rule doesn't capture that. There are also no conditions specific to people who were BCC'ed. I thought I could tweak the rule to use the condition"If recipient's address contains specific words" and plug the addresses of the groups there. This of course works awesome if the recipient specified in the rule is a person, but if the address is that of a group, it doesn't work (this doesn't entirely make much sense to me as the rule should be pretty generic, but anyway...).

Does anyone have any insight into this or able to offer any suggestions for workarounds?

I currently have a 2010 environment and I am migrating to 2013.  I have two servers built and began to try to setupauthenticated relay and I got nowhere and really really confused.  I would think this would be a really simple implementation but apparently not :(  Long story short, I just want to get back to the default settings for the receive connectors on a dual role clean Exchange install.  

Are the below settings correct for the default install of Exchange?  Is anonymous included in the default frontend connectors?  If so, can someone please explain this to me?  

The reason I ask is that I would expect that when i telnet to the mail server on 25 and try to send an email, that I should not be able to do so.  But then I think about it and think that external senders would be unauthenticated and now i've confused myself. 

In that telnet session if i try to send an email to an external domain name it says unable to relay.  If i send to an accepted domain it works.  But isnt that a security risk to allow any device on the inside to send unauthenticated to an employee?

I really appreciate any clarification you can add.  

Here is my output for Get-ReceiveConnector | fl Name,AuthMechanism,RemoteIPRanges,TransportRole,permissiongroups,MaxMessageSize

NNatic

I have a very strange situation where my Exchange Server 2010 can't receive any gmails with attachment size over 50KB. It has zero problems with all other e-mails coming in except hosted by gmail.com. I can receive plain gmails, or with attachment up to 50KB. Anytime a gmail with attachment bigger than 50KB, it will show:

Hi guys,

We had a fresh Exchange Server 2013 install. It had been working fine for a day, then all in a sudden, the outgoing emails did not go out and stuck in queue. From the NDR, it says:

Remote Server returned '554 5.4.4 SMTPSEND.DNS.InvalidData; DNS returned an invalid response for this domain'

From the Queue viewer, the last error shows:

I am pulling my hair off to try to fix this problem. Any advise and ideas would be much appreciated.

Henry

I have a single multi-role Exchange 2013 server and it would appear that it's not properly maintaining the temp files for the transport service.  I still have all those folder locations at their default and the problem folder is c:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Temp

I never had a problem with this in Exchange 2007 but I am used to running a PowerShell script nightly to clean up the IIS log files.  Do I need to do something similar for this temp folder?  Is there a setting I can adjust so that Exchange will limit the size of this folder itself?  If I stop the transport service and delete the files here will I lose anything?

Any suggestions or insight would be greatly appreciated.

Hi All

I am currently planning a migration and could really do with some advice/shared experience. I have a bunch of users currently using a hosted exchange enviroment hosted via a 3rd party and Citrix. Migration will involve bringing these users in-house to my exchange 2013/Server 2012R2 where I already have other users working from (They use a different email address for the context of this scenario). Due to resources and to minimise downtime I want to migrate users from hosted to my internal exchange in a couple of phases/chunks over a few weeks.

What I intend to do is keep the MX record pointing to the hosted platform until all users are migrated accross but in the meantime set mailbox forwards on first group of desired users forwarding them to my internal exchange via another temporary domain I have purchased for the migration. I added the currently externally hosted email domain to my authorised domain list in Exchange which worked but of course users already using my exchange who email a user who hasnt been migrated yet get an NDR because their mailbox doesnt exist yet and its trying to route the email internally. I need something where if the mailbox doesnt exist internally to route to the internet/normal MX destintion

I have been reading about External Relay Domains and it sounds like this might be what I am after. Can anyone verify if this is what I am looking for? I want this all to be transparent to all users.

I've seen a few older postings about this, but none of them have a solution.  We've upgraded to Exchange 2013 and we're using Public Folder rules to forward messages. When we set the forward type to be "Leave message intact", the message never gets forwarded.  The other two options "Standard" and "Insert message as an attachment" work fine.  In Exchange 2007 the "Leave message intact" option worked also.  I've seen some suggestions to use transport rules, but that won't work for what we're trying to do, so I'm wondering if there's another workaround for this issue.

Thanks,

Richard

Thanks, Rich

Hi,

Is it possible to block users that have full mailbox access from opening/reading IRM protected email in the mailbox they have access to?

Celtic

Hi,

I have multiple mailbox servers. We are receiving emails from Gmail, Yahoo, etc.

The issue is that some users from outside (their own domain) are sending emails and their emails are stuck in a queue named

Server\Unreachable

After trying it rejects the email and users are getting this error message.

#<#4.4.7 smtp;550 4.4.7 QUEUE.Expired; message expired in unreachable destination
queue. Reason: There is currently no route to the mailbox database.> #SMTP#<o:p></o:p>

Can any one please help us in this regard?

Regards,

Anees

Hi There

We're running on an Exchange 2013 server. When users get a NDR (look OK at this time), but when forwarding the NDR to system admin, they get garbled into Chinese (or what looks like Chinese). Any ideas on solving this ?

Kind Regards
Kim

Kind Regards Kim

Hi,

Is there any way to disable Duplicate Message Detection?