Using Mautic 3.3.3 and trying to figure out why Mautic does not the email reply under the contact history. Searching the internet and posting to Mautic forums did not help.
Added debug print and it shows that Mautic is receiving the email from SES correctly, any idea why the reply email is not placed in the contact history log? is there other Mautic configurations needed to make it match received email to a contact?
php /path/to/mautic/bin/console mautic:email:fetch
1 email processed for {imap.mail…apps.com:993/imap/ssl}INBOX with a criteria of UNSEEN
Related
I hope you are well.
I need to generate unique email for users and allow them to send email to create a new post in their profile.
Example flow
User signs up
User gets username-withsomeuniqueaddition#myproduct.com
User send email to the address above
The product creates a record with the info from email body
Similar to how users can save links to their Instapaper account using email.
I spent hours googling but it all return how to send emails with RoR.
Is there any direction, tutorial or gem you can guide me?
Thank you, stay safe.
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?
I am interested in finding out how I can send my business customers appointment confirmation emails to their Gmail accounts and have their Google calander automatically populate the info and give them a reminder without any action required on their part. I know it's possible as I received such emails from companies that have done this. Can anyone please help? I'm not the most computer savvy person so I will need an explanation. thank you.
#carl grassl You will want to use EventReservation for appointment confirmations.
When you send your customer an email confirmation with EventReservation, this will automatically populate the info of the appointment in their Calendar, additionally, it will also trigger a Google Now card of the appointment.
Check out this tool below, logging in with your personal Gmail account:
http://gmail-actions.appspot.com
Once you've logged in, load the sample "Event card." You can send yourself an EventReservation email.
When you feel that you got everything locked in with your production email client, you'll have to register with Google to use schemas. Make sure your email is authenticated (DKIM/SPF). You can get all the details here:
https://developers.google.com/gmail/markup/registering-with-google
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 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.