[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Fri Apr 9 08:41:02 2004 -->
- <!--x-from-r13: cunfrsk ng znthfncghf.pbz (Xnfba Sgurevqtr) -->
- <!--x-message-id: B49DB50C-8A22-11D8-8EE6-[email protected] -->
- <!--x-reference: DC07E888-8A1C-11D8-8EE6-[email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] email aliases and wildcards -->
- <li><em>date</em>: Fri Apr 9 08:41:02 2004</li>
- <li><em>from</em>: phasefx at magusaptus.com (Jason Etheridge)</li>
- <li><em>in-reply-to</em>: <<a href="msg00298.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00297.html">[email protected]</a>> <<a href="msg00298.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] email aliases and wildcards</li>
Ah ha. :D Found something in Exim that should work:
"Heavy email users often want to operate with multiple mailboxes, into
which incoming mail is automatically sorted. A popular way of handling
this is to allow users to use multiple sender addresses, so that
replies can easily be identified. Users are permitted to add prefixes
or suffixes to their local parts for this purpose. The wildcard
facility of the generic router options local_part_prefix and
local_part_suffix can be used for this. For example, consider this
router:
??userforward:
?? driver = redirect
?? check_local_user
?? file = $home/.forward
?? local_part_suffix = -*
?? local_part_suffix_optional
?? allow_filter
It runs a user's .forward file for all local parts of the form
*username-**. Within the filter file the user can distinguish different
cases by testing the variable $local_part_suffix. For example:
??if $local_part_suffix contains -special then
?? save /home/$local_part/Mail/special
??endif
If the filter file does not exist, or does not deal with such
addresses, they fall through to subsequent routers, and, assuming no
subsequent use of the local_part_suffix option is made, they presumably
fail. Thus, users have control over which suffixes are valid."
I'm going to see if I can find the equivalent in postfix, so I don't
have to migrate spamassassin over to exim.
Thanks!
-- Jason
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00297" href="msg00297.html">[ale] email aliases and wildcards</a></strong>
<ul><li><em>From:</em> phasefx at magusaptus.com (Jason Etheridge)</li></ul></li>
<li><strong><a name="00298" href="msg00298.html">[ale] email aliases and wildcards</a></strong>
<ul><li><em>From:</em> ale at FultonGreen.com (Fulton Green)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00299.html">[ale] Microsoft Security Summit</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00301.html">[ale] email aliases and wildcards</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00298.html">[ale] email aliases and wildcards</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00301.html">[ale] email aliases and wildcards</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00300"><strong>Date</strong></a></li>
<li><a href="threads.html#00300"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>