[Workaround.org] r154 - trunk/etch
chaas at workaround.org
chaas at workaround.org
Thu Nov 1 13:45:34 CET 2007
Author: chaas
Date: 2007-11-01 13:45:34 +0100 (Thu, 01 Nov 2007)
New Revision: 154
Modified:
trunk/etch/en.rest
Log:
Added link to PHP administration script from Robert Klikics
Modified: trunk/etch/en.rest
===================================================================
--- trunk/etch/en.rest 2007-10-23 18:57:12 UTC (rev 153)
+++ trunk/etch/en.rest 2007-11-01 12:45:34 UTC (rev 154)
@@ -40,7 +40,7 @@
:Title: Howto: ISP-style Email Server with Debian-Etch and Postfix
:Authors: Dipl.-Inform. Christoph Haas
-:License: (C) 2007 Christoph Haas. This documented is published under the
+:License: (C) 2007 Christoph Haas. This document is published under the
terms of the GNU General Public License
(http://www.gnu.org/licenses/gpl.html)
:Revision: $Rev$
@@ -2033,7 +2033,7 @@
</script>
</div>
-Step 12: Populate the database / Console interface: ispadmin
+Step 12: Populate the database / Console and interface
==============================================================
Now that the setup is working with your test entries it is now time to
@@ -2050,14 +2050,17 @@
Of course you need a convenient user interface to administer the data in the
database. Many readers offered to write a web interface to simplify the
-administration of domains, accounts and aliases. But actually none of these
-projects released usable software yet. Until we see some of that work you can
-use my console-based "ispadmin.py" Python program, that helps you administer
-domains, aliases and users. You only need to have the ``python-sqlalchemy`` and
-``python-mysqldb`` packages installed. Then download the `ispadmin.py
-<ispadmin.py>`_ program, change the *db_uri* line at the beginning of the
-script and run it. The program knows a few basic commands:
+administration of domains, accounts and aliases. But so far only Robert Klikics
+published a `PHP script <http://ronnytiebel.de/code/mail_control.phps>`_
+written by his apprentice Ronny Tiebel.
+If you prefer working on the console you may as well use my console-based
+"ispadmin.py" Python program, that helps you administer domains, aliases and
+users. You only need to have the ``python-sqlalchemy`` and ``python-mysqldb``
+packages installed. Then download the `ispadmin.py <ispadmin.py>`_ program,
+change the *db_uri* line at the beginning of the script and run it. The program
+knows a few basic commands:
+
- d / domains: shows a list of all domains. If an argument is given then only
domains are listed that start with the given string. If a number or the actual
name of the domain is entered then the program will switch to that domain.
@@ -2152,9 +2155,12 @@
A frequently asked question is how to run mailing lists with virtual
domains using the famous 'mailman' software. Actually this is not
-very hard. There are different ways to accomplish that. Let me just
-explain the way with *local aliases*.
+very hard. There are different ways to accomplish that.
+The simplest but least flexible way uses *local aliases*:
+Using local aliases
+........................
+
This first approach will use the aliases that you usually insert
into ``/etc/aliases``.
You just have to understand that virtual users cannot have piped aliases.
@@ -2182,6 +2188,43 @@
the /etc/aliases into the MySQL database, too. Let me know if you
have invented something. :)
+..
+ Using transport maps
+ .........................
+
+ (coming soon)
+
+ If you want to allow your customers/clients to have their own mailing lists
+ then the above solution is not flexible enough. Consider using Postfix'
+ powerful transport maps. They allow you to tell postfix which transport
+ (service) to use for certain domains and even certain email addresses.
+
+ Using a regular expression lookup table e.g. that looks like the following cases as emails
+ for the list 'mylist at example.com' to be forwarded to mailman, everything else
+ within 'example.com' has normal virtual delivery:
+
+ /etc/postfix/transport-lists-regex:
+ /^(mylist|mylist-.*)@example\.com$/ mailman:
+
+ You could use a mysql lookup table nearly the same way, when you add all
+ mylist-.*@example.com addresses for every list there and give them
+ mailman: as transport.
+
+ The mysql lookup table should also work with having only two entries for
+ each list, i.e. for 'mylist at example.com' and 'mylist-%@example.com' and
+ define the mysql looup table the following way:
+
+ /etc/postfix/transport-lists-mysql:
+ user = mailuser
+ password = mailuser2007
+ hosts = 127.0.0.1
+ dbname = mailserver
+ query = SELECT transport FROM transports WHERE email='%s' OR email LIKE '%s'
+
+
+ [Courtesy of Michael Dürgner]
+
+
Greylisting with postgrey
----------------------------
@@ -2334,6 +2377,7 @@
- Lucas Baltes
- Mario Duve
- Matthias Quade
+- Michael Dürgner
- Michael Weisgerber
- Mikael Tokarev
- Oliver Ladner
More information about the Workaround-chitchat
mailing list