Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
In windows Form Application, I am using Mail Definition class to send HTML emails. I got help from this post
Generating HTML email body in C#
I want to send 1000 emails per day. Do I need to set some SMTP setting or I need to write my own code to handle this.
I am thinking to put all the emails in SQL Server table and then select 1000 per day and then delete the addresses to whom email is sent. My approach is good or bad ?
Thanks
You can obviously write your own application to handle this, it's not a major challenge just create a list and take the top 100 each day.
I'm going to assume that you're not simply spamming people and have their permission to contact them. You will also have their email client's spam filters to worry about, in the scheme of bulk email a thousand is not a lot - however each SMTP server builds up a particular reputation based on it's domain and IP address. If you fail these tests you will be delivered into the junk folder (if at all!).
By taking on this work yourself you're likely to have less success than using a 3rd party MailChimp for example. Companies like this spend a long time nurturing their sender reputation and screening their clients (so they don't allow spammers to use their servers). Take a look at my answer to this question to see some of the issues you'll face.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I am working on code to send an sms to customer one week before their subscription reach expiration date. I absolutely don't know how to proceed. I am coding in asp.net c# and sql server.
Create one console Application which will take user whos expiration comes in week, Then write code to fetch the user with there numbers. Then use any third party Api to send sms. you have to send parameters to this Api with your appropriate message.
Then create one job inside sql server which will run everyday which will execute your Console Application code to send SMS.
I would say, separate out publishing and subscription tasks. So in future you can do more with such customers.
Prepare a Publisher which looks for such customers and adds a task to Queue.
Write a Subscriber who watch outs for new queue items and take action.
So in future if you want to make multiple way of communicating to customer like, email then you just need to add more subscriber.
Host your logic as a .NET windows or IIS service.
Benefit: Publisher can independently perform addition.
Subscriber performs task as soon it sees something in queue.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I've been looking around the internet for an answer to this and couldn't find anything using the keywords that I had used anyway.
I'm trying to develop a service in which users can create a wallet to use and control their money from. I don't want to reinvent the wheel and have been looking for public API's and I have found BitcoinLib. The problem I have with this API is that you can only create 1 wallet.
What is the best way I can create multiple wallets (A wallet for each user) and store and control (by control i mean to add addresses, send money, etc) them on my server?
Or is it best to have 1 wallet on the server and write my own code to tie addresses to each user?
I'd prefer not to use an online API for reference such as Blockchain.info C# Library as I do not wish to rely on another service for uptime.
Bitcoin-Core doesn't support an HD wallet, so there's really no point in creating a separate wallet for every single user since behind the scenes they will only control a number of private keys that correspond to the addresses allocated to them. So the best approach in your case is to associate the users with their reserved addresses in your DB. BitcoinLib is an excellent choice for this architecture.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Is it possible using a Windows Server, .NET, C# or PHP to send a SMS text message to q customer's cell phone without depending upon a third-party service (excluding an API provided by a phone company).
My require is to use SMS text messaging to automate authentication when resetting a customer's password, and I have security issues were I'd rather not use a third-party. The more I can keep this internal to our project the better (unless you can justify security in your answer).
UPDATE:
We've decided to use a SMS relay app and this was so easy to implement. There are many apps that already do this. Here is one I'm going to try.
https://play.google.com/store/apps/details?id=eu.apksoft.android.smsgateway&hl=en
you can build a simple mobile app that can query your api and send messages directly from the phone its running on. simple, cheap and you're in control!
we have this solution in a project Im working on atm and it seems to work great. Look up http request and using sms/send message. At least on Android this can be done with just a handful of lines of code :)
You could always use a library like SMSLib:
http://smslib.org/
You will need to purchase a device that SMSLib can work with
To the answers posted by others I would add the following:
use Gammu (or Wammu): attach a phone or gsm modem with usb to your computer and send sms messages using Gammu. Pros: cheap solution, proven by users. Cons: work need to be done with installation and setup of Gammu/Wammu
use a device called: hardware sms gateway (see google search results for possible examples). Pros: reliability and security (those devices has usually built-in database, fail-over mechanisms, etc.). Cons: this costs money, so you've got to make investment.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm working on a web app in ASP.NET that needs to send text messages programmatically. What is the best way to do this? Do I need to know the carrier for each phone number and use each carrier's email-to-text format (i.e. number#vtext.com for Verizon)?
I found this list and some others like it online, but there's no post date on the article, and I'm leery of using those in production without having tested them first.
For free, yes, you can just send to number#gatewayaddress. This has the unfortunate side effect, though, that all your customers need to input who their carrier is. If they switch carriers they need to switch their carrier in your system, too. Here is a list of SMS gateways on wikipedia.
Other alternatives can be using a pay service. One of them that I've used and been happy with so far is twilio. With a service like twilio you can just send a message to a number, and it will find it no matter what carrier they have. In addition, you do have some capabilities for return messages, although I didn't delve into that too much.
EDIT: One more comment about the SMS Gateways: They will change more than you'd like them to. Everytime someone buys someone they phase something out, or sometimes they just decide on a whim to change them. At least with twilio you're only on the whim of one company (whose very invested in keeping it the same).
If you have the budget, I'd consider using an SMS service. They wrap everything into a nice API and handle all the leg work for you.
There are a ton of SMS services out there too. I've used 3 different ones, each has their pluses and minuses, and (I think) a .NET API. In order of preference:
Twilio
Nexmo
Tropo
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
So Yet another SMS question :-)
I researched, but could not find a solution to my requirements.
I do not have a GSM modem, nor can I pay for any Third-Party software for sending SMS. Also I spent quiet some time learning SMS gateways. But when I experimented with it, it failed.eg: I emailed number#textin.in but no message was received at the receiver's side!
The application I am building takes up phone-numbers from a database and sends a different SMS to each number depending on certain condition.
Being a student, I just have to look for Free websites like
http://site3.way2sms.com/content/index.html and others,but don't know how to use them programatically!
So my straightforward question is : "How can I send SMS using just the internet?".
My SMS recipients will all be resident in India. And language is C# using Visual Studio 2010.
Please Help......
Use web requests !
Here is a great examples of Web requesets usage : WebResourceProvider using C#
All you need is just inspect web portal structure and run your web bot. There could be Usual bot's trouble with Captcha but you can google solutions where you can get media (picture of captcha) to your application. (I think that is another question)
You will need to find an SMS provider that provides an API for you to access programatically.
Unfortunately, I don't think you will be able to find any provider that will let you send large amount of texts free.
Some of the providers discussed here may be useful: https://stackoverflow.com/questions/238579/free-sms-api