1.1 --- a/docs/wiki/FrontPage Sun Nov 01 00:43:39 2015 +0100
1.2 +++ b/docs/wiki/FrontPage Sun Nov 01 18:43:11 2015 +0100
1.3 @@ -137,10 +137,11 @@
1.4
1.5 * [[/CounterProposals|Counter-Proposals and Offers]]
1.6 * [[/CronIntegration|Cron Task Scheduler Integration]]
1.7 - * [[/MailIntegration|E-Mail Integration]]
1.8 * [[/EventRecurrences|Event Recurrences]]
1.9 * [[/IncomingMessages|Incoming Messages]]
1.10 * [[/OutgoingMessages|Outgoing Messages]]
1.11 + * [[/MailIntegration|Mail Integration]]
1.12 + * [[/MailboxIntegration|Mailbox Integration]]
1.13 * [[/Testing|Testing]]
1.14 * [[/UseCases|Use Cases]]
1.15 * [[/WebServerIntegration|Web Server Integration]]
2.1 --- a/docs/wiki/MailIntegration Sun Nov 01 00:43:39 2015 +0100
2.2 +++ b/docs/wiki/MailIntegration Sun Nov 01 18:43:11 2015 +0100
2.3 @@ -1,4 +1,4 @@
2.4 -= E-Mail Integration =
2.5 += Mail Integration =
2.6
2.7 To act as a part of an e-mail system, imip-agent provides a number of programs
2.8 that may be invoked by mail transfer agents (MTAs) upon sending or receiving
2.9 @@ -75,6 +75,8 @@
2.10 || Postfix is also widely deployed and is sometimes preferred by administrators.
2.11 }}}
2.12
2.13 +Some hints on mail system configuration can be found in the [[/MTA|MTA guide]].
2.14 +
2.15 == Identification of Recipients ==
2.16
2.17 In principle, any mechanism supported by the MTA can be used to identify
3.1 --- a/docs/wiki/MailIntegration--LocalSMTP Sun Nov 01 00:43:39 2015 +0100
3.2 +++ b/docs/wiki/MailIntegration--LocalSMTP Sun Nov 01 18:43:11 2015 +0100
3.3 @@ -44,22 +44,36 @@
3.4 local+vincent.vole@example.com
3.5 }}}
3.6
3.7 -The message is then routed to a mail delivery mechanism, perhaps by converting
3.8 -the local address to a local system user identity:
3.9 +== Local System Users ==
3.10 +
3.11 +With such a local user indicated, the message is then routed to a mail
3.12 +delivery mechanism, perhaps by converting the local address to a local
3.13 +system user identity (a user with an account on the system running the
3.14 +software). For example:
3.15
3.16 {{{
3.17 vole
3.18 }}}
3.19
3.20 -The local delivery mechanism would then deposit the message in the user's mailbox.
3.21 -Alternatively, routing for a mail storage solution would accept the message for
3.22 -the local user and deliver it to that user's mailbox.
3.23 +The local delivery mechanism would then deposit the message in the user's
3.24 +mailbox. MTAs typically provide such routing for local system users by
3.25 +default.
3.26 +
3.27 +== Mailbox/Virtual Users ==
3.28
3.29 -MTAs typically provide routing for local system users by default. Where the
3.30 -mail system must instead route messages to mailbox providers employing LMTP,
3.31 -some more effort may be required. See the
3.32 +Alternatively, with a local user having been indicated, a message would be
3.33 +routed for delivery by a mail storage solution which would accept the message
3.34 +for the indicated user and deliver it to that user's mailbox. For example:
3.35 +
3.36 +{{{
3.37 +vincent.vole
3.38 +}}}
3.39 +
3.40 +Where such routing is performed to mailbox providers employing LMTP,
3.41 +some additional configuration effort may be required. See the
3.42 [[../../MailboxIntegration|mailbox integration guide]] for more details.
3.43
3.44 -Configuration files for routing messages for explicitly-indicated local users
3.45 -are provided in the [[../../MailIntegration/LDAP|LDAP]] and
3.46 -[[../../MailIntegration/Simple|simple]] integration guides.
3.47 +Some of the routing for explicitly-indicated local users is dependent on the
3.48 +identification of users and is described in the
3.49 +[[../../MailIntegration/LDAP|LDAP]] and [[../../MailIntegration/Simple|simple]]
3.50 +integration guides.
4.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
4.2 +++ b/docs/wiki/MailIntegration--MTA Sun Nov 01 18:43:11 2015 +0100
4.3 @@ -0,0 +1,64 @@
4.4 += Mail Transfer Agents =
4.5 +
4.6 +Although this documentation does not seek to cover the details of configuring
4.7 +mail transfer agent (MTA) software, some hints and tips are offered to help
4.8 +avoid frustration.
4.9 +
4.10 +== General ==
4.11 +
4.12 +Some general measures are presented below.
4.13 +
4.14 +=== Mailname ===
4.15 +
4.16 +The contents of `/etc/mailname` should probably be the fully-qualified hostname,
4.17 +at least for Exim and Postfix. See
4.18 +[[https://wiki.debian.org/EtcMailName|the Debian Wiki page]] for more details.
4.19 +
4.20 +=== Hostname ===
4.21 +
4.22 +The `hostname` command should provide a suitable hostname on the system, or MTAs
4.23 +may behave strangely. This can be tested with the following command:
4.24 +
4.25 +{{{
4.26 +hostname -f
4.27 +}}}
4.28 +
4.29 +It should report a fully-qualified hostname.
4.30 +
4.31 +=== Interfaces ===
4.32 +
4.33 +Some software attempts to listen on interfaces that may not be supported. For example,
4.34 +Exim may be configured to listen on both IPv4 and IPv6 interfaces, even in environments
4.35 +(such as User Mode Linux) where IPv6 interfaces may not be available.
4.36 +
4.37 +== Exim ==
4.38 +
4.39 +On Debian, the following command can be run to adjust the configuration:
4.40 +
4.41 +{{{
4.42 +dpkg-reconfigure exim4-config
4.43 +}}}
4.44 +
4.45 +The following questions are especially interesting:
4.46 +
4.47 +{{{{#!table
4.48 +'''Question''' || '''Remarks'''
4.49 +==
4.50 +IP-addresses to listen on for incoming SMTP connections
4.51 +|| Remove IPv6 interfaces in User Mode Linux or other environments without
4.52 +.. IPv6 support or Exim will not bother listening on IPv4 interfaces either.
4.53 +==
4.54 +System mail name
4.55 +|| State the fully-qualified hostname, not just the domain name, which is
4.56 +.. what the dialogue suggests is sufficient. For example:
4.57 +{{{
4.58 +mailserver.example.com
4.59 +}}}
4.60 +==
4.61 +Other destinations for which mail is accepted
4.62 +|| This is a colon-separated list that should indicate the local domain as
4.63 +.. well as the unqualified hostname. For example:
4.64 +{{{
4.65 +mailserver:example.com
4.66 +}}}
4.67 +}}}}
5.1 --- a/docs/wiki/MailboxIntegration Sun Nov 01 00:43:39 2015 +0100
5.2 +++ b/docs/wiki/MailboxIntegration Sun Nov 01 18:43:11 2015 +0100
5.3 @@ -98,3 +98,19 @@
5.4 These files provide example definitions for the `master.cf` and `transport`
5.5 files that typically reside under `/etc/postfix`. Their contents can be
5.6 merged with those files as appropriate.
5.7 +
5.8 +== Permissions ==
5.9 +
5.10 +Note that remarks about permissions management in the
5.11 +[[../MailIntegration/LMTP|LMTP guide]], concerning communication with mail
5.12 +storage systems such as Cyrus, also apply when getting MTAs such as Postfix
5.13 +to communicate with those systems. Consequently, it may be necessary to add
5.14 +the dedicated MTA system user to a specially-created `lmtp` group. For
5.15 +example:
5.16 +
5.17 +{{{
5.18 +adduser postfix lmtp
5.19 +}}}
5.20 +
5.21 +See the [[../SystemUsers|system users guide]] for more information on the `lmtp`
5.22 +group.
6.1 --- a/docs/wiki/SystemUsers Sun Nov 01 00:43:39 2015 +0100
6.2 +++ b/docs/wiki/SystemUsers Sun Nov 01 18:43:11 2015 +0100
6.3 @@ -32,7 +32,7 @@
6.4 }}}
6.5
6.6 This group should be employed for LMTP delivery by systems like Cyrus and
6.7 -Dovecot. See the section on configuring mail systems for delivery for more
6.8 +Dovecot. See the [[../MailboxIntegration|mail storage guide]] for more
6.9 information.
6.10
6.11 A system user needs to be created and to belong to certain groups in order to
6.12 @@ -55,6 +55,13 @@
6.13 (which merely needs the ability to connect to a local network service) whilst
6.14 allowing the Web server to read data written by those programs.
6.15
6.16 +{{{#!wiki tip
6.17 +It is possible to use the above strategy for LMTP with local SMTP delivery
6.18 +because there may be a need to create the `lmtp` group so that MTAs can deliver
6.19 +to [[../MailboxIntegration|mail storage solutions]]. However, this approach
6.20 +provides a means of separating imip-agent from mail-related users and groups.
6.21 +}}}
6.22 +
6.23 A system user needs to be created and to belong to certain groups in order to
6.24 deliver messages to mail stores and to publish resources on the Web:
6.25