starred/opentrashmail

Fork 0

mirror of https://github.com/HaschekSolutions/opentrashmail.git synced 2026-04-25 06:35:55 +03:00

[GH-ISSUE #60] Repeated uncaptured exception #42

New issue

Closed

opened 2026-02-25 23:39:41 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 23:39:41 +03:00

Owner

Originally created by @DasDunkel on GitHub (Nov 16, 2023).
Original GitHub issue: https://github.com/HaschekSolutions/opentrashmail/issues/60

Error is repeated for several emails over and over again, in the UI no information is shown, however, the file stored seems to be half written

Error;

error: uncaptured python exception, closing channel <smtpd.SMTPChannel connected <IP>:4996 at 0x7ff4397f57d0> (<type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0xe0 in position 6753: invalid continuation byte [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/asynchat.py|handle_read|165] [/usr/lib/python2.7/smtpd.py|found_terminator|181] [mailserver.py|process_message|145] [/usr/lib/python2.7/json/__init__.py|dump|189] [/usr/lib/python2.7/json/encoder.py|_iterencode|434] [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|408] [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|390])
error: uncaptured python exception, closing channel <smtpd.SMTPChannel connected <IP>:61516 at 0x7ff4397f57d0> (<type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0xe0 in position 6753: invalid continuation byte [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/asynchat.py|handle_read|165] [/usr/lib/python2.7/smtpd.py|found_terminator|181] [mailserver.py|process_message|145] [/usr/lib/python2.7/json/__init__.py|dump|189] [/usr/lib/python2.7/json/encoder.py|_iterencode|434] [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|408] [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|390])

Let me know if you'd like the partial file sent over in private

Originally created by @DasDunkel on GitHub (Nov 16, 2023). Original GitHub issue: https://github.com/HaschekSolutions/opentrashmail/issues/60 Error is repeated for several emails over and over again, in the UI [no information is shown](https://dunk.dev/PB1oJHpL2OZF.png), however, the file stored seems to be half written Error; ``` error: uncaptured python exception, closing channel <smtpd.SMTPChannel connected <IP>:4996 at 0x7ff4397f57d0> (<type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0xe0 in position 6753: invalid continuation byte [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/asynchat.py|handle_read|165] [/usr/lib/python2.7/smtpd.py|found_terminator|181] [mailserver.py|process_message|145] [/usr/lib/python2.7/json/__init__.py|dump|189] [/usr/lib/python2.7/json/encoder.py|_iterencode|434] [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|408] [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|390]) error: uncaptured python exception, closing channel <smtpd.SMTPChannel connected <IP>:61516 at 0x7ff4397f57d0> (<type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0xe0 in position 6753: invalid continuation byte [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/usr/lib/python2.7/asynchat.py|handle_read|165] [/usr/lib/python2.7/smtpd.py|found_terminator|181] [mailserver.py|process_message|145] [/usr/lib/python2.7/json/__init__.py|dump|189] [/usr/lib/python2.7/json/encoder.py|_iterencode|434] [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|408] [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|390]) ``` Let me know if you'd like the partial file sent over in private

kerem closed this issue

2026-02-25 23:39:41 +03:00

kerem commented

2026-02-25 23:39:41 +03:00

Author

Owner

@geek-at commented on GitHub (Nov 16, 2023):

very strange. this happened when you were sending an attachment? or is the error with the email itself?

@geek-at commented on GitHub (Nov 16, 2023): very strange. this happened when you were sending an attachment? or is the error with the email itself?

kerem commented

2026-02-25 23:39:41 +03:00

Author

Owner

@DasDunkel commented on GitHub (Nov 17, 2023):

They appear to be emails from Discord

@DasDunkel commented on GitHub (Nov 17, 2023): They appear to be emails from Discord

kerem commented

2026-02-25 23:39:41 +03:00

Author

Owner

@geek-at commented on GitHub (Nov 18, 2023):

I just pushed a new version with the env variable SHOW_LOGS if set to true will show the logs in the GUI. Can you try to reproduce and show me the mail log?

@geek-at commented on GitHub (Nov 18, 2023): I just pushed a new version with the env variable `SHOW_LOGS` if set to true will show the logs in the GUI. Can you try to reproduce and show me the mail log?

kerem commented

2026-02-25 23:39:41 +03:00

Author

Owner

@DasDunkel commented on GitHub (Nov 20, 2023):

Hi, ever since that update the emails have stopped, I'm not sure if it's because of a change in the update or if they've stopped being sent, I'll try rolling back to a previous release later today to see if the emails start again

@DasDunkel commented on GitHub (Nov 20, 2023): Hi, ever since that update the emails have stopped, I'm not sure if it's because of a change in the update or if they've stopped being sent, I'll try rolling back to a previous release later today to see if the emails start again

kerem commented

2026-02-25 23:39:41 +03:00

Author

Owner

@geek-at commented on GitHub (Nov 20, 2023):

you should be able to see in the logs if no emails came or if they were dropped or crashed

@geek-at commented on GitHub (Nov 20, 2023): you should be able to see in the logs if no emails came or if they were dropped or crashed

kerem commented

2026-02-25 23:39:41 +03:00

Author

Owner

@DasDunkel commented on GitHub (Nov 20, 2023):

That's the thing, the logs were empty except the startup stuff, even when I sent mail myself, and upon testing now I'm unable to send any mail to the server, the response being 500 Error: (TypeError) 'NoneType' object is not subscriptable

Edit; reverting to 1.0.2 resolves the above 500 error, so it's almost certainly a change in the latest version
It also appears like the emails have stopped completely, though I'll run the older version for a few hours to make sure

@DasDunkel commented on GitHub (Nov 20, 2023): That's the thing, the logs were empty except the startup stuff, even when I sent mail myself, and upon testing now I'm unable to send any mail to the server, the response being `500 Error: (TypeError) 'NoneType' object is not subscriptable` Edit; reverting to 1.0.2 resolves the above 500 error, so it's almost certainly a change in the latest version It also appears like the emails have stopped completely, though I'll run the older version for a few hours to make sure

kerem commented

2026-02-25 23:39:42 +03:00

Author

Owner

@geek-at commented on GitHub (Nov 21, 2023):

try again with 1.1.4

500 should be gone now

@geek-at commented on GitHub (Nov 21, 2023): try again with 1.1.4 500 should be gone now

kerem commented

2026-02-25 23:39:42 +03:00

Author

Owner

@DasDunkel commented on GitHub (Nov 22, 2023):

No more emails have been received regarding this issue regardless of which version is used, so I believe they are not being sent anymore.

I'll close this issue for the time being and continue running tests to see if I can cause the errors again.

@DasDunkel commented on GitHub (Nov 22, 2023): No more emails have been received regarding this issue regardless of which version is used, so I believe they are not being sent anymore. I'll close this issue for the time being and continue running tests to see if I can cause the errors again.

kerem referenced this issue

2026-02-25 23:39:53 +03:00

[PR #44] [MERGED] Fix where not using wildcard domains and discarding unknown domains #95