we have an application that is using the Outlook REST API v2 to allow the users to send emails from the app.
Today one of our clients send us a bug report, that after they created a new Office365 account for their company they can't send emails through our app. The current case was for sending email to hotmail.com account. The email bounces back with error code
550 5.7.708 Service unavailable. Access denied, traffic not accepted
from this IP.
The user also reports that they are able to send the same email from the Outlook web client.
I have found this issue on the network: https://social.technet.microsoft.com/Forums/ie/en-US/608d046b-755a-4264-8cdd-fc34c72ccf8f/office-365-tenant-blacklisted-on-all-emails-sent-by-ms-outlook-2016?forum=onlineservicesexchange and am now wondering if this is just a bug on Outlook side or we have missed something on our end?
You have to go here: https://sender.office.com/ and put the incriminate ip to delete it from the list.
Related
I got 403 Forbidden when I try to send Mail using graph API
If I try to login with #gmail or #outlook Id then It's working fine
But recently I've try to send mail with using #hotmail.com domain Id ,In this case I'm able to call receive mail graph API , but got 403 error in case of send mail graph api.
What's the exact Issue ?
I got this response when try to send mail graph API
There Is issue when I logged with #hotmail domain Id but I'm not able to send Mail , receive Mail functionality works fine
I tried to reproduce the same in my environment.
Below error occurs if office365 license is not available for your subscription
After using licensed subscription.
This error occurs when the delegated permissions are given instead of Application permissions to access the mail.
https://graph.microsoft.com/v1.0/Users/xxx/sendMail
and Please make sure to login with account that you are a member of .
And have the privileges to send mail.
The guest user may not have access to all the properties and some organizations restrict Hotmail/live accounts .The guest must accept the invite .
Check the user assignment and change the settings accordingly to allow users to send mail.
And for them, assign proper role to have access privileges.
I am developing PHP application that, after sign-up, sends an activation mail to the registered email address using Amazon SES (Simple Email Service).
But SES is only sending emails to verified users.
How can I send the activation link to any non-verified email address, too?
While running in sandbox mode you can only send to verified users - once your account has been activated, you can send to anyone.
Getting out of the sandbox:
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html
By default you can only send to email addresses that have been verified in your SES account. As others have said, this is called "sandbox mode". This is to prevent spam.
To enable "production mode", where you can send emails to non-verified email addresses, you need to request this manually through a support ticket, which will also be examined manually by an AWS employee. This is all explained clearly in the same link that the top answer gave back in 2016 but I've also preserved the 7-step instructions (just in case the link changes or can't be opened for some reason):
In the account details modal, fill out the following account details.
For Enable production access, choose Yes or No. You can only move out of the sandbox by choosing Yes.
For Mail Type, choose the type of email that you plan to send. If more than one value applies, choose the option that applies to the
majority of the email that you plan to send.
For Website URL, enter the URL of your website. Providing this information helps us better understand the type of content that you
plan to send.
For Use case description, explain how you plan to use Amazon SES to send email. To help us process your request, you should answer the
following questions:
How do you plan to build or acquire your mailing list?
How do you plan to handle bounces and complaints?
How can recipients opt out of receiving email from you?
How did you choose the sending rate or sending quota that you specified in this request?
For Additional contact addresses, tell us where you want to receive communications about your account. This can be a
comma-separated list of up to 4 email addresses.
For Preferred contact language, choose whether you want to receive communications for this case in English or Japanese.
When you finish, choose Submit for review.
If you are successful, you will get an email from no-reply-aws#amazon.com saying:
Hello,
Thank you for submitting your request to increase your sending limits.
Your new sending quota is 50,000 messages per day. Your maximum send
rate is now 14 messages per second. We have also moved your account
out of the Amazon SES sandbox.
This takes effect immediately in the XXXX region. You can
view the current sending rate and sending quota for your account on
the Sending Statistics page of the Amazon SES console, or by using the
GetSendQuota API.
If unsuccessful, you will get an email saying the following:
Thank you for providing us with additional information about your
Amazon SES account in the Europe (London) region. We reviewed this
information, but we are still unable to grant your request.
We made this decision because we believe that your use case would
impact the deliverability of our service.
We cannot assist you further with this issue, and we will not respond
to additional messages on this subject.
The SES forum is full of frustrated people who got the second message (indicated an unsuccessful application to send emails to non-verified email addresses), but I can assure that that this morning I got the first message (indicating a successful application to exit the sandbox and enter production mode where I can send to non-verified email addresses).
The forums indicate that this can be very hit-or-miss, depending on which staff members reads your application (people have pointed out that they have had some accounts approved with barely any description, and other accounts not approved despite giving what they felt were sufficient details). Therefore I'd advise you to be thorough during this application.
These are the restrictions in SES sandbox :
You can only send mail to the Amazon SES mailbox simulator and to verified email addresses and domains.
You can only send mail from verified email addresses and domains.
You can send a maximum of 200 messages per 24-hour period.
Amazon SES can accept a maximum of one message from your account per second.
You have to move out of sandbox to send email to non-verified email address using AWS SES.
After you move out from sandbox mode, you need to handle complains and bounds about SES.
AWS asking us ,you are sending a mail to an unregistered mail adress.what if mail adress doesn't exist? .AWS needs notificate you about the sending status of mail which you sent.
There are three sending status : complaints,bounds(mandatory),deliver(optional)
So you can get a notification about the mail if it sent or not with the reason.
To handle complaints and bounds,you need to create SNS topics and need to relate them with the SES.now AWS can notificate you about the mail it is sent or failed or something else..
Here is the detailed description how to relate SNS and SES :
https://docs.aws.amazon.com/en_us/ses/latest/DeveloperGuide/configure-sns-notifications.html
NEW UPDATE:
You can now go to the SES account page and directly drop a request for production access.
https://ap-south-1.console.aws.amazon.com/ses/home#/account
I'm having an issue receiving the verification email from DocuSign that is needed to create an account under my master account to connect for use with API. The emails don't appear to be hitting my firewall, nor are they showing up in my email. Does anyone know if these emails are coming from docusign.com, docusign.net, or some other domain?
In Demo emails will come from dse_demo#docusign.net and in PROD it should come from dse#docusign.net. Also please check your Spam/Junk folder if it landing on these folder as per your email server policy.
I have signed up with Google Apps, I am using a third party SMTP Server to send the emails from the web app, Emails are reaching inbox for all the email clients (yahoo, gmail, hotmail...)
But Emails sent to my domain (mydomain.com) are reaching SPAM, This is happening only for my domain Which is google apps account domain. The solution to the problem is the sender must be in the contacts of the receiver. So its a overhead involved in adding the sender in the contacts before receiving the mail. This is not automated.
NOTE: Mails sent from <xyz#mydomain.com> to <abc#mydomain.com> are reaching SPAM. It means, Its happening only when the sender and receiver belongs to same domain.
ASSUMPTION: ALL the emails will be sent from mydomain.com .
So, I want to write a script using google apps script So that when a mail arrives from mydomain.com (having FROM address belongs to mydomain.com), The script must execute and add the senders emails address in the contacts. So it will avoid the spam rate.
I am very new to google apps script, Please help me doing this, Or if any better solution is there please feel free to post.
Vinay,
It sounds like you may have an incorrectly configured SPF record. Please see this article:
https://support.google.com/a/bin/answer.py?hl=en&answer=33786&topic=2759192&ctx=topic
Email that has a mydomain.com sender address, needs to come from a mail server listed in your SPF record or risk being sent to spam.
By chance, has Contact Sharing been enabled for your apps domain? I'm just offering this as an hunch that might help rather than a specific solution to your problem.
If this doesn't help, its a straightforward but non-trivial problem to add all your domain accounts to each others contacts list (and keeping it synced over time), but you'll be leaning heavily on a version of the Contacts API rather than plain Apps Script because the Contacts service only operates on the contacts of the user executing your script.
I have created a document library in sharepoint 2007 and i have enabled incoming email settings to the doc library. When I am trying to send an email from workflow I am getting the error...
System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable. The server response was: 5.7.1 Unable to relay for EmailDocLibrary#xxx.com
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at DP.Sharepoint.Workflow.Common.SendMailWi
Do i need to setup anything before sending an email. Please help me.
Thanks
Your outgoing mail server isn't setup for relaying from just any address. Checkwith your email server adminto make sure that you are able to send outgoing messages with the email address you have.