Re: [mezzanine-users] Account activation email is not being sent to the users
If mailgun shows it as delivered then it was probably picked up by the user's spam blocker. I've seen this a lot from mailgun, presumably because their api's are often used for mass mailing. On Sat, Jul 16, 2016 at 8:19 PM, Akhlaq Rao wrote: > It's a weird problem, I am stumped to find the starting point. > > I am using mezzanine Accounts feature, when a user signup I receive an > email that an account requires activation, when I activate the account user > doesn't get the email about account activation. I tried different email > addresses but none of them are receiving emails, when I use the same email > as ACCOUNTS_APPROVAL_EMAILS then I receive the email. > > The mailgun shows me the email was deleiverd but user never receive the > email. I tried mailgun API to send the email directly to different > addresses and it works fine, please help me to find the solution as I > already spent hours to find the problem. > > ACCOUNTS_ENABLED = True > ACCOUNTS_APPROVAL_REQUIRED = True > ACCOUNTS_VERIFICATION_REQUIRED = True > > > EMAIL_USE_TLS = True > EMAIL_HOST = 'smtp.mailgun.org' > EMAIL_HOST_USER = 'postmas...@mg.com' > EMAIL_HOST_PASSWORD = '...' > EMAIL_PORT = 587 > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mezzanine-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[mezzanine-users] Account activation email is not being sent to the users
It's a weird problem, I am stumped to find the starting point. I am using mezzanine Accounts feature, when a user signup I receive an email that an account requires activation, when I activate the account user doesn't get the email about account activation. I tried different email addresses but none of them are receiving emails, when I use the same email as ACCOUNTS_APPROVAL_EMAILS then I receive the email. The mailgun shows me the email was deleiverd but user never receive the email. I tried mailgun API to send the email directly to different addresses and it works fine, please help me to find the solution as I already spent hours to find the problem. ACCOUNTS_ENABLED = True ACCOUNTS_APPROVAL_REQUIRED = True ACCOUNTS_VERIFICATION_REQUIRED = True EMAIL_USE_TLS = True EMAIL_HOST = 'smtp.mailgun.org' EMAIL_HOST_USER = 'postmas...@mg.com' EMAIL_HOST_PASSWORD = '...' EMAIL_PORT = 587 -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [mezzanine-users] Feature Request - Scheduled publishing for exsiting content #411
Suggest reading this thread where we discussed how workflow would work: https://groups.google.com/forum/#!msg/mezzanine-users/4vr3IWT-8UM/ORcbKB_CNeAJ Your option 2) sounds like a subset of what's described there. On Sat, Jul 16, 2016 at 4:42 PM, Shaurya Chaudhuri wrote: > *Feature Request - Scheduled publishing for exsiting content #411* > > I have two approaches for this problem > > 1) Implement an update queue, where the user would update the post/page > and schedule multiple updates that would be published in the future. > Ex:- > A) I update the post to be updated @ 12 AM. Then i update the post to be > updated at 3 AM. > Then the post would be updated at 12 AM and then subsequently update at 3 > AM. > For this we would need to implement another model for updates. > With the old data we can do 2 things > I) Delete the update data after they have been updated. > II) Keep the data in the DB , for future references to the update. > > > 2) Implement a singular future update option. The user would update the > post and schedule it, and if he updates again before the content going live > it would be overwritten. > Ex:- > I update for data to be published at 12 AM then i again update to be > published at 3 AM. then the post will be updated at 3 AM, as i ovewrote the > update whichw as to happen at 12AM. > For this there would be a need to have an update model as well. > > These are the high level conceptualisation of the feature. Would proceed > once you guys review it and tell me what should be better to implement. > > Regards > Shaurya > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mezzanine-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
