IMAP

I have Messenger Pro 8.05, but can’t find where to enable IMAP. I have tried Server Choices in Messenger Choices, but IMAP isn’t mentioned. I also tried Site Details and various other places with no luck. According to the Help manual, you need !MsgServeS which I have in !Messenger.Servers. If I go to add a new emailbox in Hermes accounts, a new POP account is offered.

Answering my own post, it seems according to the help manual that you can only get IMAP if it’s chosen at the installation stage. The problem is that I have several email addresses and need some to have IMAP and others POP. Is that possible?

I have Messenger Pro 9.00
The main difference between imap and pop is that the first leaves messages on the server and the other deletes them.
Messenger allows in choices edit POP account to choose this method with the fetching option: “Remove mail from server after fetching”
I use two accounts each with one of these possibilities, no problem.
I hope I answered your question and that this choice is possible with version 8.05

Some of my email addresses are now with a new email provider whose server for my incoming email (fetch) needs IMAP, not POP.

By the way, where did you get V9.00 of Messenger Pro?

David , who is your new email provider?

Messenegr Pro v9.01 is available via PlingStore or direct from R-Comp, as you have an older version there is a chargeable upgrade.

You can change between “offline” email (POP) and IMAP via the “User login” window.

To get the Login window, either right-click on User button on the main toolbar, or left click “Login…” on the iconbar menu.

v9 made switching between offline and IMAP modes smoother, but because of the different ways of working, you do need to switch back ends to do IMAP. Fortunately, that’s merely a case of clicking on the option in the Login window.

The difference is that in IMAP, your data is stored entirely on your ISPs servers (and may therefore have limits imposed – check with your supplier) whereas POP fetches are stored on your local machine so you have a little more control. There are pros/cons to each method, and certainly IMAP is preferable if you have multiple devices, but means everything is going over a network connection, which will be slower than local mail handling.

Please note that there are tips in the Tips folder supplied with Messenger Pro – they may help. Setting IMAP up for the first time is the trickiest bit. Whilst it isn’t difficult per-se, it is an area of Messenger that I’d like to be friendlier. Hopefully the tips help.

The other big piece of advice I would give is to load (without Mpro running) the IMAP client to the iconbar first – Shift double click !Messenger and go to Servers then run !RemoteNB. This gives it its own iconbar icon and menu, making access to the setup screens much easier whilst you’re getting it configured. Once you have it all working, then Mpro will handle RemoteNB in the background, so you don’t need to worry about it, but having the iconbar icon to interact with initially can be a lot less frustrating.

Most mail clients on other platforms mirror some or all messages locally; you get to choose how far back. When you first set them up they download these in the background.

I have gone through the configuration, but get an error when I try to login as a user on my computer. To be clear, this is not the remote login on my provider’s servers, but the very first step in using Messenger Pro. I get the “Message from Messenger”: Messenger is still in the process of logging you in. Please wait a moment and try again. Then clicking on “Continue”, another “Message from Messenger” saying “Connection to NNTP server failed (Error 65)”. Could it be that the entered user’s password is wrong? But I can’t see where this is set in the configuration, only the password for my email on my provider’s servers.

NNTP is newsgroups. Did you add something into the NNTP field?

Yes, nntp.aioe.org; but I have since deleted it and left the field blank thinking that it could be causing the problem. The problem remains.

Under Server Settings window, I have the ports added for my IMAP and SMTP connection.

imap.myprovider.com:993 / Activate SSL/TLS on connection
smtp.myprovider.com:465 / Activate SSL/TLS on connection

Do you have something similar?

For both IMAP and SMTP server names I have mail.mail.coop . For SSL/TLS I have Require SSL/TLS. The server names are as given by the supplier, and the security SSL/TLS setting just seemed appropriate as mail.coop say they use SSL. I thought I had set the port numbers somewhere as 993 for IMAP and 465 for SMTP, but now can’t find them except port 465 in !Hermes.Choices.Accounts in one of the send accounts. So I should try adding a colon and port number after the server names?

I looked at their website.

try mail.mail.coop:963 for the IMAP server and mail.mail.coop:465 for SMTP and set them to Activate SSL/TLS on connection

I have tried adding the port numbers 993 (not 963) and 465 with a colon and the “Activate SSL/TLS on connection option”, but get the same error “Messenger is still in the process of logging you in…..”.
I got another error message after first loading NetFetch and Messenger and then !RemoteNB: Support for multiple message servers is not present in this release. I don’t get this if I load RemoteNB first. What version of Messenger Pro do you have?

Using the wrong port number is not a recipe for success.

Using the wrong port number is not a recipe for success.

Especially so when the port you’re trying is definitely not open for connections. Open ports associated with mail on that server are (marked with arrows):

Nmap scan report for mail.mail.coop (81.95.52.73)
Host is up (0.016s latency).
Not shown: 89 closed tcp ports (reset)
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
110/tcp open pop3 <===

111/tcp open rpcbind
143/tcp open imap <===

443/tcp open https
465/tcp open smtps <===

587/tcp open submission
993/tcp open imaps <===

995/tcp open pop3s <===

I can’t even login as a user, the very first step.

Interesting as they list 963 on their website as the IMAP port.

“Incoming mail server (also known as IMAP server): mail.mail.coop
Port number: 993
Security: SSL
Authentication is by password sent in plain text. You might see a checkbox option to enable encrypted or secure password authentication (SPA), but you should leave this unchecked.

Outgoing mail server (also known as SMTP server): mail.mail.coop
Port number: 465
Security: SSL
Authentication is by password sent in plain text. You might see a checkbox option to enable encrypted or secure password authentication (SPA), but you should leave this unchecked."

Interesting as they list 963 on their website as the IMAP port.

Citation needed, because the thing you’ve quoted (which appears to be from here) says 993.

Authentication is by password sent in plain text.

Hmmm, the password is sent in the same manner as the messages themselves, and this should be happening within the encrypted session, so it’s not quite as plain text as plain text usually implies.

SPA is some proprietary Microsoft thing, IIRC.

The description seems to fit STARTTLS.

STARTTLS usually runs on the normal plaintext ports (to ask to upgrade to encrypted), and it is supposed to happen before any credentials are exchanged.

465/993 are the encrypted versions of protocols, so going straight into an encrypted session there is expected, it doesn’t need to be requested.

I have altered some parts of the configuration in RemoteNB and MsgServe, and now get a new error message from Messenger: Connection to IMAP server failed (SSL negotiation failed). The remoteNB application described as IMAP + NNTP Interface which helps set up the configuration doesn’t ask for port numbers. I did try adding these to the names of the IMAP and SMTP servers (see above), but this didn’t help. The options that the Messenger manual gives for the security settings of each of the two servers are: Never use SSL/TLS, Use SSL/TLS when available, Require SSL/TLS and Activate SSL/TLS on connection. I have tried all of these except the first one.

Thanks to Steve Pampling, I am successfully using POP3s on PORT 995 for sending emails.

I have another sending problem due to having several email accounts, but this should be in a new thread. A clue is that I get the error message for some, not all, sends
“5.7.1 <X@Y>: Sender address rejected: not owned by user W@Z”.