Is there any way that we can determine if the recipient has seen the report that was delivered through a subscription by email option?
No, the "Read Receipts" is configured on the E-mail server. It is not a supported configuration of the email notification on Reporting Services. Microsoft Reference
Here is the reference for E-Mail Delivery in Reporting Services. It describes report server e-mail delivery operation and configuration.
This is not directly supported, but you could build a workaround for it. For example, you could have a link provided the email that you request them to click on. The link would contain an ID and go to a site/report that logs the ID.
You could even go a step further and just send a link. They would have to click it to see the report and that could be logged.
Related
I have SSRS 2019 in native-mode with SQL Server 2019 standard behind it. To be very clear, email functionality works and outgoing emails from SSRS is being sent and received. The issue is when the option to attached the report (Include Report) is selected in the subscription options, the following error is received at time of execution:
Failure sending mail: The permissions granted to user '' are insufficient for performing this operation.Mail will not be resent.
I've tried different render format (MHTML, PDF, CSV, XML) to no avail. "Include Link" option works without issue. So unless there is a secret permission somewhere for attachments, I'm a bit confused.
SQL Server Database Mail works and shares the same email configuration values as SSRS.
If anyone has faced this issue, I would love to know what caused it and how you solved it in case my situation is the same.
Nevermind everyone. After I posted my question, I realized the service account was still at the default "Virtual Service Account". After I got an actual domain service account and updated it, plus restarted the service, emails with attachments started flowing through without issue.
Note: I had to delete my 1 existing test subscriptions since it no longer was being recognized with the new service account. After creating a new subscription, there were no more issues with attachment-emails. This in itself could be another problem altogether. More testing is required.
I'm trying to find out if it's possible from an Outlook Add-In for a Compose Form to add a Read Receipt to a message before it's sent.
My company has a form library built in an older version of outlook and an older version of exchange. The form has quite a few fields that are easy to replicate with an outlook add-in. The main requirement that I haven't been able to find any documentation on is that each time the form is used to send a message, it automatically checks the Options/Tracking/Send Read Receipt checkbox before the form creates the email body and sends the message.
I've read through the documentation (https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/), but I haven't been able to find anything that mentions Tracking or Read Receipts. Is that something I'd have to call in Exchange Web Services or access through the REST API? All of the messages sent with this add-in will be going to recipients inside my company.
Currently the Read Receipt feature is not a part of the Outlook Add-Ins framework. We track Outlook Add-In feature requests on our user-voice page. Please add your request there. Feature requests on user-voice are considered when we go through our planning process. Alternatively, you may be able to use the Outlook REST API to achieve this.
I'm using Azure API Management and I have a user who tried to sign up but never got the "validation" email. Let's just assume the email is not recoverable. Unfortunately, I have no way to reset that user's email address. The API Management framework knows that the email already exists but I have no visibility to that user's profile until they validate the account. At that point I can manage their account but, until then, they are in-limbo.
If the user tries to re-sign up or even if I send an invite, we get an error that says. "Email already exist"
Any pointers?
The confirmation request will expire in 2 days, so if the user tries again after 2 days, the "email already exist" error should go away.
Meanwhile, we are currently working on a feature to allow Admins to delete unconfirmed users from the Management Console.
In addition to allowing admins to remove unconfirmed users we added the ability for users to re-send confirmation email.
Perhaps a special command or message header in order to be able to tell Google to not store a message sent using their SMTP server in the respective user's Sent mailbox.
There is no way to prevent the message from being saved to Sent. However, you can connect via IMAP after the send and delete the message from the Sent folder. Assuming you are using OAuth authentication, the same scope you use for SMTP allows you to connect via IMAP.
I was also stucked in this kind of scenario some time back, for me I could not find any standard API to solve this. But as a workaround I have created a rule which deletes all the mails which appears in Sent Folder. But beware of IMAP protocol, it allows users to store their there sent messages in custom folders also.
I am attempting to set up a subscription on my report server that will send out an email to a outlook email group. However when I specify the group in the To: field on the report server I get the following email in response when the subscription is actually ran.
Your message did not reach some or all of the intended recipients.
Subject: Report was executed at 4/20/2011 9:39:02 AM
Sent: 4/20/2011 9:39 AM
The following recipient(s) cannot be reached
Outlook Email Group on 4/20/2011 9:39 AM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
However, when I change the TO: to include members of that group they receive the emails fine. My question is, is it possible to specify out email group names in the TO: field of a report server subscription or do you have to put all of the individual email addresses of the members of that group in there for it to work? One of the responses that I got so far was: Consider that the Report Processor "logs on" with specific credentials. This is the Service Account. Try to open a Windows Session using these credentials and send the mail. I expect it will fail. Make sure this account has group-send rights. Is this correct and if so should I be consulting with our exchange server admin to get group send rights added and to which user account?
The most likely reason is that your group may be configured to only accept mail from authenticated users, but there are also other possibilities, for example it is also possible that the group has been configured to only accept mail from a certain set of users.
It is definitely possible to put Exchange Group names into the SSRS recipient list.
I'm agree with your comment: this looks like an Exchange problem. Check with the mail admins to see what restrictions on mail to groups exist.
SSRS uses SMTP to send email. You can follow the instructions on Technet for How to Use Telnet to Test SMTP... Substitute in the server name and from address that SSRS is set to use. You will likely see the test message refused with an error that will hopefully give you more details on the error. At the very least, it will give you something to take to the Exchange team. ( I don't believe that sending email from SSRS supports authentication, but I'm not sure on that.)