[[users]] >> [[mail_setup]]
====== General ======
On this page you can find information on how to configure your local mail client to access mail from your SLUUG membership account on our mail server.
Using the new mail servers must be enabled by a system admin on a request basis until we have honed out the bugs. Once the system has become stable all users will be migrated.
Note to AT&T (SBC Global) customers: AT&T networks block smtp outbound connections (SMTP) to servers other than their own. This has been effective in eliminating spam bots from their networks. Output from the bots is silently dropped to outside servers making the bots useless for sending spam. This is probably going to become more wide spread among the major ISPs in the future. If you follow the instructions for using [[smtp_authentication]] you will be using port 465 which is allowed, as it typically requires name & password or public key authentication.
===== Supported Protocols =====
We now require Secure Pop3 or Secure IMAP. In addition we have SMTP Auth enabled via TLS to eliminate becoming a spam or virus relay. This also allows you to send mail to email addresses outside of SLUUG if you authenticate.
The choice of using POP or IMAP to retrieve mail is up to
your preference and the capabilities of your mail client.
Most mail clients will support both POP and IMAP, and
permit using them in secure encrypted mode.
**As of 07/02/2018, you must use the encrypted mode.**
===== Security =====
Unencrypted POP and IMAP are totally unsecure, so the new
email system will only use secure connections. The secure
versions are often referred to as POPS and IMAPS, and
are encrypted using SSL.
The first time your mail client makes a connection to
SLUUG's servers in secure mode, you should be prompted
to verify that the server is actually who it says it is.
This is done by the server providing you with a certificate
that you can compare against the same information
from a known reliable source. We have set up a
[[http://www.sluug.org/members/accounts/ssl_certificates.shtml|special
web page with certificate information]]. The main thing
to compare is the certificate fingerprint.
If the certificate doesn't match, there is a chance
that the connection has been intercepted by an imposter.
It is more likely that something has changed on SLUUG's
server, and we haven't updated the "reliable source".
If get get a mismatch, cancel the connection and contact
SLUUG for assistance.
=====Mail Server=====
General information needed to connect mail clients to our mail servers:
====IP Name and number====
Incoming and outgoing server
=== Old email configuration ===
**URL** : amber.sluug.org or mail.sluug.org
**IP** : 206.196.99.162
=== New email configuration ===
**URL** : mail.sluug.org
**IP** : 206.197.251.210
====Ports====
**SMTP** : 25 (Not for mail client use, use SMTPS. Relaying will fail)
**SMTPS** : 465 (SSL/TLS, normal password, username@domain required)
**POP3S** : 995 (SSL/TLS, normal password, username@domain required)
**IMAPS** : 993 (SSL/TLS, normal password, username@domain required)
====== Mail Clients ======
Below is information on how to configure your mail client for connecting to the SLUUG mail servers.
For all mail clients, the account name/user used must be of the form
user_name@sluug.org since this is how authentication is performed.
=====Elm=====
Be the first to update this!
=====Eudora=====
Be the first to update this!
===== Evolution =====
Be the first to update this!
=====Kmail=====
Be the first to update this!
=====Mutt=====
First, create a ''.muttrc'' file:
touch ~/.muttrc
chmod 600 ~/.muttrc
Then edit the ''.muttrc'' file to tell it to use IMAP.
# Set the start folder, as well as the location to save emails.
set spoolfile=imaps://user_name@sluug.org@sluug.org/Inbox
# Set the base folder.
set folder=imaps://user_name@sluug.org/Inbox
# Don't check mail as often as we would check local folders.
set mail_check=120
# Don't try to move read messages into spool folder.
unset move
Yes, that is ''@sluug.org@sluug.org''. The first is your login name,
which includes ''@sluug.org''. The second is the server you are connecting to.
On the old amber server, there wasn't the repeated ''@sluug.org''.
If you are using IMAP, you might want to enable header caching to improve performance. Set the header_cache variable in your muttrc to wherever you want, such as: set header_cache="~/.mutt/header_cache"
Now you can simply start [[Mutt]]:
mutt
==== Notes ====
The first time logging into the IMAP server, you'll need to hit A to accept the SSL certificate.
Use SHIFT-J and SHIFT-K to move up and down to select deleted messages, D and U to delete and undelete.
Use C to change folders. Use X or Q to quit. Hit ENTER to read a message.
You can add ''set imap_pass=my_imap_password'' to the ''.muttrc'' file to keep from having to type in the password every time you start up.
===== Pine=====
To access a mail account on sluug.org, change the inbox-path to: "{localhost/novalidate-cert/user=user_name}". /novalidate-cert allows the self-signed Cert for SASL to sluug.org, /user avoids the prompt for "LOGIN NAME".