Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: atom-ant on February 28, 2015, 12:05:30 PM
-
Can someone help as I am having a lot of touble with yam 2.9 to set it up for e-mails. I have tried lots of settings but still no joy so could one of your kind poeple give me a step by step guide how to do this as it taken me over 2 days and still can not get it right.
Thanks
-
What exactly are you having problems with?
I've always found YAM as easy to setup as any other email client, albeit it being outdated compared to the mainstream OS's email clients.
It never gave me any difficulties installing nor on setup, assuming a person knows the proper server info to input into it, like any other email client requires.
-
hello
Ive open YAM says cheaking mails @virginmedia.com than a error message 'coudn't connect to host virginmedia.com of acccount fred@virginmedia.com. The mail server did'nt respond within the predefined time frame and therefore timed out the setting as tcp/ip settings Desciprion- fred@virginmedia.com. server/port virginmedia.com. conn security SSL/TLS.Authen Plain Password User Name fred Password ******** I have put in pop3viginmedia and smtp virginmedia and tried every other setting and I still can not get it too work
-
Do you have AmiSSL installed? Iirc you need all three versions installed.
http://www.heightanxiety.com/AmiSSL/
-
@Danwood
For reference, I use YAM with AmiSSL 3.6 (25.2.2006) and OpenSSL 1.1 (24.6.2005) installed both in the same directory, to which the AmiSSL: assign is pointed (albeit not on OS4.1FE).
@atom-ant
Is pop3 access enabled on your account? (http://help.virginmedia.com/system/selfservice.controller?CMD=VIEW_ARTICLE&ARTICLE_ID=2720&CURRENT_CMD=SEARCH&CONFIGURATION=1001&PARTITION_ID=1&USERTYPE=1&LANGUAGE=en&COUNTY=us&VM_CUSTOMER_TYPE=Cable)Apparently pop3 access can be disabled with virginmedia accounts, although should be enabled by default.
General virginmedia settings (http://help.virginmedia.com/system/selfservice.controller?CMD=VIEW_ARTICLE&ARTICLE_ID=2708&CURRENT_CMD=SEARCH&CONFIGURATION=1001&PARTITION_ID=1&USERTYPE=1&LANGUAGE=en&COUNTY=us&VM_CUSTOMER_TYPE=Cable) look OK from what you posted.
-
I have set yam up but all I get is Could'nt intialise TLSv1/SSLv3 sssion with host 'pop3.virginmedia.com' of account fred@virginmedia.com. I have tried everthing and stiil no joy.
-
Never post personal info like that online. Bad form.
-
I have set yam up but all I get is Could'nt intialise TLSv1/SSLv3 sssion with host 'pop3.virginmedia.com' of account fred@virginmedia.com. I have tried everthing and stiil no joy.
MY virginmedia.com account (which I don't use but does work in YAM) is set up as follows:
Server/port: pop3.virginmedia.com 995
Connection security: SSL/TLS
Authenification (sic): Plain password
Username: yourusername@virginmedia.com
Password: ********
That;s all you need, except as said you have to enable POP on the email account (through webmail).
-
I have set yam up but all I get is Could'nt intialise TLSv1/SSLv3 sssion with host 'pop3.virginmedia.com' of account fred@virginmedia.com. I have tried everthing and stiil no joy.
I am with virgin but still use my blueyonder account and I use imap not pop3?
-
Hi, sometimes the ssl problem is at V.M's end, try changing the connection security setting to "no security" Click "use" rather than "save", this will at least confirm that your user name and password are valid from V.M's perspective.
P.S. your settings look the same as mine.
Draby
-
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. :-)
-
You use imap with YAM?
.....
please post how to use imap if i understood you right. :-)
Yam still doesn't support imap4: https://github.com/jens-maus/yam/issues/37
-
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?
-
YAM 2.9p1 stopped working with my mail provider for no apparent reason, and from this thread it looks like it's stopped working with a lot of mail providers. In my case, my provider changed something on the server end and YAM doesn't like it.
The YAM nightly build worked for me, but those have expiration dates and I haven't tried to keep up to date. I'm hopeful that the next formal release will have this issue fixed.
-
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?
-
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.
I don't think you had to do all that - just replacing the binary should have done it.
For some weird reason, it works now, but using 2.10 means it will only work until a specific date....
Right. I've stopped trying to do email with YAM until the formal release of 2.10 happens.
Since i got this working, should i also be able to get 2.9p1 working?
No, YAM 2.9p1 is apparently incompatible with whatever global change has been made to email servers.
-
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
-
AmiSSL is, as far as I know, outdated and does not support encryption currently in use.
-
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 :-)