Re: [Not yet solved] Modest send & receive problem
 

Confirming the working state! :D

Just one question to foobar/arcean: the deb size and also the lib sizes differ in the file posted above and the one from cssu-repo.
Any idea/explanation?
I took the one from official cssu repo.

For non-CSSU users: please do not try to install the cssu deb package, it may cause serious problems. If needed I may prepare a workaround like here.

--
but now I again need to reset all my accounts from
IMAP on STARTTLS [setting: Normal (TLS)] -which I just did- back to
IMAP on SSL/TLS [setting: SSL] :( :) :D

Re: [Not yet solved] Modest send & receive problem
 

Maybe thumb-related problem in scratchbox?
More about issue: http://maemo.org/community/maemo-use..._installation/

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Hello,

Just changed the title of the thread to "[SOLVED] Modest cannot receive/send via SSL/TLS" as suggested by peterleinchen.

But frankly I don't know how to get the fix.... I mean is it in the repos or will it be?

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

It depends!
Whether you are on CSSU or not.

If on CSSU then just grab this deb (or later versions) and download it to MyDocs. Then get root and execute following command:
Done.

If not on CSSU (but running stock PR1.3[.1]) then use the attached tar.gz, download to MyDocs and execute following commands (just like here):

All credits to foobar!

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Just some thoughts:

Since both SSL2 and SSL3 are insecure (if not obsolete) what would it take to disable them altogether. With the proposed fix it is made to work, but it leaves some questions.

For instance, if the provider offers both SSLv3 and TLS which one will be choosen. The first in the list or the best? Does it matter if it reads

#define SSL_FLAGS (CAMEL_TCP_STREAM_SSL_ENABLE_SSL2 | CAMEL_TCP_STREAM_SSL_ENABLE_SSL3 | CAMEL_TCP_STREAM_SSL_ENABLE_TLS)

or

#define SSL_FLAGS (CAMEL_TCP_STREAM_SSL_ENABLE_TLS | CAMEL_TCP_STREAM_SSL_ENABLE_SSL2 | CAMEL_TCP_STREAM_SSL_ENABLE_SSL3)

??

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

The best will be chosen if things are not completely fubar'd inside NSS (the crypto lib tinymail uses).

The order in the #define doesn't matter.
Disabling SSL3 now would lock a lot of people out of their mail servers again, so while it would be beneficial from a security point of view, it would not help with the problem at hand. :)

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

See also:

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Don't they teach math at school anymore?
Repeat after me: addition is commutative! :)

-- add.
As @peterleinchen rightly pointed out, ORing is not really ADDing (that would be XORing). However for cases where the things being added do not overlap (in the binary sense of the word), ORing is, for all purposes, the same as ADDing.

So for the sake of completeness:
Repeat after me: disjunction is commutative! :)

(I know, it sounds much much worse.)

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

I'm using CSSU but not the devel repository. So I do not have libglib2.0-0 (>= 2.24.0). And I do not want to install the files manually via tar.gz.

Because the files in the tar.gz by peterleinchen are the same as in the CSSU devel package, I simply modified the deb to depend on libglib2.0-0 (>= 2.20.0). For me it works.

I cannot add the modified deb here because I am not allowed to attach files > 488 kB. And the deb is > 600 kB.

I uploaded it there:
http://packages.der-he.de/austausch/...ssu7_armel.deb

It should work for all CSSU and PR1.3(.1) users.

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Just for restoring my reputation:
I know those rules already and I know how to apply them ;)

A computer might implement checking the conditions in a different way though.
It might check all conditions for truth and state the result afterwards.
Or it might be implemented to do something like an IF-ELSEIF-ELSE chain would do, meaning if it hits first it sticks to it. Why should a computer test more than one condition if the "true"-outcome has already been reached?

I have seen such implementations before. This of course saves CPU cycles noticably only for large numbers of repetitions. It all depends on the implementation of the checking routine.

And this I have learned AFTER school in university lectures about algorithms and data structures ;))

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Would be easier if the fix were in the repos; just an apt-get install and it is set.

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Amboss, you are confusing | and ||. The former is an arithmetic operator, the latter a logical one. The C and C++ Standards define the behaviour of both. In a nutshell, | works a bit like +, although not quite. 1 | 2 = 3, but 2 | 3 = 3, not 5. The important thing is that a | b = b | a. Also important is that to evaluate the result of a | b, both a and b must be evaluated first. You can figure it out yourself: to work out a | b, it is not enough to know that a is 2, you also need to know if b is 1, 2 or 5. That's because 2 | 1, 2 | 2 and 2 | 5 yield different results (3, 2 and 7, respectively).

|| uses the shortcut mechansm you describe. That's because it works with logic values and results in TRUE or FALSE. You know that if a is TRUE, no value of b will change the result of a || b, so b does not need to be evaluated. Note that this shortcut mechanism makes no difference to the value of a || b, but it does make a difference if evaluating b has a side effect. That can happen if b is an expression with some kind of assignment in it (=, +=, -=, ++, --), or if b is a function call with side effects. The programmer must be aware of this and make sure to write the code so that it behaves predictably.

Finally, in the example in question, the value of a | b is evaluated at compile time and the final code will see only a single number that is the result of that evaluation. It will not compute it at run time. The question why it is like that is left as an exercise.

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Any news on Modest making its way into the repos?

I'm so glad I found this thread, I was worried about how useful the N900 would be to me without an IMAP client that can do TLS.

I run my own Postfix+Dovecot email server, so I could re-enable SSLv3 but I'd really rather not for security reasons. I've just (in the last day or two) started using the N900, flashed PR1.3 and installed CSSU stable. Do I need to be using testing to get this new version from the repo?

Sorry if these are dumb questions, Maemo is still new to me.

Sam

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

It seems modest (libtiny-mail libs) have not yet made it into testing branch (A shame; why? They should be in stable imho.).
So you would need to enable cssu-devel repo and update those libraries described in this thread (but only those) and disable that repo immediately.

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

It worked!!

For the record, I ran:

Then disabled the repo and did an apt-get update again to be safe (although I think the GUI tool does this anyway).

Here's part of the header from the first email I sent from my n900:

Many thanks to all of you. I think it's great that we were able to do this. This is what free software is all about, right? Power to the users!

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Are you using gmail?
But anyway you should also update libtinymail-tiny... from cssu devel.

See here http://talk.maemo.org/showthread.php...&postcount=130 or http://talk.maemo.org/showpost.php?p...&postcount=149

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Me? Nope i run postfix/dovecot on an ubuntu server at home. The test message was sent from my server to a freemail outlook account.

I'll look into updating that library, thanks again!

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

hmm, i can't find that library...

Sam

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

libtinymail-1.0-0

see my edit above
second link: http://talk.maemo.org/showpost.php?p...&postcount=149

--edit
Should not be needed according to
http://talk.maemo.org/showthread.php...05&postcount=1

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

My imap stopped working. I am on CSSU testing. After I downloaded this version of tinymail

http://maemo.merlin1991.at/cssu/comm...ssu7_armel.deb

and then according to given instructions installed it using (the file located in my sdcard, change the location to where you downloaded yours)

dpkg -i /media/mmc1/http://maemo.merlin1991.at/cssu/community-devel/pool/free/t/tinymail/libtinymail-camel-1.0-0_1.1.92%2b1cssu7_armel.deb*

with the asterix * in the end and then as root

killall modest

my mail started to receive mails again. I have installed that some needed package mentioned in this thread lib something and I have cssu devel repository enabled when I installed this.

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

I am pretty sure you read not only the first post but also some statements when this repository
https://talk.maemo.org/showthread.ph...eat+your+brain
should be enabled only?

For enabling SSL in mails there are only a few manual packages to be installed from devel.
Do not have cssu devel repo enabled...

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Yes I have heard it should not be enabled. I have done an upgrade with cssu devel repo. First time there were just two thinga which caused problems (I mentioned them in my "Devel upgrades" thread) and they were easy to fix. Tried the same last week with fresh flashed N900 and made it not to boot anymore. Felt a bit sad. Flashed again (5x in 24h cause was messing around with trial and error) and did not make cssu devel upgrade, only with Extras devel I think.

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Congratulations!

On a side note:
The asterisk is meaningless in this instance.

Re: [SOLVED] Modest cannot receive/send via SSL/TLS
 

Nice! Good to see I was not far off :rolleyes: