welcome: please sign in

Diff for "MemberManual/Email/VirtualMail"

Differences between revisions 1 and 12 (spanning 11 versions)
Revision 1 as of 2007-11-01 20:31:10
Size: 2013
Editor: MichaelOlson
Comment: Flesh out
Revision 12 as of 2007-12-27 20:16:29
Size: 3263
Editor: DavorOcelic
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from MemberManual/VirtualMail
Line 7: Line 8:
== Introduction == = Introduction =
Line 9: Line 10:
Virtual mailboxes are a good way to give someone a "vanity address" on one of your domains, where they can receive and check email. You may create virtual e-mail boxes for any domains for which you have write permission in DomainTool. Virtual mailboxes are a good way to give someone a "vanity address" on one of your domains, where they can receive and check email. You may create virtual e-mail boxes for any domains for which you have write permission in DomTool.
Line 13: Line 14:
== Administration == It is also very important that your "daemon" user gets write privileges on the directory that is used to store mail for each vmail username.
Line 15: Line 16:
We use a custom program called `vmail` to manage delivery to virtual mailboxes. It may be invoked with '''`vmail $DOMAIN $COMMAND`''', which indicates that you are configuring the virtual mailboxes for domain '''`$DOMAIN`''' for which you have DomTool permissions. The valid commands are: = Complete example =
Line 17: Line 18:
 * `list`: Print the mapping from usernames to mailbox directories for `$DOMAIN`.
 * `add $USER $MAILBOX`: Add a mapping from `$USER@$DOMAIN` to a Maildir directory `$MAILBOX`. You'll be prompted to enter a password for the user, which he can then use to access IMAP, POP, or restricted SMTP services.
 * `passwd $USER`: Reset a virtual user's password.
 * `rm $USER`: Remove a mapping. The mailbox directory remains for you to deal with as you like.
To be able to receive email for the new virtual user, you need to create their Maildir directory, set the correct permissions on it, and
then create the actual virtual mailbox.
Line 22: Line 21:
== Access == In the example below, replace
'''$USER''' with your username, '''$VUSER''' with virtual user name, '''$DOMAIN''' with your domain, and '''$MAILDIR''' with the directory
where the virtual user's email is to be stored.
Line 24: Line 25:
People with virtual mailboxes may use the normal services for accessing their email, such as SSL IMAP and POP, and the [http://mail2.hcoop.net] web interface. {{{
maildirmake $MAILDIR
fsr setacl $MAILDIR $USER.daemon write
vmail $DOMAIN add $VUSER $MAILDIR
# Enter a password as prompted.
vmail $DOMAIN list
# You will see that the new account shows up.
}}}
Line 26: Line 34:
== Changing password == = Administration =
Line 28: Line 36:
People with virtual mailboxes may change their password using the handy web interface at [https://members2.hcoop.net/passwd]. We use a custom program called `vmail` to manage delivery to virtual mailboxes. It may be invoked with '''vmail $DOMAIN $COMMAND''', which indicates that you are configuring the virtual mailboxes for domain '''$DOMAIN''' for which you have DomTool permissions. The valid commands are:

 * '''list''': Print the mapping from usernames to mailbox directories for `$DOMAIN`.
 * '''add $USER $MAILDIR''': Add a mapping from `$USER@$DOMAIN` to a Maildir directory `$MAILDIR`. You'll be prompted to enter a password for the user, which he can then use to access IMAP, POP, or restricted SMTP services.
 * '''passwd $USER''': Reset a virtual user's password.
 * '''rm $USER''': Remove a mapping. The mailbox directory remains for you to deal with as you like.


Note: If you try to log in to the web interface this will fail because the mail directory has not been initialized yet. Send a test message to the new account, then verify that the $MAILDIR directory now has some files and directories, then try to access the account from the web interface.

= Access =

People with virtual mailboxes may use the normal services for accessing their email, such as SSL IMAP and POP, and the [https://mail2.hcoop.net] web interface. They authenticate giving their full e-mail addresses as usernames, in contrast to the situation for normal UNIX users.

= Changing password =

People with virtual mailboxes may change their password using the handy web interface at [https://members.hcoop.net/passwd].

This page describes how to use virtual mailboxes.

TableOfContents

Introduction

Virtual mailboxes are a good way to give someone a "vanity address" on one of your domains, where they can receive and check email. You may create virtual e-mail boxes for any domains for which you have write permission in DomTool.

Before continuing, please note that DomTool allows you to create aliases that forward mail from one address to another. Aliases are much preferable to extra mailboxes, both in terms of conserving server resources and convenience for you, as you can continue checking one mail account even if multiple aliases point to it. The basic rule is: If you are creating a virtual mailbox that only you will read, or if you are creating multiple virtual mailboxes to be read by the same other person, then you should be using aliases instead.

It is also very important that your "daemon" user gets write privileges on the directory that is used to store mail for each vmail username.

Complete example

To be able to receive email for the new virtual user, you need to create their Maildir directory, set the correct permissions on it, and then create the actual virtual mailbox.

In the example below, replace $USER with your username, $VUSER with virtual user name, $DOMAIN with your domain, and $MAILDIR with the directory where the virtual user's email is to be stored.

maildirmake $MAILDIR
fsr setacl $MAILDIR $USER.daemon write
vmail $DOMAIN add $VUSER $MAILDIR
# Enter a password as prompted.
vmail $DOMAIN list
# You will see that the new account shows up.

Administration

We use a custom program called vmail to manage delivery to virtual mailboxes. It may be invoked with vmail $DOMAIN $COMMAND, which indicates that you are configuring the virtual mailboxes for domain $DOMAIN for which you have DomTool permissions. The valid commands are:

  • list: Print the mapping from usernames to mailbox directories for $DOMAIN.

  • add $USER $MAILDIR: Add a mapping from $USER@$DOMAIN to a Maildir directory $MAILDIR. You'll be prompted to enter a password for the user, which he can then use to access IMAP, POP, or restricted SMTP services.

  • passwd $USER: Reset a virtual user's password.

  • rm $USER: Remove a mapping. The mailbox directory remains for you to deal with as you like.

Note: If you try to log in to the web interface this will fail because the mail directory has not been initialized yet. Send a test message to the new account, then verify that the $MAILDIR directory now has some files and directories, then try to access the account from the web interface.

Access

People with virtual mailboxes may use the normal services for accessing their email, such as SSL IMAP and POP, and the [https://mail2.hcoop.net] web interface. They authenticate giving their full e-mail addresses as usernames, in contrast to the situation for normal UNIX users.

Changing password

People with virtual mailboxes may change their password using the handy web interface at [https://members.hcoop.net/passwd].

MemberManual/Email/VirtualMail (last edited 2015-04-13 16:13:37 by ClintonEbadi)