Yam on AmigaOS 4.1 Final edition

[Shamron]

I am with virgin but still use my blueyonder account and I use imap not pop3?

You use imap with YAM?

This is what i want, since i DO want to check mail on my X1000, but until the day comes that i can rely on my Amiga for EVERYTHING, i still use my pc, tablet, etc as main mail checking platforms and i don't want the mail marked as read or no longer new or worst case, deleted because i opened it on my Amiga.

I've disabled the "delete mail on server" option in YAM.. but only got it working with pop.

please post how to use imap if i understood you right. :-)

[Shamron]

Yam still doesn't support imap4: https://github.com/jens-maus/yam/issues/37

Ok, thanks. :-)

Anyways, i'm trying to configure YAM 2.9p1 using pop/smtp with gmail and i've tried this so far with no luck.

smtp.gmail.com
ssl/tls port 465 (also tried starttls and port 587)
plain pass (also tried login and auto)
server accepts 8 bit characters

pop.gmail.com
ssl/tls port 995
plain pass

i've selected "accept less secure clients" in google mail.

The thing is, i used YAM 2.9p1 on OS4.1 on my Sam460ex a year or so ago without issues, following a guide on how to set up YAM with gmail, but now, when i try to install and configure YAM om my X1000 with OS4.1FE, i can't get it working.

I've downloaded and installed AmiSSL 1.1, 2.2 and 3.6. I also use amicloudhandlers (dropbox and googledrive which needs the assign sslroot which was set to sys:devs/cloud/.sslroot

I put a ; in front of that line in network-startup and set sslroot to sys:devs/amissl instead, just to see if that helped.

Do i need to add some services to prefs/internet/services?

[Shamron]

Ok, so i downloaded YAM 2.10dev and replaced the binary.

I also disabled the tooltypes user and pass, and the check for new mails at startup. The only tootlype i enabled, was debug.

For some weird reason, it works now, but using 2.10 means it will only work until a specific date....

Since i got this working, should i also be able to get 2.9p1 working?

[Shamron]

Oh well..

So i got YAM to work, but somewhere along the line i must have screwed up my AmiSSL setting/configuration...

I downloaded bot 1.1, 2.2, and 3.6(68k) and as the readme said, i need all of them, but somewhere in the middle of all my googling, i read that maybe the order of which you install them might be important? Also that the most important is the AmiSSLMaster.library (or something).

I can't any longer log in to a secure site i regularly log in to... and when i checked Odysseys "Messages", there was a bad cookie, so i checked it and it expired in 1970...

What's going on? I have messed a bit with input/locale prefs switching betwern ISO-8859-15 (Norwegian WITH the "%&$#?@!%&$#?@!%&$#?@!8364;" symbol) and ISO-8859-1 (Norwegian without it).

I tried 3 different installs of Odyssey 1.23r4 (just renaming old folder to -old and trying the new one).

Anyone able to help? :-P

[Shamron]

AmiSSL is, as far as I know, outdated and does not support encryption currently in use.

Just a few days ago, i was able to use Odyssey both when signing in to DNB (Norwegian bank using bank-id through a small authenticator) and when logging in to NAV and Digipost (also uses the same authentication)

Now i get javascript and cookie error. The js error is something "deflected.xss" and the cookie and auth ssl key is for another domain. Also when opening the cookies window in Odyssey, and search for the cookie, ALL the cookies under that domain three says they expire 1. jan 01:59.:59 1970

A friend of mine, very into Linux and Debian, responded very sceptic to the .xss warning, saying he would have turned off the computer and not entered any more passwords or personal information.

Anyways...

Odyssey worked both in DNB, NAV and Digipost WITH bankid (electronic authenticator) before i upgraded to 1.23r4, BUT... NOW it works with youtube and google services...

Weird :-)