aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/installing/email.md17
-rw-r--r--docs/installing/manual_install.md46
2 files changed, 57 insertions, 6 deletions
diff --git a/docs/installing/email.md b/docs/installing/email.md
index 5eaaa3786..90d7a74a6 100644
--- a/docs/installing/email.md
+++ b/docs/installing/email.md
@@ -323,7 +323,7 @@ is working (it doesn't actually send any mail). If it is working, you
should receive a delivery report email, with text like:
<foi+request-1234@example.com>: delivery via alaveteli:
-delivers to command: /var/www/alaveteli/script/mailin
+ delivers to command: /var/www/alaveteli/script/mailin
<backupfoi@local.machine.name>: delivery via local: delivers to mailbox
You can also test the other aliases you have set up for your domain in
@@ -339,6 +339,11 @@ delivery report email using the `mail` command on a new server:
apt-get install mailutils
+If emails are not being received by your Alaveteli install, we have some
+more troubleshooting tips for incoming mail in [the manual install
+guide]({{ site.baseurl }}docs/installing/manual_install/#troubleshooting).
+
+
## Example setup on exim4
@@ -541,6 +546,10 @@ message routing in the same way:
user-support@example.com -> |/var/www/alaveteli/script/handle-mail-replies
transport = alaveteli_mailin_transport
-There is a great
-[Exim Cheatsheet](http://bradthemad.org/tech/notes/exim_cheatsheet.php)
-online that you may find useful.
+If emails are not being received by your Alaveteli install, we have some
+more troubleshooting tips for incoming mail in [the manual install guide]({{ site.baseurl }}docs/installing/manual_install/#troubleshooting). There is also a
+great [Exim
+Cheatsheet](http://bradthemad.org/tech/notes/exim_cheatsheet.php) online
+that you may find useful.
+
+
diff --git a/docs/installing/manual_install.md b/docs/installing/manual_install.md
index 7eac53ae3..20b672856 100644
--- a/docs/installing/manual_install.md
+++ b/docs/installing/manual_install.md
@@ -541,7 +541,7 @@ and so it knows to include that in any absolute urls it serves.
We have some [production server best practice
notes]({{ site.baseurl}}docs/running/server/).
-## What next?
+## What next?
Check out the [next steps]({{ site.baseurl }}docs/installing/next_steps/).
@@ -579,10 +579,52 @@ Check out the [next steps]({{ site.baseurl }}docs/installing/next_steps/).
75
The `mailin` script emails the details of any errors to
- `CONTACT_EMAIL` (from your `general.yml` file). A common problem is
+ `CONTACT_EMAIL` (from your `general.yml` file). A common problem is
for the user that the MTA runs as not to have write access to
`files/raw_emails/`.
+ If everything seems fine locally, you should also check from another
+ computer connected to the Internet that the DNS for your chosen
+ domain indicates that your Alaveteli server is handling mail, and
+ that your server is receiving mail on port 25. The following
+ command is a query to ask which server is handling the mail for
+ the domain `example.com`, which receives the answer `mail.example.com`.
+
+ $ host -t mx example.com
+ example.com mail is handled by 5 mail.example.com.
+
+ This next command tries to connect to port 25, the standard SMTP
+ port, on `mail.example.com`, and is refused.
+
+ $ telnet mail.example.com 25
+ Trying 10.10.10.30...
+ telnet: connect to address 10.10.10.30: Connection refused
+
+ The transcript below shows a successful connection where the server
+ accepts mail for delivery (the commands you would type are prefixed
+ by a `$`):
+
+ $ telnet 10.10.10.30 25
+ Trying 10.10.10.30...
+ Connected to 10.10.10.30.
+ Escape character is '^]'.
+ 220 mail.example.com ESMTP Exim 4.80 Tue, 12 Aug 2014 11:10:39 +0000
+ $ HELO X
+ 250 mail.example.com Hello X [10.10.10.1]
+ $ MAIL FROM: <test@local.domain>
+ 250 OK
+ $ RCPT TO:<foi+request-1234@example.com>
+ 250 Accepted
+ $ DATA
+ 354 Enter message, ending with "." on a line by itself
+ $ Subject: Test
+ $
+ $ This is a test mail.
+ $ .
+ 250 OK id=1XHA03-0001Vx-Qn
+ QUIT
+
+
* **Various tests fail with "*Your PostgreSQL connection does not support
unescape_bytea. Try upgrading to pg 0.9.0 or later.*"**