I have an app written in PHP that I am porting to Meteor. This question is really two parts:
1) Currently, my server forwards all email to a PHP script that parses out the response and inserts it into a database, allowing users to respond to message threads by emailing reply+someidentifier#myapp.com. What is the best way of accomplishing this now that I am using Meteor?
2) From a performance perspective, should I running this on the same server that is hosting my application. Is this scalable?
I didn't notice it but you're using procmail? I've never done this before but you could tell procmail to put its files into a folder that Meteor can access. Then use the fs npm module to parse through these every few minutes & put these into a collection using the server side js.
From there you could make the UI you want to use to reply/make threads, etc.
Meteor uses Mailgun http://www.mailgun.com/ to send email. It's free to send up to 200 email per day.
I never tried it, but Mailgun can also receive email and then call a HTTP POST request to your app (meteor) that contains the information about the mail. With the router package, you should be able to handle this request on the server.
Related
Hope you all are doing well. I came up with very important question. My task was to creating an email box using Laravel. I did it successfully using Imap. My problem is related efficieny and performance. Currently i am sending request after every 20 seconds to the server and getting new email messages. I dont want to send requests to server. Is there any way to make it real time. For example, my webmail server should inform me that he has received new emails and i would display new messages in my inbox in laravel application.
I am not bound to php. any framework and progamming language are acceptable. Need solution just.
Any help would be highly appreciated. Thanks in advance.
As the title says, I would like to know if there is any way to send emails without having to use an external service, that charges me for sending the messages, or having to use an SMTP server in which each user has to be registered.
I have also seen pages like email.js but I don't want to have to pay for that if there is a possibility to do it on my own. It is also not useful for me to open the Gmail or messaging application of the device itself since I already know how to do that and it is not what I want.
For better understanding, I will give an example of what I want to do.
What I want is that from my application the user writes a message and from there that email message is sent to several different users from a list, without having to log in or anything, since the emails will be sent from my own email account. gmail that I have specifically created for the application.
I have seen the smtp server but from the information that I have seen that server implies that I have to log in to be able to have the token and that is not what I want because I want that once I configure everything there is no need to do anything else that people receive your messages and that's it.
I don't know if this is possible but I hope someone can help me.
Sending emails without your user logging in would require you to have either the credentials stored in the app (which is unsafe) or use a custom backend server that will host all the credentials that cannot be extracted. I would advise going with the backend route because it is easier to setup and your application will simply perform a HTTP request to get it done.
From the documentation of the mailer package, you can implement the server method pretty easily and get it moving. You will have to find a free web hosting service to deploy to.
There would really be otherwise no other way to get what you desire for virtually free.
When I need to send occasional notification emails from an Erlang app (there's no need for the app to receive emails), I can pick one of two ways:
use a simple OTP app only for sending, like esmtp
use a simple (send-only) OS app like ssmtp and make a call to it from the Erlang app via os:cmd and compose the message (containing information from the running system) by writing to a file from within the Erlang app.
They both work, but I don't know if there are any dis/advantages to either approach. Which is better suited for a production system?
You may try to use AWS SES (Send Email Service)
there is aws erlang api to send mail via erlang driver
so you may send formatted or raw messages including html pages.
also you may add ses headers to see statistic about how many email have opened by customer and what clicks to they done
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/event-publishing-cloudwatch-tutorial-send-email.html
I am so confused. My simple requirement is: i have an application which contains confirmation form i.e. nib file. It contains some textFields like name, age, email etc. I simply want when somebody click on submit button application send background and automatic email to email defined in textField. that email contain all information like name, age etc. User need not to fil anything and it should work in background. There are so many application do the same thing. I am creating booking application.
So how can i impliment this behaviour.
Apple does not provide a way to do this - and for good reason. Sending emails from the phone automatically introduces a lot of security risks.
I am willing to bet that the apps that do this use an intermediary server to which they post the data. When the data is posted then the server handles the sending of the emails.
To do this:
Send an HTTPS POST request to your server application.
From your server application, send an email via SMTP (or APIs built on top of SMTP).
Google AppEngine provides a simple and cheap way to create such a web service, running on top of Google's cloud-computing infrastructure. The sending mail from AppEngine help document includes detailed examples of how to send mail from your server application (assuming you use the Python version of Google AppEngine).
Unfortunately, there is no official feature for this but you could download a third-party library. Refer here for a couple of suggestions.
I have an application running on WebLogic Server with 6 instances. Many requests for the application come from Email. We already set up an email account that will be used by all clients to send email to. But the problem is that the email account inbox can only be opened for reading by a single connection, unlike a typical database.
Currently I can only deploy the email reading service on a single server instance, this will effectively create a single point of failure and unbalanced load. What's the best way to read from the same inbox from multiple servers? I am thinking developing something using a database table, sort of leasing, whoever locked the table own the lease and can connect to the email server, but this is pretty hard to implement correctly in all circumstances.
I am not sure why you say that only one client can access the inbox as POP certainly can handle multiple connections to the same inbox and this can be configured in the mail server. You might need to talk to your mail server admin.
I haven't worked with Weblogic to give you a specific answer, but you should also be able to have a service written that checks the incoming mail and process incoming mails into a database as you wanted. Once the information is in a database, you can use it via multiple hosts. This is a better approach as this can be setup to prevent multiple clients responding to the same email.