#go#dovecot#email#email_marketing#mail#mailserver#newsletter#newsletters#postfix#rspamd#server#smtp
BillionMail is a free, open-source mail server and email marketing tool that lets you send newsletters, promotions, and transactional emails with full control and privacy. You can install it in about eight minutes, connect your own domain, and start campaigns easily. It offers advanced analytics, unlimited sending, customizable templates, and keeps your data secure on your own server. This means you avoid expensive fees, hidden costs, and third-party tracking, making it ideal for businesses and individuals who want powerful, private, and flexible email marketing[2][3][4].
https://github.com/aaPanel/BillionMail
Eppie — open protocol encrypted p2p email
=> https://eppie.io
=> https://github.com/Eppie-io
Eppie is a next-gen providerless email that allows its users to own their accounts, addresses and data. In addition to its own p2p network Eppie can communicate with other popular decentralized networks, like Ethereum, and is capable of interacting with conventional IMAP/SMTP email. It is beautiful and easy to use, just like a normal email client.
Features:
🌎 Works on all platforms: Windows, MacOS, Linux, iOS, Android
🕶 Privacy-first: there's no such thing as optional encryption
🚀 P2P messaging: without servers nobody's holding your hand anymore
🔑 Identity manager: key management is a breeze
💾 Decentralized backup: your data is safe and only yours
🤙 Ultimate interoperability: Eppie can communicate with Ethereum, Bitcoin and more
📬 IMAP/SMTP compatible: connect to Gmail, Microsoft Outlook etc.
🦄 Proton Mail Authentication: Eppie is the first native desktop client capable of that
🔐 PGP encryption: stay safe even with conventional email
🤖 Local AI agents
NOTE: the project is early in development, not all of the features are publicly availabe
via @dcntr
#email#p2p
https://docs.djangoproject.com/en/1.11/howto/deployment/wsgi/
How to deploy with #WSGI
Django’s primary deployment platform is WSGI, the Python standard for web servers and applications.
Django’s startproject management command sets up a simple default WSGI configuration for you, which you can tweak as needed for your project, and direct any WSGI-compliant application #server to use.
#django
http://www.bogotobogo.com/python/python_redis_with_python.php
Redis with Python
In order to use #Redis with Python, we will need a Python Redis #client.
In following sections, we will demonstrate the use of redis-py, a Redis Python Client.
redis-py requires a running Redis #server. See Redis Install for installation.
https://pythonspot.com/en/python-network-sockets-programming-tutorial/
Python network sockets programming tutorial
In this tutorial you will learn about in #network programming. You will learn about the #client-#server model that is in use for the World Wide Web, E-mail and many other applications.
#socket
https://docs.python.org/3.6/library/cgi.html
#cgi — Common Gateway Interface support
A CGI script is invoked by an #HTTP server, usually to process user input submitted through an #HTML <FORM> or <ISINDEX> element.
#server
http://aiohttp.readthedocs.io/en/stable/web.html
Server Usage
Run a #Simple#Web#Server
In order to implement a web server, first create a #request handler.
A request handler is a #coroutine or regular function that accepts a Request instance as its only parameter and returns a Response instance.
https://blog.miguelgrinberg.com/post/designing-a-restful-api-with-python-and-flask
In recent years #REST (REpresentational State Transfer) has emerged as the standard architectural design for #web services and web #APIs.
In this article I'm going to show you how easy it is to create a RESTful web service using Python and the Flask microframework.
What is REST?
The characteristics of a REST system are defined by six design rules:
Client-Server: There should be a separation between the #server that offers a service, and the #client that consumes it.
Stateless: Each request from a client must contain all the information required by the server to carry out the #request. In other words, the server cannot store information provided by the client in one request and use it in another request.
Cacheable: The server must indicate to the client if requests can be cached or not.
Layered System: Communication between a client and a server should be standardized in such a way that allows intermediaries to respond to requests instead of the end server, without the client having to do anything different.
Uniform Interface: The method of communication between a client and a server must be uniform.
Code on demand: Servers can provide executable code or scripts for clients to execute in their context. This constraint is the only one that is optional.
https://github.com/KeepSafe/aiohttp
Supports both #client and #server side of HTTP protocol.
Supports both client and server Web-Sockets out-of-the-box.
Web-server has middlewares and pluggable #routing.
Optionally you may install the #cChardet and #aiodns libraries (highly recommended for sake of speed).