In Outlook there are options to disabled replying to and forwarding of emails.
My question is how can send disable mail using ews?
VerbStream format is documented. See Glen's blog for an example: https://gsexdev.blogspot.com/2014/09/sending-noreply-noreplyall-noforward.html
Related
My iOS application uses Mailcore to access a user's email account. Sending and receiving is done via SMTP and IMAP, and both processes work as expected for Gmail and Outlook (which both use OAuth for login).
I just added Yahoo (as well as some other providers to the app who do not use OAuth) and for all of these providers I am having an issue specifically with sending messages.
The issue is that although messages DO get sent successfully from my application, they do not appear in the sent folder on the web for the provider.
For example, if I log into my Yahoo account in my application, and send a message to my Gmail account, the message appears in my Gmail inbox on the web, but not in my Yahoo sent box on the web.
I tried adding Yahoo to the regular mail app on iPhone and sending a message from this account - this worked fine - the message shows up Yahoo sent box on the web. So, I then compared the headers of the two messages (the one sent from mail app and the one sent from my app) and the only obvious difference I see is in the line 'X-Rocket-Received':
Mail App:
X-Rocket-Received: from [11.180.250.219] (userName#71.208.72.234 with xymcookie [216.39.61.254])
by smtp203.mail.ne1.yahoo.com with SMTP; 23 May 2014 08:19:54 -0700 PDT
My App:
X-Rocket-Received: from (userName#118.41.27.139 with plain [98.138.105.21])
by smtp214.mail.ne1.yahoo.com with SMTP; 23 May 2014 08:58:29 -0700 PDT
Can anyone answer any of the following questions for me:
1) What does X-Rocket-Received mean?
2) What is the significance of "with xymcookie" versus "with plain"?
3) Is my issue likely to do with my not having an xymcookie?
4) Where might I begin to solve this issue?
Many thanks.
Additional information:
It was placed there by some server along the way. It is a non-standard header. It appears similar to a standard SMTP Received header though.
'xymcookie' is a non-standard authentication method used by Yahoo. It is not, as far as I can tell, publicly documented.
No.
See Remy's answer. Use IMAP Append for most servers. Gmail does not require it, but that is non-standard.
Sending an email with SMTP directly does not put the email in the provider's Sent folder. You have to log into the provider with IMAP and put a copy of the email into the Sent folder as a separate operation. Higher level apps, like iPhone's mail app, handle these details internally.
How to mailto to office 365 like this one on the gmail - Open Gmail on mailto: action.
I have this link:
https://outlook.office365.com/owa/#viewmodel=IMailComposeViewModelFactory
but I have no idea for recipient parameter to put in the TO. Please help guys.
Here's how it do it in Gmail:
sample#domain.com
Now here's what i do in Office 365 but i dont know what is the right parameter for the Recipient:
sample#domain.com
Office 365 now supports composing an email using a URL:
https://outlook.office.com/?path=/mail/action/compose&to=service#domain.com&subject=Customer Service Request&body=Add+Your+Request+here
available parameters:
path /mail/action/compose
subject Customer Service Request
body Add your request here
to service#domain.com
cc is not supported at this point.
See
https://blogs.msdn.microsoft.com/carloshm/2016/01/16/how-to-compose-a-new-message-or-event-and-populate-fields-in-office365/#comment-1645 for more details
This extension worked for me. I just had to edit the Outlook.com url by clicking on "change" and editing it to be something like:
https://outlook.office.com/owa/?realm=example.com&rru=compose&to={to}&subject={subject}&body={body}&cc={cc}
Where example.com should be replaced by your organizations Outlook 365 domain.
I should note that I am on Debian linux with no default email client set at the moment. However, I don't see how that might have any effect as I believe this extension might be simply altering the url that is opened to go to a different url. I could be wrong about this last part since I haven't looked into the extension code.
This cannot be done without using a 3rd party app or setting OWA as the default mail agent on the client computer.
http://social.technet.microsoft.com/Forums/exchange/en-US/38d11e6d-8009-4d7d-8d69-a6701860feb8/setting-up-owa-to-be-used-by-mailto-protocol
Set OWA as default mail agent:
http://blogs.msdn.com/b/tmeston/archive/2004/01/08/48837.aspx
After the recent changes what works for me is:
https://outlook.office.com/mail/0/deeplink/compose?popoutv2=1&to=[EMAIL_ADDRESS]&subject=[SUBJECT]&body=[BODY]
I would like to know if it's possible to provide an email certificate (signed by a recognised CA) so the user clicking on the mailto link can send encrypted email to the owner of the cert ?
hello#gmail.com
Is there any way to do that using the mailto link or using some JS ? Given the mailto link is handled by a local email client, should be possible ?
If there is no direct way to do this, how to make it?
One option is a web form for message sending, served via HTTPS. The server-side handler of the form would compose an encrypted mail on the server and then send it via SMTP. This provides almost the same level of security as direct encryption (given that your server is secure). Unfortunately there's no other simple way to do what you want. Of course, you can put a link for your .cer file download and tell the user to download the .cer file and use it to compose an encrypted mail, but how would you deal with GMail users and mobile users? Web form is more flexible and easier to use for the sender.
You can look up what you according to the current specification can do with a mailto URL in RFC 2368. You'll see that it only refers to the construction of the mail text and headers, not their encoding or encryption. There may be extensions for some mail clients, but that's not something one should generally count on.
Furthermore, Web mail users generally will have problems with such links anyways. Thus, for a solution that has to be usable by anyone, a scheme counting on some client side program is not a good choice.
Thus, some Web form as mentioned by #Eugene accessable only via https would best serve your requirements.
I'm trying to sent Direct Mail Newsletters over SMTP but I didn't get it.
did you get to send Direct Mail Newsletter with SMTP?
Regards
It does not work with the current public version because direct_mail does not yet have adopted to the new mail API.
I have a web application, written in PHP, where we have a couple of files that regularly needs to be sent to multiple recipients. The client wishes to have the mail conversation in their mailbox, so the web app should not send the e-mails itself. Is it possible, and if so how, to do the following:
Create an e-mail with multiple recipients
Add text to the subject and body of the e-mail
Download and attach a zip file which is available on the server
The mail client in question is Outlook - I'm unsure of the exact version.
I'm open to suggestions on which technology to use for this - the client mentioned Visual Basic but I'm unsure of how I could use that on the client side of the web app - or if it's even appropriate.
Assuming that the client want's to send that by hand, you can do all that by using the mailto: in an tag and "&attachment=". The only problem is that attached files need to be localy accessable. If they are not, they are not attached. Exact syntax specifications can be found here: mailto: Syntax
If you have imap access to the customers mail server you could use php imap mail and php imap mail compose to create a email which will just show up in your customers sent email folder.
Also I there is a MIME Message class, where the author claims that it can create and save an email as an .eml file. MIME Class
This is theoretically possible, but only with IE on the client side, and with other limitations and tribulations.
How about a different approach: Have the web server send out the E-Mail, and send a copy into the client's mailbox. Mark the copy with a special header or something, and add a rule in the client's Outlook to sort mails with that header into a specific folder.