xchange 2013 mail.que

May 13, 2019, 11:34 am

≫ Next: Mail sent using the wrong send connector

≪ Previous: Problem with receive mail from external address in exchange online

Started to have a problem with a Server 2012R2 with Exchange 2013 installed where the C: disk space was being eaten up rapidly for no reason. After some general housekeeping restarted the server and the Transport Service timed out and was left "starting". I had removed Trend Micro exchange software as well and have before seen issues with where transport agents had been left but this was not the case

Looked into C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue and see a 8GB mail.que file. I forced the service to stop and then moved all the files form that folder to another folder. Restarted the service OK... After a couple of hours the service had stopped again, so jumped back on and the mail.que file was already up to 2 GB with loads of logs that had been increasing rapidly. Trying to restart done the same again with the service being stuff on "starting"

Cant see any real reason why this should be happening so any ideas...? Don't want to keep removing the files in the folder to get the service to start

↧

Mail sent using the wrong send connector

April 9, 2019, 8:56 am

≫ Next: SMTP client mail frontend 587 not sending email using send as user.

≪ Previous: xchange 2013 mail.que

Hello, I have Exchange 2013 Organization with 2 sites. 2 servers in Site1 (CAS and MBX/HUB) and 2 servers in Site2, same roles.
I have Fortimail as Smart Hosts in each site. Both connectors has SMTP * with cost 10, but each one has the "Scoped send connector" checkbox checked, and only the corresponding server for that site. So, Site1 send connector has only MBX/HUB server on that site and Site2 the same. No DAG, separated servers with databases in each server,
The thing is that someone with a mailbox hosted in a database in server in Site2 send a mail, and the mail apparently goes through Site1 send connector. Got the mail and the header says that the sender is the fortimail from Site.
If I check delivery reports the mail appear as delayed and in the info says that the mail was sent to a remote site. I am scratching my head and thinking which log could I check to know the route is taking the mail to be sent using the wrong connector.
Something to say, the send connectors are using instead the direct fortimail records, a DNS zone with MX records inside. In site1 the mx record with cost 10 is the site1 fortimail and the mx record with cost 20 is the site2 fortimail. Same thing for DNS zone for site2, but fortimail for site2 has cost 10 and fortimail for site1 has cost 20. This is for failover, so if site2 lost connection with fortimail in site2, goest to site1 fortimail, but don´t know if this is happening because the fortimail is up and sending mails and only happens for this mailbox.
Is there a tracking log I can check?

↧

SMTP client mail frontend 587 not sending email using send as user.

May 13, 2019, 11:48 pm

≫ Next: Mail sent using the wrong send connector

≪ Previous: Mail sent using the wrong send connector

Hi there,

Thanks for reading my questions below.

I have configured my client frontend to send from IMAP client using port 587, it works on IMAP client. But I have given send as permission to user2 for the mailbox user1, I'm able to send using user1 for the mailbox user1, but unable send email using user2 for the mailbox user1. I would like to know how to send as user2 for the mailbox user1. (or) the send as permission only applicable to exchange connectivity?

Could you please answer my question and How to send using send as for IMAP client?

Thanks for your time.

Kannan

↧

Mail sent using the wrong send connector

April 9, 2019, 8:56 am

≫ Next: How to stop duplicated mails to be sent

≪ Previous: SMTP client mail frontend 587 not sending email using send as user.

↧

How to stop duplicated mails to be sent

May 16, 2019, 5:07 am

≫ Next: on-prem meeting rooms no longer accepting meetings from office 365 users, and not sending meeting accpetance email to user

≪ Previous: Mail sent using the wrong send connector

Hello

I have a system who is using Exchange Server 2013 to send mails to users

i need to prevent the mailbox account of this system for sending the same mail more than a time

↧

on-prem meeting rooms no longer accepting meetings from office 365 users, and not sending meeting accpetance email to user

May 16, 2019, 6:53 pm

≫ Next: Emails are slow leaving Outlook outbox

≪ Previous: How to stop duplicated mails to be sent

Hello,

We have Exchange 2013 on-prem in full hybrid mode with Exchange online, leveraging Centralized Mailflow. We also leverage AAD Connect to sync identities from on-prem AD to Office 365. Today, all of a sudden, users migrated to Office 365 are no longer able to book meetings against on-prem meeting rooms. all meeting rooms are still located in on-premise. When user sends a meeting invite to the meeting room, they do not receive an acceptance email from the meeting room, and the meeting does not appear on the meeting room calendar. I have re-ran the Hybrid config wizard, and also ran an initial sync in AAD connect...no luck.

I've verified that the value -AutomateProcessing is set to AutoAccept on these meeting rooms, and i've also tested setting the value: ProcessExternalMeetingMessages to True, but still no luck

I logged into the meeting room mailbox via OWA, and see meeting requests in the rooms inbox, message that displays is: “Your calendar couldn’t be checked to see whether this event conflicts with other events”

I've also followed this article, and verified all is correct in the calendar settings of the meeting room mailbox:

https://jasoncoltrin.com/2019/01/30/office365-resource-room-calendar-not-processing-accepting-meeting-requests/

From on-prem user to on-prem meeting room...all functions as expected. Please advise on how this can be resolved... issue seems to be with the hybrid side. (hybrid mailflow works fine, as well as free/busy across the hybrid)

I also noticed, when creating meeting invites from office 365, the Room List no longer shows available meeting rooms. seems to be related to above issue.

Thanks in advance

↧

Emails are slow leaving Outlook outbox

April 12, 2018, 10:58 pm

≫ Next: Replication issue for DHCP cluster in "Hot Stanby" mode

≪ Previous: on-prem meeting rooms no longer accepting meetings from office 365 users, and not sending meeting accpetance email to user

I have a few users in a remote site that complain of message sitting in the outbox some time before moving to submission. Would Outlook logging give e any information on what's happening. I don't see any issues on the server side. Submission logs do not show any failures. What would be the best way to capture helpful information. Any assistance would be appreciated.

↧

Replication issue for DHCP cluster in "Hot Stanby" mode

May 18, 2019, 1:53 pm

≫ Next: Help with setting up authenticated external mail relay through our on-premises exchange 2013 servers

≪ Previous: Emails are slow leaving Outlook outbox

On windows 2012 R2 servers we have setup the DHCP cluster in the "Hot Stanby" mode to provide redundancy.
But we have noticed that the DHCP reservations do not sync across to the other server.
When I perform a sync for a scope only following tasks are performed and syncing reservations is one of the tasks.

Does it sync only 1 way i.e. from Active member to Passive?
If someone creates a reservation on Passive member will it replicate to Active member?

On one of the posts on internet I read that reservations not replicating is a known problem with DHCP cluster setup and to schedule a task with following command to ensure everything is replicated:-
Invoke-DhcpServerv4FailoverReplication -ComputerName "dhcpserver.contoso.com" -Name "SFO-SIN-Failover" -force

So I ran this command from Powershell on the Active server before scheduling it.
It resulted in the scope going offline and deleted a few reservations. I had to bring it online again manually after the command finished.

Why would the scope go offline?
And why did it delete a few reservation entries. Should I be running that command from Passive member of the cluster?

↧

Help with setting up authenticated external mail relay through our on-premises exchange 2013 servers

April 11, 2019, 1:21 pm

≫ Next: Spam emails from my own domain and different domains

≪ Previous: Replication issue for DHCP cluster in "Hot Stanby" mode

I need to configure external smtp relay with authentication on exchange 2013 server.
I went through the article below :

https://practical365.com/exchange-server/exchange-2016-smtp-relay-connector/

This article explains how to setup external SMTP Relay with Exchange Server 2016 Using Authentication, but I guess it is still relevant to exchange 2013. Is that correct?

So I tested the external relay by using the "Send-MailMessage" powershell command and using port 587 (without ssl switch as we don't have cert on that connector).
It did not succeed without credential as expected and succeeded with credential as expected.

On-premises exchange servers send to office 365 and then it should go out to internet.
How can I get confirmation that it was using “SERVERNAMEClient Frontend SERVERNAME” connector for receive.
If I enable "RequireTLS" on this connector then are there any issues I should be aware of?

And which send connector it is using to send out to Office 365.
As per the article below it should be going through the send connector that is set to use "<OurDomain>-com.mail.protection.outlook.com":-
https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-flow/set-up-connectors-to-route-mail

I need to ensure that TLS 1.2 is used between on-premises exchange and office 365. Thus I need to ensure which connector it is going through.

↧

Spam emails from my own domain and different domains

May 20, 2019, 2:25 pm

≫ Next: dns lookup fail

≪ Previous: Help with setting up authenticated external mail relay through our on-premises exchange 2013 servers

My exchange organization receives multiple spam emails some of them from our own domain.

we have Edge server only for inbound and outbound mail flow. we need to know how to investigate this problem and how to stop those emails.

↧

dns lookup fail

May 22, 2019, 3:16 am

≫ Next: Relayed email from printer/scanner to different domain in the same office 365 tenant.

≪ Previous: Spam emails from my own domain and different domains

hi all,

our exchange server has dns server on it. the dns server malfunctions even after restart. nslookup returns timeout and default server not found.

we tried to use another dns server for exchange but it gives us 421 4.4.2 error.

does anyone know what we can do?

regards

↧

Relayed email from printer/scanner to different domain in the same office 365 tenant.

April 14, 2019, 8:24 am

≫ Next: عروض اصلاح ثلاجات جولدي 01225025360 اتصل بنا الان 01014723434 البحيرة

≪ Previous: dns lookup fail

I need to relay email from printer/scanner using our internal exchange 2013 server "EX1" (int.abc.com domain). Even I need to allow email to other domains like xyz.com.
Our user mailboxes are already in Office 365.
Internal exchange server has a send connector setup to send email through "def.mail.protection.outlook.com" smart-host for "*" fqdn.
Other domain like xyz.com are federated to same Office 365 tenant as abc.com.
Currently I can't scan from scanner (setup to send mail through EX1) to xyz.com . It says EX1 is not in the allowed senders list for xyz.com domain.
I think one way to solve it is to add EX1 to the spf record for xyz,com.
We need to do this for lot of domains.

I want to find out if there is a better way. Can office 365 route internally between abc.com and xyz.com without doing spf check as xyz.com domain is in same Office 365 tenant as abc.com?

↧

عروض اصلاح ثلاجات جولدي 01225025360 اتصل بنا الان 01014723434 البحيرة

May 28, 2019, 1:53 am

≫ Next: Relayed email from printer/scanner to different domain in the same office 365 tenant.

≪ Previous: Relayed email from printer/scanner to different domain in the same office 365 tenant.

GOLDI

↧

Relayed email from printer/scanner to different domain in the same office 365 tenant.

April 14, 2019, 8:24 am

≫ Next: 'Invalid recipient address', email address formatting strangely in the headers

≪ Previous: عروض اصلاح ثلاجات جولدي 01225025360 اتصل بنا الان 01014723434 البحيرة

↧

'Invalid recipient address', email address formatting strangely in the headers

May 29, 2019, 8:44 am

≫ Next: Exchange 2013 to 2007 Mail Flow Not working

≪ Previous: Relayed email from printer/scanner to different domain in the same office 365 tenant.

I have a single user in my organization of ~650 that is having this strange issue. Occasionally, when she sends emails to a specific user, she'll get a NDR stating

Remote Server returned '550 5.1.3 STOREDRV.Submit; invalid recipient address'

The email headers show strange formatting on the recipient. I'll change the first/last names and domain name for privacy, but leave formatting the same:

From: Jane Doe <Jane.Doe@company.ca>

To: John Doe <JohnDoe<John.Doe@company.ca>>

You notice the recipient is "duplicated" in the angle brackets which causes an invalid address.

This is the only user reporting this issue. She's received 9 NDRs out of 32 emails sent to this recipient. One was a reply, the others were new emails.

We've tried removing the autocomplete entry in Outlook, rebuilding her mail profile, and giving her a new computer to work off of, the issue persists. She does have a fairly large OST file (~20GB), not sure if that is a factor.

We've had her try out webmail, without issue (so far, the ~25% failure rate might not have revealed itself yet in webmail).

We are running off an Exchange 2010/Office 365 hybrid environment. The mailboxes are all hosted in O365. The Outlook client we are using is Office 365 ProPlus. Please let me know if there is any more information I can provide.

↧

Exchange 2013 to 2007 Mail Flow Not working

May 30, 2019, 10:31 am

≫ Next: Google Rejecting our Emails

≪ Previous: 'Invalid recipient address', email address formatting strangely in the headers

Dear All,

We are upgrading Exchange 2007 to Exchange 2013 Latest CU

All Pre-req are done, Co -Existence has been Established

All other functinality working fine , apart from mail flow from Exchange 2013 to Exchange 2007

Exchange 2007 to Exchange 2013 Works fine

I Tested Telnet from Exchange 2013 and Tried to send mail to Exchange 2007 and that also works , but when I am sending mail using outlook or OWA , mail gets stuck in Exchange 2013 queue and doesnt proceed

Any idea what could be going wrong

↧

Google Rejecting our Emails

June 2, 2019, 8:34 am

≫ Next: Exchange Toolbox Error when launching

≪ Previous: Exchange 2013 to 2007 Mail Flow Not working

Hi Guys, I hope you can help me.

I'm getting this error below every time I send an email to a google hosted email. How did you resolved this kind of Issue? we are using Exchange 2013. Recently we moved our VM to a new Data Center, replaced our public IP and then this happened.

-this issue is specifically only to google hosted emails because we can send email to other email domains.

-sending/receiving an email to gmaildotcom has no problem

mx.googledotcom rejected your message to the following email addresses:
'user@domaindotcom' (user@userdotcom)
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.

mx.google.com gave this error:
[x.x.x.x 12] Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. ***"Microsoft not allowing me to send with links -newbie user here "****. j5si14415577plk.229 - gsmtp
I have reported to Google to unblock on June 31, 2019.

thanks,

GT

↧

Exchange Toolbox Error when launching

June 2, 2019, 8:37 am

≫ Next: Exchange Server Installation on Active Directory

≪ Previous: Google Rejecting our Emails

Hi Guys,

Is it possible reinstalling Exchange Toolbox and Exchange Management shell on existing and running Exchange 2013 Server?

I am getting an error when launching Exchange management shell (Unable to connect winrm, even though winrm is configured), and Exchange Toolbox (loading/freezing, and then error).

note: sorry Can't provide screenshots right now.

thanks,

↧