I'd like to send an email message that contains multiple translations. The correct translation should be displayed according to the recipient's language preferences. Possible?
There is nothing in the email message format that will let you do that. What you can do instead, is to put translated contents as attachments, or post some (translated) links to your website, that will refer recipients to translated contents.
Anyway, I think it is best to store language preferences in the user profile (provided you have one) and use this information for customizing emails. That works well, unless you are sending messages to group of people...
To the best of my knowledge, email accounts are protected from getting any information about the recipients unless they provide it. Even email clients often prevent emails from displaying pictures, since it reveals the recipient's IP address. So I also think, it's unlikely to be possible.
I agree with the idea of Pawel Dyda.
Related
I manage an email newsletter for a customer. It uses a custom list management utility, but the emails are being delivered through SendGrid.
In order to integrate correctly with our list management unsubscribe. I'm manually creating the "List-Unsubscribe" header, with a mailto address, which goes to an email parser, and unsubscribes the user from the correct publication etc.
The email parsing etc. works fine. However for some reason gmail is not displaying the "Unsubscribe" link in the header, as it does with other newsletters I receive.
Another newsletter I manage for a different customer, uses SendGrid's built-in unsubscribe management, and for these ones gmail does display the link.
What I want to know, is why is my custom "Unsubscribe-Link" ignored by gmail, but SendGrid's works?
SendGrid's "List-Unsubscribe" looks like this ...
List-Unsubscribe: <mailto:unsubscribe#email.mycustomdomain.com?subject=http://links.mycustomdomain.com/asm/unsubscribe/*q*user_id=[SHA hash...==]>
My custom "List-Unsubscribe" looks like this ...
List-Unsubscribe: <mailto:u-[custom-encoded-user-id+publication-id]#list-management.mycustomdomain.com>
My email parser reads the incoming "to" address, and interprets the encoded user-id and publication-id, to unsubscribe the person from the correct list.
Can anyone suggest why gmail might not like my link? It's extremely difficult to find detailed information about the requirements for this header.
One obvious difference, is that mine doesn't have a subject, but that's because it doesn't need it. It gets all it needs from the "to" address. Could this actually make a difference though? Does the "to" address need to remain static?
I thought perhaps it just needed time, for gmail to familiarise itself with this newsletter. However it has been running for months, and still no link.
The list is very clean, and all recipients have opted-in. We don't get any spam reports, and very few bounces.
I've gone to a great deal of trouble to ensure that everything works correctly from my end, and it's very frustrating that I cannot find out what I need to do to make this work.
I found a similar question at the gmail forums, and the official response to that question was to "contact a professional about constructing html emails".
Not very helpful for me, as in my case, I'm supposed to be that professional.
Any suggestions would be greatly appreciated.
Are there any reasons (Spam, etc.) to include the name in the To: headers instead of just omitting them and only using the address?
No, it just looks pretty, that's mostly it.
When you're sending mail to multiple people it can be useful when some of the recipients' email addresses don't easily map to their names.
It usually displays in your email client. If you leave it out, it simply displays <example#test.com> instead of Example Test <example#test.com>.
Im guessing it might be a factor for spam detection too (so adding the recipients name makes it more likely to show up in the inbox)
I publish myself as a personal teacher for students, and recently the number of the clients increased, and I think that a proper solution for me will be like that:
when a client sends me an email on Gmail (more correct, puts my gmail address on "send to" field), a template will show up and the client will choose from dropdowns details like: grade, subject, phone number etc.
and that will help me manage myself in a proper way.
I would like to know if that possibility even exists on gmail, and if it does, how do i operate it.
thanks for helping me.
The closest thing that I can think of is using Filters. Filters in Gmail will let you label incoming mail based on the sender, subject or more. These will then show the label in your inbox. You can then keep a Draft or spreadsheet of response templates. You can read up more on filters here.
I'm trying to get a mailto link that would open a new outlook email window with a modified from field (i.e. to use a secondary account as it were). Is that possible?
No. Certainly not in most of the popular mail clients.
I assume you are wanting to do this just to save time in your own mail client. I would certainly be annoyed with a website that tried to change my from or reply-to address, so I'd expect my mail client to ignore it.
MAILTO is designed to facilitate a sender contacting an address that has been listed on a website. So there are very few things that the sender would expect to have dictated by the website. Even the standard options can be pretty annoying if handled badly by the website owner.
Your options are pretty much limited to
subject
body
cc
bcc
Even if a client were to support From (and I am not aware of any that do), there is no obvious way for them to handle edge-case scenarios such as a from address that has not been configured in the mail client.
What do you need this for? Perhaps you can use a script to send mails and dynamically set the From header. For example, PHP has a mail() function which would allow you to set a custom From address (and modify other headers).
Am trying to determine the best way to persist information from an originating email, through to a reply back.
Essentially, it is to pass a GUID from the original email (c#), whereby when the receiver replies back, that GUID is also sent back for reference.
I have tried setting the MessageID, whereby using Outlook, the In-Reply-To value is set with the original ID, however using some webclient email systems, that value is not created on reply. Is there another way to sent this info through email headers?
Some variation on VERP is probably the most reliable...
http://en.wikipedia.org/wiki/Variable_envelope_return_path
Specifically, instead of having all your replies coming to the same address, encode the information you want to persist into the From address for the email.
For example, in the case of a helpdesk ticket, you could use something like:
From: Helpdesk <support-ticket-123#example.com>
To: End User <user#example.org>
Subject: Ticket #123 - problem with computer.
That way, regardless of what the user edits in the subject or text, you know what ticket is being referred to by the receiving email address.
I don't think you'll be able to do anything that is perfectly reliable by headers alone -- the number of clients that would have to cooperate is immense.
Most systems that do this work by including something in the body of the email that is sent that allows it to identify the message, and including text instructing the recipient to include that block of text in the response. You could also try including it in the subject (and including text in the body to leave the subject unchanged). That's how some mailing list managers I've seen do it.
I stumbled upon this question, and it's been very informative. This, however, leaves me with one question: Will using VERP, or a variation of editing the 'reply-to' or 'from address', cause the messages to be locked up in spam filters?
I have read that spam senders often change the bounce address to prevent their servers from getting clogged with bad email address bounces. Is it a spam risk to assume this approach?
The most reliable way is to put the ID in the subject, which should be preserved throughout replies.
(It doesn't hurt to tell your users that they should keep the subject intact.)
RT, a popular ticketing system, does this. They use a simple subject format like "[Ticket #123]" and key off of 123.