In Dec 2016, we added required password rules for new Connect IN Email accounts and password resets. At that time, however, we did not force users to change their existing passwords.
As part of a Security Audit of Connect IN services, we now ask that those who have not changed their Connect IN Email password since before Dec 2016 to please do so before February 1, 2018.
Any Connect IN Email accounts with passwords that have not been changed since before Dec 2016 will lose access on Feb 1, 2018, requiring your Email Administrator to change the password in order to regain access.
To change your Connect IN Email password, please visit the following site:
Thank you for your assistance in keeping Connect IN secure.
Given that Connect IN is run on free software, some additional steps are needed for certain password resets. We ask that libraries using Connect IN keep the following in mind.
Password resets for a Connect IN Email address are to be handled by the appropriate Library’s designated contact for Connect IN, via the Connect IN Email Administration console. In the event that the designated contact cannot access the Administration console, new passwords to the console will only be provided over the phone after a verification process.
Password resets for the Connect IN Web service are initially only allowed to be sent to existing Connect IN Email addresses. In order to allow other email addresses to receive password reset requests, a plugin (such as WP Mail SMTP) must be installed and configured with an existing email account.
Since Connect IN hosts a large number of sites, it receives a significant number of attacks against it. In order to mitigate these, we are continuously revising our security measures to prevent new methods of attack.
If a Connect IN site seems no longer to respond, it is possible that a security measure has been triggered. (A common method of doing this is to continually guess a password within a short time frame.) Thus, if this occurs, please provide your public IP address, obtainable through a site such as whatismyip.com, to the Connect IN Helpdesk, and we will work to solve the issue for you.
Maintaining secure sites is an ongoing process, and we thank you for working with us towards providing better security for all who use Connect IN.
Both Connect IN Web and Mail will be undergoing hardware maintenance on Friday, February 10, 2017, at 8pm EST, during which Web and Mail services will be inaccessible. We apologize for any inconvenience this may cause, but we hope to have service restored as quickly as possible.
Spam can be a problem for any email system as spam and/or phishing attacks attempt to find new ways to trick people into clicking their links or opening an attachment. Connect IN uses multiple methods to prevent spam, but these methods may not always be successful.
The best practice for handling spam while using Connect IN is to keep spam in the Spam folder while keeping any non-spam out of the Spam folder. Keep in mind it is still possible some false positives may occur. Checking the Spam folder regularly to remove any false positives should correct this. By following these guidelines, the system should correctly learn what is and is not spam.
It has been discovered that a recent automatic security update caused an issue where mail was unable to be sent between 7am and 10am on Wednesday, May 25, 2016. Only attempting to send mail during this time was affected.
If you experience a problem using webmail, please inform the Helpdesk.
Also, please keep in mind that Connect IN currently limits the size of attachments to 5 megabytes and the size of mail accounts to 5 gigabytes.
Connect IN Webmail was updated between 9pm and 10pm on March 9, 2016. The new version of the software has slight cosmetic changes, but functionality should remain mostly the same.
Please keep in mind that viewing attached Office files will now upload the file to live.com (Microsoft) to display them.
Should there be any issues with using the new update, please contact the Helpdesk.
Now that Let’s Encrypt (letsencrypt.org) is available, Connect IN supports HTTPS (secure) connections! Also, for your protection, all Connect IN logins are now forced to use these secure connections. For best use of HTTPS (receiving the green “https” lock icon in Chrome), all images linked on a page should also be linked via HTTPS. This proves that the image was not changed somewhere between its original location and the browser viewing it.
Let’s Encrypt also stops the need to accept the previously self-signed certificate when configuring Connect IN Mail for iPhone or Outlook, as long as the server is set to mail.connect.lib.in.us.
As Connect IN is a free service, we currently use self-signed certificates for our encrypted (SSL) connections.
For those using Connect IN Mail with a mail application (such as the iPhone’s Mail app or either phone or desktop versions of Outlook), the SSL certificate was recently updated. This means that, for those using SSL, you will be required to accept the certificate again for each application in order to send/receive mail.
The current certificate is set to last for two years.
This does not affect Connect IN Webmail users.
As of 8pm, June 1, 2014, we made some internal changes to the Connect IN services to provide better long-term reliability and security. One of these changes was a new domain name along with new IP address. To further reflect changing from the AccessPoint service to Connect IN, the support blog (and alternative webmail sites) can now be found at connect.lib.in.us. If you experience any issues that might be due to this transition, please contact the Connect IN Helpdesk.
Update: There may be an issue where Outlook and iPhone users’ settings might not be working properly. The settings can be changed to reflect the new domain as shown in Configuring Your Mail Client. If SSL is used, the new certificate may need to be accepted before being able to send or receive email.