|
2020-01-22
, 21:28
|
|
Posts: 868 |
Thanked: 2,516 times |
Joined on Feb 2012
@ Germany
|
#2
|
There are some DBUS methods available for debugging.
run-standalone.sh dbus-send --print-reply --dest=com.nokia.modest /com/nokia/modest com.nokia.modest.DumpOperationQueue
(instead of DumpOperationQueue, you can also use DumpSendQueues or
DumpAccounts)
These methods will print a list of the current mail operation queue,
send queues or the accounts. If you don't know what that means, then
this problably not for you
"showui"
To actually start with the UI, you have to provide the 'showui' parameter to
modest. Reason for this not being the default is to allow for DBUS-activation
of various services without showing the UI.
"MODEST_DEBUG"
The MODEST_DEBUG environment may contain any number of ':'-separated strings
to trigger certain debugging features:
"abort-on-warning"
Abort the program when any Gtk/Glib warning or error occurs. This can be useful when running inside a debugger.
"debug-code"
Run various pieces of debug-only code in modest
"log-actions"
Log actions to the log file (not available yet)
"debug-objects"
Debug GObject usage (G_TYPE_DEBUG_OBJECTS)
"debug-signals"
Debug GSignal usage (G_TYPE_DEBUG_SIGNALS)
"factory-settings"
Return all the user-settings to the 'factory defaults'
The Following 7 Users Say Thank You to Halftux For This Useful Post: | ||
|
2020-01-23
, 07:09
|
|
Posts: 584 |
Thanked: 1,550 times |
Joined on Sep 2019
|
#3
|
The Following User Says Thank You to nonsuch For This Useful Post: | ||
|
2020-01-23
, 13:39
|
|
Posts: 868 |
Thanked: 2,516 times |
Joined on Feb 2012
@ Germany
|
#4
|
|
2020-01-24
, 08:03
|
|
Posts: 584 |
Thanked: 1,550 times |
Joined on Sep 2019
|
#5
|
Modest uses the microb-engine and the microb-engine uses libnss3.
You could try install modest, microb-engine, libnss3, libnss3-certs, and maybe other packages from cssu-devel.
The Following User Says Thank You to nonsuch For This Useful Post: | ||
|
2020-01-24
, 11:36
|
|
Posts: 868 |
Thanked: 2,516 times |
Joined on Feb 2012
@ Germany
|
#6
|
Sorry to be obnoxious about it, but do you have reason to think this will give me something, like the ability to use a fully SSL or TLS encrypted connection?
|
2020-01-24
, 19:53
|
|
Posts: 584 |
Thanked: 1,550 times |
Joined on Sep 2019
|
#7
|
Sorry I can't tell you but the chance that it will work is very low. It is something what I would try.
Better would be to work on leste to make it useable, instead of working with the nearly dead maemo5. So when you working with qmf it could be also useful for leste, because the mer-core also has qmf which is used by sailfish os.
The Following User Says Thank You to nonsuch For This Useful Post: | ||
After some fiddling I managed to get the connection work like this:
- Incoming mail server (IMAP) with TLS using port 143
- Outgoing mail server (SMTP) with TLS using port 587
According to my mail provider this means that the connection is actually STARTTLS and not TLS/SSL because of the ports I'm using.
Using the ports for full TLS/SSL encryption I get errors, it does not work with either TLS or SSL setting in Modest's account preferences.
I wonder what that means. Why can it start unencrypted and then switch to an encrypted connection, but can not start an encrypted connection straight away? This is how my desktop clients are set up for the same provider.
I can see on the linked page that "The connection to Posteo is always encrypted (STARTTLS, TLS or SSL)" but it makes me wonder nevertheless.
Can I check this somehow? Full error messages?
Does Modest have settings/config/log files somewhere?
Could not 'find' anything.
On a side note, is there another good mail client?