<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Crossed Wires &#187; servers</title>
	<atom:link href="http://veejoe.net/blog/tag/servers/feed/" rel="self" type="application/rss+xml" />
	<link>http://veejoe.net/blog</link>
	<description>Vic's Blog</description>
	<lastBuildDate>Sat, 31 Dec 2011 13:29:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>LDAP groups in Postfix</title>
		<link>http://veejoe.net/blog/2010/02/ldap-groups-in-postfix/</link>
		<comments>http://veejoe.net/blog/2010/02/ldap-groups-in-postfix/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 11:24:35 +0000</pubDate>
		<dc:creator>Vic</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[ldap]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[servers]]></category>

		<guid isPermaLink="false">http://veejoe.net/blog/?p=5490</guid>
		<description><![CDATA[For a long time I&#8217;ve been managing virtual e-mail addresses (the ones you create when you sign up to a web service, so that you know where your spam is originating) using Postfix&#8217;s LDAP alias capability.  At the time I was still putting every bit of configuration I could into LDAP&#8211;particularly if it was user-id [...]]]></description>
			<content:encoded><![CDATA[<p>For a long time I&#8217;ve been managing virtual e-mail addresses (the ones you create when you sign up to a web service, so that you know where your spam is originating) using Postfix&#8217;s LDAP alias capability.  At the time I was still putting every bit of configuration I could into LDAP&#8211;particularly if it was user-id related&#8211;and I&#8217;ve never had a need to change what was working really well.</p>
<p>N&#8217;s school recently decided to distribute the weekly school newsletter via e-mail, and had allowance for one e-mail address per family.  Not wanting the additional overhead of having to have either S or me receive it and then having to forward it to the other, I thought it would be neat to have a single common address that, when items arrived, distributed the mail to multiple boxes.  Of course I took the stupid path of providing the school with a yet-to-be-created e-mail address, foolishly trusting my ability to set the system up before they tried to send anything to it&#8230;  but in the end it was not so foolish after all, as unbeknown to me I already had everything I needed to achieve my objective.</p>
<p>Unfortunately the first thing I did was assume that I needed mailing list software.  I installed Mailman, and started to read-up on the process to get it working.  I did this on my yet-to-be-commissioned KVM-hosted mail server (a blog post for another day), and started trying to diagnose why mail wasn&#8217;t getting delivered.  I had set up Postfix on this mail server to point to my existing LDAP to test, and thought that there was a problem there (but also started to work out if there was a way to use the LDAP server to manage the Mailman aliases).  I re-found the <a href="http://www.postfix.org/LDAP_README.html" target="_blank">Postfix LDAP HOWTO</a>, and stumbled over the section entitled &#8220;Example: expanding LDAP groups&#8221;.  <em>Et voila: </em>multidrop incoming mail without the need for a mailing list manager!</p>
<p>I had always assumed that e-mail aliases were a one-to-one mapping of alias address to real destination.  Not the case: an alias can have multiple destinations.  It doesn&#8217;t just apply to LDAP alias support, either: as per the &#8220;aliases&#8221; man page you can do</p>
<pre>name: value1, value2, ...
</pre>
<p>In my LDAP situation, all I need to do is list the alias in the &#8220;mailLocalAddress&#8221; attribute of which ever users need to receive mail for that alias.  Done!</p>
<p>I may have to keep Mailman, however.  Shortly after this success, I wondered how cool it would be to have the notification SMS messages for voicemail received at home, that currently go only to S, come to me as well.  I&#8217;m using a hosted email-to-SMS gateway service for this, so the &#8220;alias&#8221; would have to expand to multiple <em>external</em> e-mail addresses.  I&#8217;m not sure if you can alias mail addresses that are not in your domain&#8230;  I&#8217;ll have to try and see&#8211;might be easier to do that than subscribing to a Mailman list via SMS-to-email!  <img src='http://veejoe.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://veejoe.net/blog/2010/02/ldap-groups-in-postfix/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

