email-actions | tiny SMTP server with a rules based engine | Email library

by shantanugoel Python Version: 0.1.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | email-actions Summary

email-actions is a Python library typically used in Telecommunications, Media, Media, Entertainment, Messaging, Email, Ruby On Rails, Docker applications. email-actions has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install email-actions' or download it from GitHub, PyPI.

email-actions is a tiny SMTP server with a rules based engine to trigger any actions (notifications/commands etc) based on the emails sent to this server

Support

Quality

Security

License

Reuse

Support

email-actions has a low active ecosystem.

It has 27 star(s) with 5 fork(s). There are 4 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 1 have been closed. On average issues are closed in 15 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of email-actions is 0.1.0

Quality

email-actions has 0 bugs and 0 code smells.

Security

email-actions has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

email-actions code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

email-actions is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

email-actions releases are available to install and integrate.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

email-actions saves you 172 person hours of effort in developing the same functionality from scratch.

It has 425 lines of code, 21 functions and 11 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed email-actions and discovered the below as its top functions. This is intended to give you an instant insight into email-actions implemented functionality, and help decide if they suit your requirements.

Process a message from a message
Match rules
Get the list of actions for a filter
Get the rules for a given filter
Send an email notification
Read the configuration for a specific plugin
Create a new socket
Create a socket
Check if the configuration file exists
Create a config file
Sends an event
Join a notification
Start server
Stop the controller

Get all kandi verified functions for this library.

email-actions Key Features

No Key Features are available at this moment for email-actions.

email-actions Examples and Code Snippets

No Code Snippets are available at this moment for email-actions.

Community Discussions

Trending Discussions on email-actions

passing state in email actions - continueUrl

QUESTION

passing state in email actions - continueUrl

Asked 2017-Sep-16 at 12:43

In the comments of the accepted answer it was noted I should set my firebase version to 4.3.1, not my last version 4.2.0

Hi this should be rather straightforward, I'm following the documentation at: firebase passing state in email actions as well as changing the default email-handler

I'm looking to redirect the user after he has verified his e-mail to a new url. The url is already in the Authenticated domains in firebase.

I also already have my actionCodeSettings:

...

ANSWER

Answered 2017-Sep-14 at 21:39

1) The default action URL is https://faros-fe2f5.firebaseapp.com/__/auth/action . Am I supposed to change this? It will change automatically based on my actionCodeSettings I guess

If you want to handle the verification link in your own page, you can change it to your own link but that can only be done in the Firebase Console -> Auth -> Email templates section

The continue URL ('http://myurl.io/join') is the final redirect link which would be embedded in the continueUrl query parameter of the link. You would typically after email verification is complete, show a continue button to go to that link. This can be passed from the client and must be a whitelisted domain.

2) At line 113 we have the function of interest and it takes the parameters that are retrieved through getParameterByName. How is the continueUrl called at this point?

You only need to write this if you are using your own email action URL and not the .../__/auth/action link above. You would after email verification is applied, show a continue button to go back to that link.

I recommend you try the flow with the default widget, click the link, verify the email and then click the continue button. You can mimic that and build your own custom landing page based on that.

Source https://stackoverflow.com/questions/46216774

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install email-actions

Pre-requisites: You need Python 3.4+ to be able to run this.
Install using pip (May need to use pip3 instead of pip according to your OS/python installation. May need to use sudo prefix before below command if installing system wide)
Install directly

Support

Feel free to fork the repo and send PRs for any changes. If you can't make changes but want to report issues or provide feedback, open an Issue on github or ping me on twitter @shantanugoel. You can contribute either to the core or write a plugin for your usecase. The only guiding principle is to keep it as simple/minimal as possible.

Find more information at: