I've been writing a FAQ that covers in its main thrust how to use
implement and use multiple email addresses for mail filtering. Exim
is an MTA I currently do not have an entry for. The latest copy can
be found at <URL:
http://www.netusa.net/~eli/faqs/addressing.html>.
Chris Thompson (cet1@???) wrote on Sun, 6 Apr 1997 (and I
found in the web archive of the list):
> Brian Blackmore wanted
> > to use an address that is only valid for a certain time after the
> > posting has been made. I would like to implement this so that any
> > mail addressed to
> Surely it would be easier to put the variable in the local-part, for
> example
> bnb-x859840695x@???
Hmmm. Is this sort of thing automatic? With a properly .cf'ed sendmail
one can just append "+<string>" for strings that do not contain
whitespace or RFC822 special characters to a user id to get a new
email address automatically. With qmail the user needs to create a
configuation file for each address she wants (or a catchall default
file).
How does exim fit in? This bit from that post leads me to believe it
is admin configurable for something like that:
> Alternatively, if user-defined suffixes are allowed in the domain,
> in the style of chapter 38 of spec.txt, then this sort of check
> could be done on a per-user basis in their Exim filter files.
What kind of admin configuration is needed? What kind of filtering
does an exim filter file offer? (A way to invoke procmail as the
filter from the file would make me happy for my FAQ. I'd rather not
be writting a FAQ on every mail filter out there, particularly not
when I can nag Nancy McGough to update her filtering FAQ instead.)
> > Is this implementable without writing another director??
> If the expiry key is in the local-part, it could certainly be done
> without a new director *type*, if that is what you mean. You would
...
What's this director business? Sounds like an MDA to me so far.
Elijah
------
please do not CC me when replying to the list
__END__
