WARN ENiGMA½: Error exporting message: Object does not exist: No NetMail route for 2:11/211
Looking at the previous log entry, I can see that it happens during scheduled exports:
INFO ENiGMA½: Performing scheduled message scan/export... (module="FTN BSO")
Taking a look at the code, the system is logging from getNetMailRouteInfoFromAddress(), which is called from exportNetMailMessagesToUplinks(). Essentially what happens is an “external” (i.e.: to be exported) message fails to export, logs, then nothing else happens. The NetMail remains to eat up space and log the next time around.
But which message is this? Unfortunately, the current log doesn’t tell us. 🥲
Time to do a little digging…
Since I don’t (yet) know much about the the message causing this, time to gather some info. ENiGMA marks a few metadata values about external messages. A FTN destined NetMail will have a
remote_to_user value. In this case, set to
2:11/211. I’m only seeing a single log, so there should hopefully be one match. For this I’ll use sqlite-utils and jq:
> sqlite-utils query db/message.sqlite3 'select * from message_meta where meta_name="remote_to_user" and meta_value="2:11/211"' | jq
Awesome, there it is: A single message with the ID of
544380. This has been happening for a while, and I don’t in fact, have a route to this destination address, so I’ll just delete the message. But first, I want to gather a bit of info about it so I can let the user know their message never sent. For this, I’ll use the tools above again:
> sqlite-utils query ./db/message.sqlite3 'select * from message where message_id=544380' | jq
Finally, rid of the bugger:
> sqlite3 db/message.sqlite3 'delete from message where message_id=544380'
For the future, look to Unroutable NetMail persists forever on the issue tracker :)