I'v encountered an issue with gmail mailto: link, the link works fine for Outlook in both iOS and BB OS.
See below:
mailto:firstname.lastname#gmail.com?subject=thread#:1234123123123
But in gmail, the subject thread#:1234123123123 got truncated because # symbol.
Subject: thread
I found that after removing # symbol, the subject field populated well, but the # is required. Any ideas?
Thanks in advance.
Most likely has to do with that # character not being URL encoded.
Try mailto:firstname.lastname#gmail.com?subject=thread%23:1234123123123
And take a look at http://www.albionresearch.com/misc/urlencode.php when you have a chance.
Related
I am sending an email to new users asking them to verify.
This is my email
But when I am testing the email in mail-tester.com, I get this HTML_IMAGE_ONLY_20 message. But I do not have any image sith text in or am I misunderstading the error?
I assume that’s a SpamAssassin rule. It is a rule that says that your message is composed primarily of image and not text. In your example you have a logo and not much text, so I’d assume it’s that. You could look up the source code for the SA rule and see what it’s actually looking for.
My app is downloading eMails from a POP3 server. But it receives "strange" subject lines. I see there is a pattern of coding in there. But what exactly is that coding? What do I google for if I want cover the parsing of lines like that?
=?utf-8?Q?HMS=20will=20no=20longer=20provide=20Netbiter=20SIM=2Dcards?=
The eMail header is:
Subject: =?utf-8?Q?HMS=20will=20no=20longer=20provide=20Netbiter=20SIM=2Dcards?=
So I know it's coded by the sender. Also this is just one of many header lines, which all seem to be valid. The subject is obviously HMS will no longer provide Netbiter SIM-cards after you replace "=20" with spaces and all the other stuff. The eMail is just a notification from a supplier.
**Found it myself:** [RFC 2047][1]
I don't remember exactly but i have experienced a issue like this before. If the subject is greater than some length of character (which i think is 75 chars) then subject will not be parsed properly.
This used to be a problem in codeIgniter (I don't use it now, so don't know the current status of this issue)
To resolve this issue you might have to change your email config.
There might be other reasons for this issue but i think this is because you have more characters in your subject.
I have the problem with google mail markup
https://developers.google.com/gmail/markup/overview#gmail_actions
I tried Json-Ld and Microdata. But i have nothing. When i try to send me mail from google tester https://script.google.com/ - everything is ok and i get the letter with quick button. But when i send the same letter from my server- i get letter without quick button. At my server i tryed to change mail's charset, encoding, i tryed to use php function mail and PHPmailer script (yii)- the result is the same.
What should i see the next
Thank everybody for answers. lol
But i found that i should add me to wite list at google here
https://developers.google.com/gmail/markup/registering-with-google
Writers from google didn't mention about it at first part of instruction
I have a website that emails a link to the invoice when an order is complete.
The link should be http://mysite.com/QuoteAndBook/Confirmation?orderId=123
But for some reason it is:
http://204435-204435/QuoteAndBook/Confirmation?orderId=123
The host portion of the link is generated using HttpContext.Current.Request.Url.Host but I would expect that to return "mysite.com", not "204435-204435".
Any idea what's going on?
Turns out the IT guy was changing something with the server configuration and broke it. Not sure what he did but he's fixed it now...
I have a URL stored in a Sharepoint 'Link to a document' that contains the Nordic Character 'Ø' as hex(%D8). Sharepoint is encoding the % symbol, (thus making it %25D8).
If I enter the URL directly into an address bar, it works fine.
If I don't URL encode it, I still get the same problem.
Anybody got any ideas?
So what happens if the URL is stored as 'Ø' in the URL instead of already having it encoded?
Also do you have any special process running that stores it for you? Because if you don't have any custom code interacting with this, this is probably better asked on serverfault.com.