Thus spake Jason R. Mastaler: > So basically, you specify a header, say > ``X-Original-To'', which is added to your incoming messages by your > MTA. It might look like: > > X-Original-To: [EMAIL PROTECTED] > > TMDA then parses the address in this header and sets RECIPIENT and EXT > for you in the environment. > > [EMAIL PROTECTED] > EXT=dated-1037484885.7112e0
That would be great if tmda could handle this. But I'm not sure how to solve this problem in a general way. The real problem is, that there are so many different dial-scenarios. 1) For example some isps add a uniq header to message to identify the envelope recipient (those would simply let tmda figure out the recipient based on `x-orignal-to'). 2) A more common scenario (in my opinion) is a isp that does not provide the dialup user qmail-extension addresses or a uniq-header. Such a user (like me) has to configure a catch-all address to be able to receive mail destinied to a qmail-like extension address (e.g. [EMAIL PROTECTED]). Furthermore, it is harder to figure out the envelope recipient (e.g. play with delivered-to lines). So, the first case is simple and could be easily handled by a further tmda configure variable and some code. The second case requires some preprocessing by a tool like procmail to insert a uniq header like 'x-orignal-to' that contains the _real_ envelope recipient. But we could help here if we would provide some recipes on how to get it working. Marcus -- .signature: No such file or directory _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
