public.py | : snake : replace '__all__ ' with ' @ public.add ' decorator

You have a simple mistake in the setup script, this line:

I had to download python36.dll and save it in C:\Windows\System32

Because of the lack of library versioning, the fact that the directory containing the executable is always on the shared library path and the ensuing sloppy habit of keeping random copies of the same shared library in various directories, Windows users got in the habit of downloading executable code from somewhere on the internet and running it.

This is a dangerous and detrimental practice. You obviously got the wrong incarnation of the Python shared library, or you are missing some other important files, and as a consequence PostgreSQL crashed when using it.

Remove any DLL files from rogue downloads, get a Python 3 installation package and install it in the regular fashion.

By default, on a cPanel server, emails are sent using EXIM. So the email log (for received and sent emails) is located at /var/log/exim_mainlog. There you can see detailed info about whatever emails were sent to or by your server.

A lot of factors can lead to your emails being delivered to junk. Just to name a few: - your server's ip address is blacklisted (you can check it using tools like http://mxtoolbox.com/) - you do not have a proper hostname defined for your server - you do not have a proper reverse DNS for your server - SPF and/or DKIM are not configured properly

Try sending an email from your server to a Gmail address for example, a Gmail address that you own. Then go to Gmail and even if the email landed on Junk, please check the email headers. There you get info about what checks have been made, what Spam score you got for your email and so on. That would be a good starting point for you to figure out why the sent emails land in Spam/Junk.

Since you have provided very little information, is hard to guess or provide a proper answer...

This is caused by limitations in the underlying C functions that python uses for some date and time handling. These functions are implemented differently on different platforms, which is why it doesn't affect everybody (I had to borrow a Windows box to replicate the error).

The docs for datetime.utcfromtimestamp mention these limitations:

This may raise OverflowError, if the timestamp is out of the range of values supported by the platform C gmtime() function, and OSError on gmtime() failure. It’s common for this to be restricted to years in 1970 through 2038.

Fortunately the same docs suggest a workaround, and, as the function in the DateTimeLine class that contains the troublesome line is so short we can easily create our own class that inherits from DateTimeLine and over-rides the function.

It looks like you could rewrite your code to use get_or_create, which has some handling for race conditions.

To avoid the An error occurred in the current transaction error, you need to wrap the code that can raise the IntegrityError with transaction.atomic: