Before starting the Hedwig IMAP server, you need to create the hedwig database in MySQL. There are two files in the sql/mysql directory: hedwig-schema.sql and hedwig.mwb.
The hedwig-schema.sql file contains all the CREATE statements required to create the structure of the hedwig database including tables and triggers.
The hedwig.mwb file is a MySQL Workbench data model that you can open within MySQL Workbench.
To install the hedwig database, follow these steps:
shell> mysql -u root -p
Enter your password when prompted. A non-root account can be used as long as the account has privileges to create new databases.
mysql> SOURCE D:/hedwig/sql/mysql/hedwig-schema.sql;
Replace D:/hedwig/sql/mysql/hedwig-schema.sql with the path to the hedwig-schema.sql file on your system.
mysql> USE hedwig; Database changed mysql> SHOW TABLES;
+------------------+ | Tables_in_hedwig | +------------------+ | hw_acl | | hw_alias | | hw_headername | | hw_headervalue | | hw_keyword | | hw_mailbox | | hw_message | | hw_physmessage | | hw_subscription | | hw_user | +------------------+ 10 rows in set (0.00 sec)
You can manage users directly using SQL queries. And you can also manage users using Web console. See the Web Console for more information about Web console.
You can manage aliases directly using SQL queries. And you can also manage aliases using Web console. See the Web Console for more information about Web console.
The alias table provides a system-wide mechanism to redirect mail for local recipients.
Before configuring the server, make sure you configure your DNS server correctly. For SMTP to work, you must define MX records for your domain. MX stands for Mail eXchanger. Simply put the MX records tell other email servers what server in your domain is responsible for handling mails.
Nslookup is a command line program that basically queries DNS-servers for information. You can do all kind of DNS lookups using nslookup. The text below shows how to do MX lookups. Start the command prompt and check if the response include an MX record.
C:> nslookup -type=mx yourdomainname.com Server: your-isp-dns-host Address: your-isp-dns-address yourdomainname.com MX preference = 10, mail exchanger = mail.yourdomainname.com (the line above is your MX exchanger) mail.yourdomainname.com internet address = your-mail-server-ip
Hedwig has minimal configuration parameters that are controlled via the default.properties file. You can find this file at conf directory. Before starting the server, you need to configure some parameters to your environment. Enter the JDBC URL for the jdbc.url property, and adjust username/password for the database.
jdbc.driver=com.mysql.jdbc.Driver jdbc.url=jdbc:mysql://[host]:[port]/hedwig jdbc.user=[username] jdbc.password=[password] jdbc.maxActive=[number] jdbc.maxIdle=[number]
The fully qualified Java class name of the JDBC driver to be used.
The connection URL to be passed to our JDBC driver to establish a connection.
The connection username to be passed to our JDBC driver to establish a connection.
The connection password to be passed to our JDBC driver to establish a connection.
The maximum number of active connections that can be allocated from connection pool at the same time, or zero for no limit.
The maximum number of active connections that can remain idle in the pool, without extra ones being released, or zero for no limit.
In minimal configuartion, all you need to configure is the jdbc related parameters if the host name for your server is properly set.
The default.properties configuration file specifies minimal parameters that control the operation of the server. Most parameters have default values, and need not to be specified.
Default values are shown after the parameter name in parentheses.
The directory where Hedwig data files are stored. This directory must be owned by the hedwig account, and must not be shared with non-Hedwig software.
The directory where Hedwig temporary files are stored.
The location of Hedwig top-level queue directory. This is the root directory of Hedwig MTA daemon is monitoring.
The location of keystore file. This file must be in JKS format. You can create this file using keytool command-line utility included in the JDK. You MUST specify this parameter if you want to use SSL/TLS for IMAP or SMTP server. See the Using SSL/TLS for more information about how to configure SSL/TLS.
Password for recovering keys in the keystore. You need not specify this parameter if the tls_keystore parameter is not specified.
Password used to check the itegrity of keystore. You need not specify this parameter if the tls_keystore parameter is not specified.
Name of the JAAS login module. See the JAAS LoginModule for more information about JAAS login module.
Followings are description of all IMAP configuration parameters.
Message files are automatically compressed after the configured time. The actual compression is done in a nighty cronjob, which you must set up:
Time units: y(years), m(months), d(days)
Example:
compress_after=3m
Mails are expunged from mailboxes after being there the configurable time. The actual expunging is done in a nightly cronjob, which you must set up:
Example:
expunge_after=INBOX 3m Trash 2m
Stop disk cleanup cron (which is responsible for compression of message file and expunging mails) after the configured time from it started.
Time units: h(hours), m(minutes)
Example:
stop_cron_after=3h
The default quota for uers in mega bytes. Specify 0 when user has no limit in quota.
The IMAP socket I/O timeout value in seconds, or zero (timeout infinity).
The maximun number of IMAP worker threads.
The IMAP protocol trace mode. If true protocol trace will be printed to the output specified by the imap_protocol_log parameter.
The location of file used for debugging output for IMAP protocol. If empty, the standard output will be used.
If you decided to use legacy MTA like Postfix, you dont need to read this section. Instead see Configuring_MTA for more information about the legacy MTA configuration.
SMTP configuration parameters are also controlled via the default.properties file. Before starting the server, you need to configure some parameters to your environment.
Followings are description of all SMTP configuration parameters.
The maximal number of times that a spooled message attempts to be re-sent. If a temporary exception has been caught during transmission, the infrastucture automatically retransmits the message. If a permanent exception is caught, a failure message is sent to the original message sender or postmaster. The retransmission algorithm quadruples the delay with every attempt, which result in approximately 42 minutes passing between the first transmission attempt and the last transmission attempt.
The maximal size in bytes of a message, including envelope information. Specify 0 when message size has no limit.
The internet domain name of this mail system. The default is to use $myhostname minus the first component.
Example:
mydomain=example.com
The internet hostname of this mail system. The default is to use the fully-qualified domain name from gethostname().
Example:
myhostname=host.example.com
The list of trusted SMTP clients that have privileges to relay mail through Hedwig. Specify a list of network address, network/netmask or network/netmask bits patterns, separated by commas and/or whitespace.
Note 1: If you set the mynetworks to 0.0.0.0/0, the Hedwig acts as an open relay server.
Example:
mynetworks=127.0.0.0/8 168.100.189.0/24 168.100.170.0/255.255.255.0
The sender address of delivery status notification message.
Example:
postmaster=postmaster@example.com
The host name to send in the SMTP EHLO or HELO command. The default value is the machine hostname.
SMTP server to be used as a gateway for this server. If this value is set, then all messages with remote recipients will be delivered to the gateway server. The port may be specified in the format host:port.
The username to be passed to the SMTP gateway to establish a connection.
The password to be passed to the SMTP gateway to establish a connection.
The maximum number of recipients that the Hedwig SMTP server accepts per message delivery request. Specify 0 when recipients count has no limit.
Enable SASL authentication in the Hedwig SMTP server. By default, the Hedwig SMTP server does not use authentication.
The Hedwig SMTP client socket connection timeout value in milliseconds. When no connection can be made within the deadline, the Hedwig SMTP client tries the next SMTP server associated with target MX record.
The Hedwig SMTP client socket I/O timeout value in milliseconds.
The SMTP protocol trace mode. If true protocol trace will be printed to the console.
The location of file used for debugging output for SMTP protocol. If empty, the standard output will be used.
Optional restrictions that the Hedwig SMTP server applies in the context of a client request.
The default is to allow all connection requests.
The following restrictions are specific to client hostname or client network address information.
Permit the request when the client IP address matches any network or network address listed in mynetworks.
List of servers that provides real-time black list (RBL) and domain name server black lists (DNSBL). Connections are blocked when the reversed client network address is listed with the A record under these domains.
Specify a list of rbl domains, separated by whitespace.
Note 1: If you're running a high-traffic mail server, you'd better setup a local DNS server to catch DNS queries, because free RBL service like zen.spamhaus.org may improperly reply if your server exceed the DNS query limit.
In addition, you can use the following generic restrictions.
Reject the request. This restriction is useful at the end of a restriction list, to make the default policy explicit.
Example:
smtpd_client_restrictions=permit_mynetworks, reject_rbl_client zen.spamhaus.org spamlist.or.kr, reject
SMTP server response delay in second after a client has made more than smtpd_soft_error_limit errors, and fewer than smtpd_hard_error_limit errors, without delivering mail.
The maximum number of errors a SMTP client is allowed to make without delivering mail. The Hedwig SMTP server disconnects when the limit is exceeded.
Optional restrictions that the Hedwig SMTP server applies in the context of a client RCPT TO command.
The default is to permit everything.
Search the specified access table for the resolved RCPT TO address, domain, or localpart@, and execute the corresponding action. If access table is not specified, conf/recipient_access file is used as a default table.
Reject the request when the RCPT TO address does not exist in the local user database.
Access retrictions for mail relay control that the Hedwig SMTP server applies in the context of the RCPT To command. Specify a list of restrictions, separated by commas.
IMPORTANT: If you do not specify this restrictions Hedwig will acts as an open relay server.
Permit the request when the client is successfully authenticated via the RFC 4954 (AUTH) protocol.
Optional restrictions that the Hedwig SMTP server applies in the context of a client MAIL FROM command.
The default is to permit everything.
Search the specified access table for the MAIL FROM address, domain, or localpart@, and execute the corresponding action. If access table is not specified, conf/sender_access file is used as a default table.
The number of errors a SMTP client is allowed to make without delivering mail before the Hedwig SMTP server slows down all its responses.
The SMTP server socket I/O timeout value in milliseconds, or zero (timeout infinity).
If you decided to use Hedwig's own MTA, you don't need to read this section. Instead see the Configuring_the_SMTP_server for more information about the MTA configuration.
Hedwig LDA is easy to configure with Postfix virtual domains support. Hedwig supports two delivery methods PIPE and LMTP.
Add hedwig-pipe service in /etc/postfix/master.cf:
hedwig-pipe unix - n n - - pipe
flags=DRhu user=hedwig/hedwig argv=/home/hedwig/bin/deliver.sh ${sender} ${recipient}
Replace hedwig above with your virtual mail user account.
Then set virtual_transport to hedwig-pipe in /etc/postfix/main.cf.
default_destination_recipient_limit = 50 virtual_mailbox_domains = your.domain.here virtual_transport = hedwig-pipe
And remember to run
postfix reload
LMTP will be supported in near future.
Add hedwig-lmtp service in /etc/postfix/master.cf:
hedwig-lmtp unix - - n - - lmtp
Then set virtual_transport to hedwig-lmtp in /etc/postfix/main.cf.
virtual_transport = hedwig-lmtp:<host>:<port>
Comment the bean definitions with followings IDs in the applicationContext.xml. (smtp.server, smtps.server, smtp.taskExecutor)
Use the following method to configure Outlook as an IMAP4 client.
Use the following method to configure Thunderbird as an IMAP4 client.
The following is a very simple example of a production default.properties file. The line numbers shown are provided for reference only and are not included in the actual file.
1. # Database connection information 2. 3. # MySQL Database connection 4. jdbc.driver=com.mysql.jdbc.Driver 5. jdbc.url=jdbc:mysql://localhost/hedwig 6. jdbc.user=hedwig 7. jdbc.password=s3cret 8. jdbc.maxActive=120 9. jdbc.maxIdle=30 10. 11. # Network information 12. mydomain=hedwig.org 13. myhostname=mail.hedwig.org
Lines 1 and 3 are comments. Line 4 through 9 are for database connection information.
Line 11 is a comment. Line 12 specifies the internet domain name of the mail system. Line 13 specifies the internet hostname of the mail system.