Peter J. Holzer skribis 2007-12-10 23:01 (+0100):
> > Qmail's modular design made replacing the SMTP daemon very simple, and
> > because
> > development on qmail stopped with version 1.03 in 1993, several replacement
> ^^^^^^^^^^^^^
> 1998.
Heh, I've got this patch 4 times now. I'm lucky to have such careful
reviewers here! Thanks.
> The aliases plugin supports catch-all domains and catch-all extensions,
> although the separator character is hard-coded to be "+" (like in
> sendmail) instead of "-" (as in qmail). That should be fairly easy to
> change. User extensions are not supported, but I'm not sure how they are
> different from catch-all extensions at the the MTA level - IMHO that's a
> matter for the MDA.
I'll take this into account in the next version. However, I'm not going
for "easy to change" unless it's actually a configuration option.
Qmail has, in addition to catch all user extensions, specific user
extensions. E.G., on a bare qmail installation, I could have both
[EMAIL PROTECTED] and [EMAIL PROTECTED], without having
[EMAIL PROTECTED], if I wanted.
> (But I am thinking about "user-registered" extensions at the MX: So if I
> have a username of "hjp", and I have registered and extension of "foo",
> mails to <hjp/[EMAIL PROTECTED]> are accepted but mails to
> <hjp/[EMAIL PROTECTED]> are not ("/" here is an arbitrary separator
> character - it could be "-", but "-" does occur in personal names, so
> I'm reluctant to use that - it should be configurable anyway).)
That's what qmail allows by default. The aliases plugin currently
*strips* the extension before checking (and adds it back after
expanding), so indeed that makes it awkward to use with a "-" separator.
Note that qmail has no simple way of preserving the extension in a
forward instruction.
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> <http://juerd.nl/sig>
Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>
