I am trying to make an e-commerce website in Django and react. but I am not able to find a way for this scenario.
whenever a user purchases something a confirmation email should go to the user and one to the admin that a user buy something.
can we do this just by code or we have to use something like Mailchimp?i want to do it by writing code.
You don't need a service like Mailchimp for this. You need to write your own code for sending emails.
To send emails in Django you need to configure a mail server. You can use your own mail server or use providers like AWS SES (Simple Email Service) or SendGrid.
Then you need to write the code that will send two emails after the purchase. Ideally, it should be done in the webhook that will wait for payment confirmation from your payment provider (for example Stripe).
BTW, I'm working on Django+React tutorials at SaaSitive and just committed example code how to send activation emails (after registration) https://github.com/saasitive/django-react-boilerplate
What Azure service allows us to run at a fixed interval (IE every 5 min), and if a given Outlook/mailbox folder has one or more emails in it, then send one notification email?
We have a Logic App that does email processing. If the processing fails for whatever reason, the email is placed into a "Failed" folder, and an email notification is sent out. The issue is when a dependent service is down, we are getting hundreds of email an hour.
We tried creating a second Logic App that runs every 5 min, sending email if it found email in the folder that is "flagged", but we still received one email per flagged email.
We are thinking a separate service that runs every so often, and if a folder has email in it, then send out a single email.
Actually there is a Outlook trigger action to detect if there is an email is flagged. It supports to change the Folder,Importance,Interval and add other parameters to match.
And this is the action Optional Parameters description.
I have this listing site built up in cake php. The site has profile pages containing contact forms to contact these profile owners. I have integrated mandrill to this site to manage email notification sendings.
If a general visitor contact the profile owner then email goes to three people
To the Profile owner
To the site Admin
To visitor as well.
Now the problem is certain domains are continuously trying to send spam messages to my clients.
I have tried following to block these emails:
From Mandrill Settings, I have blocked these emails. This method works
perfectly in blocking all 3 emails initiated by spammer's email but then I
cannot block such emails all the time, as this doesn't block whole domain.
In mandrill Outbound, I have set up Rules to block emails which contain spammy content. But then I can only prevent email sending from my site to these emails and NOT what these email addresses send to my clients. As this only work for outbound emails and not inbound emails.
I have also added math captcha tool (as mandatory obviously) in the forms.
The site is hosted on Linux server. is there any way to prevent these spam emails by setting some rules like
if the email address or body contains words like 'seo, promotion..'
then Reject email
So it will block all such emails:
seo#example.com
abc#seo.com
a.bc#hostsite.com
Thank you for reading and sorry if I am confusing you.
Any help would be appreciated.
I am trying to send some reminder emails to the users of the site. I have setup in Amazon EC2 and CakePHP as a language. I have a bit of code in CakePHP Shell which send the mail to particular recipients. I tried to setup as a cronjob.
My cronjob is working but sending the mail to /var/spool/mail/ec2-user instead of original recipients. I know I can send emails to multiple email addresses using MAILTO="..." in crontab but that all would be static addresses. Though my code has the email address of users of the website (remainder of payment in every 2 days) but still mail is being forwarded to /spool/mail/.
How do I setup the cronjob to send emails to dynamic email addresses or bound cronjob to send the email to the same recipient mentioned in CakePHP code? Any help would be appreciated.
So I'm writing a mobile app and have reached a point where I need to allow users to register a username. I'm doing this by asking for an email address, username and password.
Typically, it's been normal to set this sort of thing up on the web by having the user confirm his email address by clicking on a link sent to his inbox.
Needless to say, on a mobile app this is a bit clunky as the user will be redirected out of your app and into his browser.
So I had a look at how other mobile apps are doing it (WP7) and was surprised to see that DropBox and Evernote both allow you to sign up without confirming your email address. The end result of this is that I was able to sign up with completely bogus email addresses and/or valid email addresses that don't belong to me.
I assume this is done on purpose.
Your thoughts?
I came across the same issue when writing a social networking style app. I chose to have the user create a username and then provide and email and password. I do not verify the email address and I've never attempted to send any email to them (yet).
What I would suggest would be alternate ways to validate a users email address. My app allows users to do Facebook Connect. All they have to do is log into Facebook, and the app talks to Facebook to confirm that they are using a valid email address. No need to verify it with a URL in an email.
I believe Twitter has a similar service and there may even be a few others that provide an API.
I've also discovered that a lot of people just want to tinker around in the app and not create an account at all. It's definitely a balancing act
I'd say it depends on your app and how important it is to ensure users have valid email addresses. In an app I'm creating now, we want to discourage users from signing up with multiple bogus accounts (because our system could be gamed that way) so we're not allowing users to log in until their email address if verified. On other sites however, it might not be such a big deal so why bother users with that extra step?
As for a mobile device, I don't see why you can't still send a verification email that sends them to your website to verify their email address. There are plenty of mobile apps that also have a website users can log into to manage their account.
Another option is have multiple "states" for users. Before they validate their email, they are in a "pending" state. Once they click it, they're in an "active" state. If you store the createDate for the user, you can periodically remove pending users older than 1 week (or however long).
The bonus is that you can easily add more states, such as suspended or deleted.
Personally, I wasn't too happy for users to create accounts with any old email address.
I think a few decent options are:
send a confirmation email with a link that uses a Custom Url Schema to redirect back to the app (although this is only good if they use the link on the same device)
send a short PIN in the email for them to enter back in the app.
send a confirmation email with a web link, have your server confirm the valid email/token, and have your app check the account status either periodically or with some sort of realtime tech like SignalR or Firebase.
I prefer the last one, although hardest to implement. A user might well have their phone in their hand and their laptop next to them, register in the app and try to click the link in the email that just showed up on their laptop. I like the idea of the app then just "knowing" that they've validated.
Do you have a web server? Write a web service that does the validation for you on the server side, and sends back the result.
Either you can use some platform, such as Facebook connect as #Brian replied above, or you may give users a reasonable timeframe to verify, for example, a few days or even a week. After that, the account gets removed.
You can even have your app issue notifications to remind the user to verify his account (such as every day, or on the last date of the verification.
Don't ask for email confirmation on mobile and allow the user to use the service. When the user is using a PC, then ask the user to confirm his email.
I won't defend my recommendation because most of the solutions here are valid. There isn't one correct way. You asked for ideas and here's one.
A good strategy is to allow people to use as much of your app as possible given the amount of data they've provided.
For example, in the case of a newsreader you might let someone browse your app without registering, then require an account for offline syncing, and a verified email for alerts. Always give people a good reason to take the next step, and build engagement first, then people will forgive you pestering them later.