We would like to send Event Reservation markup along with our order confirmation email. The schema was implemented using JSON+LD and following the requirements set by google's reference document for event reservation.
We filled the form required by Google and sent one of our confirmation emails to the specified email address with the markup data. As a reply we were informed that "the schema was empty". When trying to request more information we received a no-reply message from the address that contacted us.
I'm adding a link to the html of the email sent along with the form confirmation emails with the markup data here. Our sent email contents are base64 encoded, could that be the cause of the email being rejected? If not, what other actions can we take to get the event reservation markup displayed in our emails?
Related
We are on JIRA On Demand. We have one Email handler configured to create/update tickets if we receive emails on a particular email id. In most of the cases, the emails will be from outside email ids and hence we have a JIRA user id by which the emails from unknown ids will be created as issues. So reporter of the issue will be our JIRA user though the emails are from some unknown email ids. Is there any way to get the actual "FROM Email ids" and put it in a custom field or at least to get the correct email id.
According to the Atlassian page on creating isses from incoming emails the "From" is appended at the end of the message body if you are using Default Reporter:
Default Reporter
Specify the username of a default reporter, which will be used if the email address in the From: field of any received messages does not match the address associated with that of an existing JIRA user — for example, a JIRA username such as emailed-reporter
(info) Note:
When an issue is created and this option is specified, the email message's From: field address is appended in a brief message at the end of the issue's Description field, so that the sender can be identified.
Unfortunately there doesn't look like a convenient way to transfer this to an issue field. At least the information will be present though in the issue description.
On our webpage we have a contact form to let people contact us without sharing our email addresses.
We require a name, an email address and a message and allow people to send a copy to themselves.
On our server we have Postfix setup to send outgoing email.
Right now we add information as:
from = their email
to = our email and theirs if they want a copy. (could be cc instead)
It works okay, but just some weeks ago Gmail started to put all our emails in junk, even with explicit rules and stuff.
We figured out our Message-ID have the wrong format and added
def set_message_id(sent_at: Time.zone.now)
headers["Message-ID"] = "<#{Digest::SHA2.hexdigest(sent_at.to_i.to_s)}#domain.com>"
end
Based on an article from Mailgun and StackOverflow.
However we also get an SFP-softfail because we send the email from the users email, and the domain of their email does not have the same origin as our domain.
How do you solve this? We really like the way that you can instantly respond to a contact email and get the right name and email address automatically.
Is it worth investing in a service such as Mailgun just for this contact form?
I'm working on a free iOS app; at the end of the registration (when the user has registered a good phone number and good email address) I want the user to enter a code which he has received on his phone or email.
But the problem is how to send automatically a SMS or an e-mail programmatically that contains the code?
I don't want the user to be redirected to a specific view controller to compose a message by himself (like with MFMessageComposeViewController or MFEmailComposeViewController)
just and only just the same appearance of SMS or email sent to users but with a different activation key (for the keys, I think about auto generated keys stored in a database).
And I think about the same way for forgotten identifiers, the user enter his email address or his phone number in a text field, and a message is automatically sent with the password and the username of the user, if the email address or the phone number entered is already existing in the database, if it is not, it shows an alert view with an error.
Does anyone have an idea for how to do this?
You can use the following services Parse.com + mailgun. Search on Parse.com for a tutorial using mailgun and it should accomplish what you are trying to do. On a side not, be careful when creating an app which does not allow the user to use it until they enter some access code, it is against the Apple rules and could lead to rejection.
I assume you have a server that generates this activation code that is sent to the user.
When the user enters the text field with the code he got it should be sent back to the server with an http request (use NSURLConnection ). The server should response to the http request with approval or error whether the code is right, or send the username and password and any other data the user needs to continue.
I am building an email app in ruby on rails and I had a basic version which just used to send emails using AWS SES but recently I received a mail from AWS team saying that most of the email which I have sent had bounced back and they will discontinue my account if I send emails to the bounced email ids.
Is there any way to verify before sending email to any address that whether that email exists or not and valid or not.
Any gem or work around will help me a lot
The general way to do this is purely from a system design point of view. If you are going to collect an email address from one of your users and send them email periodically, or as events happen etc, then you should first ask them to "verify their email address". This typically involves generating a unique token, putting that into your database, linked with the user, then sending an email containing a URL with that unique token in it. The user clicks the link, which goes to a controller in your Rails application that matches the token against the user. If they can't follow that link, they can't read your emails, so don't send further email to that address.
If you obtained the email addresses through "other means", you're down to setting a Return-Path address on the outgoing email (bounces will be sent here), then checking that mailbox for bounces. I'm also often suspicious of how people happen upon a list of email addresses that didn't come from users consenting to an agreement with your website.
You could use the Mail gem to do this, but you need to know how to set up an SMTP server that pipes the email into your Rails application, which is not straightforward without prior experience. You can also use a variable Return-Path address (VERP), such as <some unique hash>+bounces#your-domain.com, where <some unique hash> references the email address in your system. This takes away the pain of trying to parse and interpret the bounce email, since the address it is sent to tells you who the bounced recipient is.
I have an application that allows users to send an invitation to a friend. Emails are being sent out using SendGrid. I am wondering if it's possible to forward the mailer-daemon emails back to the user in an event they type in an email address that doesn't exist.
So for example a user enters in the email 'thisisnotreal#fakedomain1234.com' to send the invitation. I want to be able to notify the user that the email they have entered doesn't exist. Usually when you just send an email from an email client the server lets you know right away that the email is not able to be delivered. I am wondering if it's possible to do this as well through SendGrid.
Take a look at the event notification section of the SendGrid API. You can add a page to your application that accepts POST requests from SendGrid, and then you'll get event notifications in real-time.
When a bounce event is posted to that listener from SendGrid, you could then lookup the user that needs to be notified via the recipient email. If you don't have this relationship available in your local store, you could pass a unique argument to SendGrid at send time that contains information you can use for the lookup - unique arg information is included with event notifications. Then it's just a matter of taking the appropriate action required to notify your user - either with an email or via a notice on your website or a text message or whatever is best for your application.
This maintains asynchronous communication. You'll be alerted when something goes wrong without having to add blocking code, and you can send your users a nice branded message (using SendGrid, of course) rather than just forwarding a mailer-daemon response .