Its really frustating that EmailComposeTask doesn't have any way to send attachments. I googled this and found MailMessage dll. I don't know whether it is secure or not because user gonna send his password.
Now I am thinking tot build my own service, send data from phone to service, and service will use smtp to send email with attachment.
Now I want to ask, Am I right? What kind of service I use?
I dont know about security concerns of MailMesssage.dll.
However, if you wish to send transactional EMails, then there are few services available. In such a case, you will not be required to create your own service. The popular one's are:
Sendgrid
Mandrill by MailChimp
MailGun by Rackspace
All services provide free tier and may be helpful, if you need to send, less EMails. Moreover, besides SMTP, these services provide Web APIs, so you can send mails using REST interface.
Related
In looking at amazon's SES API documentation it looks as if there is no clear cut way for sending attachments unless a raw email is created. Where as when using an SMTP Client to amazons SES sending emails with attachments seems more manageable. Outside of the messageid returned from the SES API is there any benefit to using the api over the SMTP client? Or am I completely missing the boat and there is an easy implementation of adding attachments to an email in the SES API?
I use SES all the time, have never felt a need to use anything other than the SMTP interface - which is a simple drop-in replacement for any other SMTP service you may be using. Unless you have a compelling reason (and I can't think of any), use the regular old SMTP way. Then if you ever need to move off, it would be trivial to switch to another service.
Well, the main reason to use the api is you can set a domain key to improve delivery success rate. This is useful if you send a huge amount of emails. In general, unless you have an easy way to implement the api (like django-ses or similar) just stick with SMTP.
A website that I used my password on was compromised and the monkeys in charge had stored everything in plaintext. The list was released publicly online. Needless to say, my password and email were among them.
I would like to send emails to everyone else who was listed (thousands) and inform them that to continue using their password is unsafe. My language of choice would be C# and I would be sending them from my gmail with the help of this code: Sending email in .NET through Gmail
I can pretty much assume gmail will lock me out before I finish 10 in under a minute. Apart from sending emails out intermittently, how can I do this?
edit: I agree with the responses. I should instead send one email. Is there a limit to the amount of recipients I send an email to from gmail?
If happy to spend a bit of money for a reliable solution, you could integrate (very easily) with http://sendgrid.com. Provides you with heaps of features to track delivery of email and reporting/analysis of email opening, clicking etc.
Gmail does have limitations on how many emails you can send per day, and I would not recommend for your usage.
Or use some online mail marketing tool like MailChimp http://www.mailchimp.com
This service can easily send thousands of e-mails without problems. They have a free service too. Where you can store up to 2,000 subscribers. Send up to 12,000 emails per month.
It even has a REST API available for interacting with it from a custom app.
However I don't know if you are legally allowed to sent e-mails to the addresses on the list. I know it's for a good cause, but please be warned that this sort of e-mails can be considered as spam.
Again, don't build it yourself, but use off-the-shelf specialized services: I suggest looking at
Amazon Simple Email Service (SES)
which is part of Amazon Web Services (cloud storage, computing and more).
Amazon SES lets you send bulk and transactional email to customers in a quick and cost-effective manner
Service highlights include:
Simple
Inexpensive
Reliable
Scalable
I want to ask you about sending files using WCF.
I want to implement service, to send fax and emails. My case looks like that:
The service will be hosted in windows service.
I would like to make this service visible on the local network only. (So I will probably use netTcpBinding)
and It will be great, when a customer who wants to send a fax or send email with attachments, will have to use only the "SendFax" function with specific parameters. I mean.. How to do that, so it would be very simple for client?
I think the biggest attachment could be up to 20MB, I don't know how it looks like in case of a fax. But I think it will be MS Word file, so 20MB will upper limit.
I want to ask you how to implement, the server-side part of WCF service?
Use buffered upload or streamed upload ?
Could you give me a link to good example or article ?
Any help will be great,
Thanks
A WCF service endpoint can accept a byte array of variable sizes so it shouldn't be a problem for a client to send a pdf,word, etc document as a byte[] to the service. The default netTcpBinding settings will need to be adjusted to accomodate the large file sizes.
Your windows service will host your WCF endpoint (e.g., SendDocument()).
The service's implementation of this method will use the standard System.Net.Mail.SmtpClient class to send the email. See the MSDN documentation for SmtpClient and especially the MailMessage class, which among other things has an Attachments property you can use.
We have a website sending mail alerts to end users. The site has been developed in c# ASP.NET.
I want to find the best way to send the email alerts to my users. Making sure the mail is not trapped in any spam filters. I read on the internet it is best to sent the mail directly from the web server and not route via an SMTP mail service such as google apps or Postini.
Can anyone tell me if this is correct?
First of all
Making sure the mail is not trapped in
any spam filters
Is not possible - otherwise spammers would do this. You just have to make sure you're domain isn't associated with any spamming activities and watch for keywords within the email.
I read on the internet it is best to
sent the mail directly from the web
server and not route via an SMTP mail
service such as google apps or
Postini.
This point doesn't make sense - your e-mail will never be delivered if it doesn't get routed via an SMTP server, the average message will pass through multiple on its route to the recipient.
The answer is to not actually send email and let someone else deal with the problem. I'd look at postmark or Amazon's simple email service.
We had problems that mails sent with local server often get trapped in spam filters until we implemented SPF on our mail server.
http://en.wikipedia.org/wiki/Sender_Policy_Framework
But I am not admin, that's just what our admin said, and after that we have no problems anymore.
btw. maybe would be better to ask on serverfault.com
I want to send an sms to a mobile phone through my C#, C++ code. Can any body help me. I dont want any mobile, or any external device attached to my computer. I am just having my laptop, or desktop PC and in that i want to write a C++ or C# application which can send an sms to a mobile phone.
Clickatell is a popular SMS gateway, which covers 819 networks in over 220 countries.
The API offers a choice of connection options via: HTTP/S, SMPP, SMTP, FTP, XML, SOAP and COM. You can simply choose any suitable connection method that you feel confortable using in C# or C++.
To give a few examples, the HTTP method would be as simple as requesting the following URI from your application:
http://api.clickatell.com/http/sendmsg?to=NUMBER&msg=Message+Body+Here
The SMTP method would consist in sending a plain-text email to sms#messaging.clickatell.com, with a body as in the following example:
user: xxxxx
password: xxxxx
api_id: xxxxx
to: NUMBER
text: Message Body Here
The other methods are similarly easy to interface with, in my opinion. You can check out the full details from the Clickatell API Guide.
There are a couple options out there. You could use a gateway like Twilio, Clickatell or the many others. These cost money but are more reliable than other methods. I wrote a C#/.NET library for Twilio that makes it super easy to use.
Alternately you could ask each user for their carrier, then send an email to their phone's email address. This is less reliable and requires you to know what carrier they use and if they change carriers, they have to remember to tell you.