SSRS Mailer Issue - service

I am facing one issue, when I send a mail through Subscription in SSRS, it will send the mail twice or thrice. So for a time being I have stop the Reporting services. And when I again open that service mail sent automatically.
Please suggest...

Related

SQL Server 2014 - DB mail sending Issue

DB mail was working fine using SQL Server 2014; however since we moved our email to Office365 online Exchange, we are having issue. Whenever there are rapidly generated emails by our application; then sending emails is stopped with following message:
The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 3 (2018-04-08T08:25:06).
Exception Message: Cannot send mails to mail server. (Failure sending mail.)
Service again starts sending emails automatically after a lag of few hours.
I have already checked email account separately and it is working fine.
This is a limit set by Office 365. Check this image captured from microsoft technet post
Based on your subscription, limits are there for sending total emails per day as well as bulk email at a time. Same has been confirmed in this Microsoft blog question
That's why your task stops sending email for sometime to reset its Recipient limit.

Gmail is not receiving emails from SendGrid

I have a Django app set up to send emails from my contact form via SendGrid.
The contact form should send emails to contact#clientdomain.com, which is an account using G Suite, so the client opens the email on Gmail.
However, the emails from the contact form are getting stuck on SendGrid with status deferred or block.
I tried changing the destination email from contact#clientdomain.com to personal_email#gmail.com and it worked just fine.
I don't know what else to do.
Here is my Activity Feed from SendGrid dashboard:
I read when the status is deferred, SendGrid keep trying to send the email again for the next 72h, but I have emails sent 3 days ago that never arrived on the inbox.
Anyone knows what could I do to fix that?
I solved it! Thanks to #Selcuk comment.
I had my domain pointing to a server with cPanel all set up.
Then I developed a new app, deployed it on Heroku and installed the PointDNS to get my domain poiting to the Heroku app.
When I did this, I lost my MX records set up on my server with cPanel.
All I had to do was to add the MX records for G Suite on PointDNS:

OTRS 3.2.14 - How to know how many mails have been sent on each queue?

Is there any possibility to know how many emails have been sent through OTRS system ? When I try to search it on Google, response are about "How to schedule statistics by mail?" and this is not what I'm looking for.
In OTRS you can configure only one SMTP account to send mail (when you create a ticket or when you response/forward one ticket, you send a mail).
My mail provider is limiting send mail to 200 per hour, but I don't know which queue (which customer) is sending so much mail.
Is there any possibility to have a report under OTRS that shows me how many mails have been sent from each queue per hour ?
My Environment is : OTRS 3.2.14 Windows Server 2012 MSSQL 2012
All outgoing mail is recorded in the OTRS log. On Windows, this would be in <OTRS>/var/log/otrs.log. Just open this file and count the number of sent mails. It could well be that agent notifications are causing you hitting your limits.
Everything is saved in database.
You can use SQL query to determine that.
To get needed information you should join ticket, article and queue tables.

CRM plugin not firing for emails sent from console application

I have a plugin written that is registered for the DeliverIncoming message on the email entity in CRM. The plugin fires normally when emails arrive into a queue.
I also have a console application that connects to the CRM service, checks the followupby attribute of cases and depending on the date sends out a reminder/overdue notification.
The problem is that these emails aren't causing the plugin to fire. The email activities are created in CRM and the emails are sent and delivered without any issue but the plugin doesn't fire. I also tried registering the plugin against the Create message of the email entity and that doesn't fire either.
The emails are sent using the SendEmailFromTemplateRequest as the request object being passed into the CrmService.Execute() method
The plugin fires for all other instances of emails being delivered. The emails sent from the console application are the only ones experiencing this issue. Does anybody know why this would occur?
Thanks,
Neil
DeliverIncoming only fires for eMails routed into the CRM queues by the eMail Router. It will not fire on eMails you send from the CRM system.
Finding out what exact message a plugin needs to be registered against to fire on a certain action is sometimes a case of trial and error. Write a simple plugin that just logs the time and context.MessageName somewhere and register it against any message valid for the email entity. Then send an eMail through your application and have a look at what the plugin logged.
Turns out the plugin was firing, but when run from the console application it was throwing an exception when trying to log to a file it didn't have permission to. I had a break point on the second line, the first line was the logging line.

CRM email not appearing in queues

I have a CRM applicaton with queues setup to receive emails. It is all working as expected except for one exception.
The client is scanning letters that they receive and using a SMTP request via their exchange server to send the scanned letter to the queue in an email message. The message is being delivered to the email address but it is not going into the queue in CRM.
Relaying has been enabled on the exchange server for the CRM system. If the message is sent from a normal email address it enters the queue as expected. There is nothing in the Trace logs or the event viewer on the CRM server to indicate why the message is not going into the queue.
Can anybody provide me with some suggestions as to why this could be happening?
Thanks,
Neil
Turns out the mails weren't entering the mailbox at all