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.
Related
I'm currently using Twilio Frontline on top of my conversation service and my identity for each user is a uuid so when a message comes in on Frontline, it displays that user's uuid. This can get confusing if we have multiple participants in chat. Assigning a name as the identity would not work since it may not be unique. Assigning their email as the identity would not work as well if they update the email.
In Conversations, the name of a participant in a conversation comes from the underlying User resource and the FriendlyName property.
You can update Conversations Users using their identity as the key in the URL and set the FriendlyName, that will then show in Frontline instead of the identity.
We also recommend using the onParticipantAdded Conversations webhook to do things like setting a customer_id, avatar and display_name for customers in a conversation.
You can read more in the How to enable incoming messages? section of our Quickstart Guide.
I have the Mautic and Salesforce integration working fairly well, and now I would like to sync the email bounce status back to Salesforce. This allows Salesforce users to update email addresses when they are talking to prospects and making notes in Salesforce. I don't see how to sync the bounce back since there is no "email bounced" field in a Mautic contact.
Using Mautic, I can detect bounced emails as shown below once their email has bounced:
However, when I go the Salesforce plugin, there's no field to select for this bounce, something like "Email Bounced":
Maybe I can create a custom field called "Email Bounced", but then how would I populate it? Ideas? Thank you!
The solution below assumes the cron jobs for syncing and segments are set up (that's a small project in itself). It also assumes email inbox monitoring has been setup.
Create a field in SalesForce to store the Invalid Email flag.
See SalesForce help. Create a Boolean field called "Email Invalid".
Create a field in Mautic to store the Invalid Email flag.
Create a segment with contacts having a bounced email.
From https://www.irelandwebsitedesign.com/images/learning-centre/mautic/mautic_docs_en.pdf:
a. Go to Segments / New.
b. Type in the segment name. For example Bounced emails.
c. Select the Filters tab.
d. Create new Bounced Email equals Yes filter.
e. Wait for the app/console mautic:segments:update command to be automatically triggered by a cron job or execute it manually.
Create a campaign to update the bounce date.
This campaign will update the "Email Invalid" field when a contact is added to this segment.
Set the fields to sync in the plug-in.
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?
Can anything be done to limit an Eventbrite event to the invited individuals only?
I realize that there are settings which cause an event to be "by invitation only". Then you send an invitation to the particular email addresses you want. Only they can use the registration page. (Others will get a message "this event is by invitation only"). That's great! So far so good.
But the problem is, the person who received the invitation can register a completely different (uninvited) individual to be the attendee. All the attendee fields are writeable: Name, email address, mailing address etc.
It let's you change the email address and even asks if you wish to send an invitation email to the new email address. The new individual gets an email saying: "An order for xxxx was purchased for you by: yyyy" which is not desirable in our case.
The invited individual has a "my Account" area with his/her information (name, email, etc) filled in. But the attendee information is different info to be filled in (as opposed to being drawn from the info in the account area)
Configuring your Order Form to "collect only basic information" should ensure that each registration email and attendee email are identical:
http://help.eventbrite.com/customer/en_us/portal/articles/426121-collect-information-from-attendees
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.