I've just subscribed to the list. I read the FAQ and got some hints, also searched the mailing list archives as well as the HTML docs. The situation: my company has been bought. We were (and still are) using MMDF for mail transport. I, and several other employees, have been using an MMDF feature whereby mail to "user=token@domain" gets routed to "user@domain". We then parse the mail when it's delivered to our local mailbox. This allows us to route mailing list mail to specific mailboxes. We also use it when giving addresses to sites we don't really trust -- if I start getting spam to "user=amazon@domain", I'll be pretty sure who to blame. [sendmail apparently has a similar feature for routing "user+token@domain"] Now, our IS department is switching our MTA to qmail. I have nothing to do with it, so I have little control over what's going to happen. I'm trying to research how they can configure qmail to do this sort of thing, without it being a big hassle for them. We have one (probably more) bastion host(s) running qmail, transporting mail inbound to the company. These are already set up; mail to our old company name is still being routed via MMDF, while mail to the new company goes via qmail. Internal routing beyond the bastion host is fairly complex, with several hundred users, thousands of mutual-interest aliases, and dozens of mail hosts (mail to user1@domain ends up in mailhost1.domain:~user1/.mailbox while mail to user2@domain ends up in someotherhost.domain:/usr/spool/mail/user2). I don't know how that part is currently being handled. I've been able to test for certain that none of "user=token@domain", "user+token@domain", "user-token@domain", or "user.token@domain" are being processed in the desired manner. All of them return bounces similar to: From mail.caldera.cozz!orphanage Thu Aug 2 18:20:18 2001 Date: 3 Aug 2001 01:22:53 -0000 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: failure notice Hi. This is the qmail-send program at calderasystems.cozz. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[EMAIL PROTECTED]>: Sorry, no mailbox here by that name. (#5.1.1) --- Below this line is a copy of the message. [...] (old-domain = sco.com, new-domain = caldera.com; I'm trying not to include any real, complete addresses in this message, in case evil people mine the list archives for spam targets. I changed "com" to "cozz" above to avoid them being correct addresses.) In the qmail docs, I can see how to set this sort of thing up for one user at a time. qmail-users(5) describes the file /var/qmail/users/assign and how it could presumably be configured with: +belal=:belal:(I don't know what goes here when it's being used as a relay) +bela.lubkin=:belal:(relay) MY QUESTION: is there any way this could be set up in a global fashion, rather than listing every single user in some config file? That is, I want to instruct qmail that for _all_ addresses "user=token@domain", it should relay (according to all other relay configuration) as if the mail were addressed to "user@domain". If possible I'd like to set up several different characters for this, so that "user+token@domain" and "user-token@domain" would also work (I frequently encounter web pages which will not accept "=" as an email address character; I'm sure other characters are similarly burdened -- I want a whole pallette of choices to try.) And I want this all to be so easy that even the most overworked, uninterested and half-competent IS person would be able to set it up in five minutes. ;-} So, what can I do? Thanks, >Bela<
