Email Server & Routing issue

General
1

When I configure email server and rounting to wedj.com hosting I get the below error message. I want messages from gigbuilder to come from sales@dj-geek.com

ERROR:Fatal error on SSL transport protocol: transport: <_SelectorSocketTransport closing fd=6> Traceback (most recent call last): File “/usr/lib64/python3.9/asyncio/selector_events.py”, line 916, in write n = self._sock.send(data) OSError: [Errno 9] Bad file descriptor During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/usr/lib64/python3.9/asyncio/sslproto.py”, line 690, in _process_write_backlog self._transport.write(chunk) File “/usr/lib64/python3.9/asyncio/selector_events.py”, line 922, in write self._fatal_error(exc, ‘Fatal write error on socket transport’) File “/usr/lib64/python3.9/asyncio/selector_events.py”, line 717, in _fatal_error self._force_close(exc) File “/usr/lib64/python3.9/asyncio/selector_events.py”, line 729, in _force_close self._loop.call_soon(self._call_connection_lost, exc) File “/usr/lib64/python3.9/asyncio/base_events.py”, line 751, in call_soon self._check_closed() File “/usr/lib64/python3.9/asyncio/base_events.py”, line 515, in _check_closed raise RuntimeError(‘Event loop is closed’) RuntimeError: Event loop is closed - sales@dj-geek.com - email:sales@dj-geek.com

2

Hi @DjGeekusa,

It sounds like you’re encountering an SSL transport error when trying to configure your email server for Gigbuilder. While the documentation doesn’t provide a direct solution for this specific error, I can offer some general advice:

  1. Stick with Gigbuilder’s Default SMTP: Unless you have a specific reason to switch, using Gigbuilder’s default SMTP is recommended as it is reliable and includes delivery notifications.

  2. Test Email Button: After making any changes to your SMTP settings, be sure to use the “Test Email” button. This can help you identify issues before they affect real client emails.

If you continue to experience issues, please reach out to our support team for further assistance. They can help troubleshoot the SSL error more specifically.

Best of luck, and let me know if you have any other questions!

– Ashley, Gigbuilder Support

3

After the server moves for hosting, the backend api was using an older ip address – that has been resolved along with a number of minor fixes to the mailer script.