This is the chapter of the MemberManual that describes how to receive and manage your email.

TableOfContents

Introduction

HCoop offers a variety of ways to wrangle and access your email. Your email address is your login name, @hcoop.net.

Email sent to any of your HCoop-managed domains can be configured using Domtool. Please consult the [:DomTool/UserGuide:Domtool User Guide] for details on how to set that up.

We use the Maildir format (that is, a directory which contains files, each file containing exactly one message) rather than the mbox format (where all messages reside in one large mbox file).

By default, all email is delivered to your ~/Maildir directory. This directory is created for you when your account is created. So please do not delete the ~/Maildir directory if you value mail delivery and access.

Delivery

This section contains some topics relating to email delivery.

Quotas

The ~/Maildir directory resides on its own volume, and has a separate quota from the rest of your home directory.

Before copying over any existing email, be sure that you have enough disk space in your quota. Here's how:

fs listquota ~/Maildir

This will give you the name of your mail volume, available space (in MB), used space (in MB), the percentage of your volume used, and the percent of space used on AFS by all HCoop volumes.

If you need more space, please file a support request at [https://members2.hcoop.net/portal/support] in the AFS category. Be sure to nmention how much space you want.

Filtering

Both Exim filters and Procmail are available on the new systems. You can use either procmail or an Exim filter, but not both. Here are some considerations for deciding which one to use.

• If you are not familiar with procmail, and simply want to send mail to another email address, using an Exim filter will be best.
• If you want to exercise control over your email by splitting it into various IMAP folders based on custom criteria using the power of regexps, perhaps using procmail would be best.

• If you want to use a more readable syntax, which uses if ... then statements, then using an Exim filter instead of procmail will be more tolerable.

Please read the following subpages for specific information on each method.

• [:/EximFilter:Exim filter instructions]

• [:/Procmail:Procmail instructions]

Virtual mailboxes

Virtual mailboxes are a good way to give someone a "vanity address" on one of your domains, where they can receive and check email. See the [:/VirtualMail:Virtual Mail subpage] for full details on how to use them.

Dealing with spam

Spam is an inevitable fact of life. See the [:/SpamAssassin:SpamAssassin subpage] for details on using SpamAssassin, which is our preferred solution to the spam problem.

Access

This section explains how to access your email.

Webmail

HCoop has a webmail interface at [https://mail2.hcoop.net]. It allows you to access your email using a web browser.

IMAP

SSL IMAP is available via SSL at port 993, using hostname deleuze.hcoop.net.

STARTTLS IMAP is available on port 143, using hostname deleuze.hcoop.net.

POP3

POP3 access is available via SSL at port 995, using hostname deleuze.hcoop.net. If you're using Thunderbird, make sure to uncheck "Use secure authentication". Do not use port 110; it is not available.

Configuring email clients

Please consult the [:/Clients:email clients subpage] for examples of how to get IMAP and POP3 access working with various email clients.

Sending Mail

If you have a convincing reason for wanting to use our SMTP server to send messages to e-mail addresses for mailboxes that we don't host, then you can configure deleuze.hcoop.net as the outgoing SMTP server in your mail client. You must enable TLS SMTP auth, and you will need to authenticate with the same username and password that you use to get mail from POP3 or IMAP. Virtual mailbox names and passwords may be used here. The server will not query you for a username and password by default. Thus, you will get confusing error messages if you don't configure your client to attempt to authenticate with plaintext SMTP auth using TLS.

The SMTP server requires a TLS aware mail client. MacOS X Mail, Outlook and Opera do not seem to support this at the moment. Mozilla supports TLS and runs on MacOS X, Windows and Linux.

However, be sure to have a good reason to use our SMTP server in this way. If your computer never moves and your ISP provides an SMTP server (which most ISP's do), then you should definitely use that server instead of ours. SMTP servers are like public postal mailboxes in this way. There is rarely a reason to prefer one over another, so it generally makes sense to use the one physically closest to you.

You can also set up a SSH tunnel to port 25 on mail.hcoop.net, if your MUA can't/won't use TLS.

Reasons to do this

Here is a list of situations where it might be acceptable to use our server for sending email.

• The SMTP servers that some ISP's use today will rewrite the sender address, so that it is not possible for example to send mail as user@hcoop.net via those ISPs.

• You travel frequently and your ISP's SMTP server does not let you send email from some locations.

ISPs that block SMTP

Some ISPs and possibly other networks discriminate against the SMTP protocol. Some block or filter in or outgoing SMTP altogether.

If you need to send mail using HCOOP's mail server and experience long delays, this is likely due to your network. You can test out the mail server's responsiveness by doing "telnet deleuze.hcoop.net 25" on mire. If you immediately get a "220" banner, the server is working fine and you can type "QUIT".

To work around this issue, you can use mail80.hcoop.net as the server, and configure your email client to send mail through port 80.