"Robert P. Thille" <[EMAIL PROTECTED]> writes: > Since the qmail virtualdomains file can list different > [EMAIL PROTECTED] entries which route to different addresses, when > checking the virtualdomains file for a 'match' for the original > envelope domain you need to check that the 'prepend' coupled with > the user part of the virtualdomain matches the 'ousername'. > > From virtualdomains: (edited to protect the guilty :-) > ------------------------------- > # John Smith's stuff: > [EMAIL PROTECTED]:jsmith > [EMAIL PROTECTED]:jsmith > > # user 'rthille' owns these domains, except the above > # specified users. > example.org:rthille-example > .example.org:rthille-example > nospam.example.org:rthille-spam > -------------------------------
[...] > So what happens without my patch is that when mail to > [EMAIL PROTECTED] comes in, the code matches against the > '[EMAIL PROTECTED]' entry, picks 'jsmith' for the prepend to remove > from the envelope sender, but the envelope sender is really > '[EMAIL PROTECTED]' (after qmail has munged it) so > the prepend removal doesn't happen. Unfortunately, TMDA won't work in situations like this, even with the patch. The virtual domain configuration above will cause qmail to deliver mail addressed to [EMAIL PROTECTED] to the 'jsmith' user (or to look up 'jsmith' in /var/qmail/users/cdb). Without the patch, TMDA will match the wrong virtual domain, as you note. With the patch, TMDA will sometimes match the correct virtual domain and sometimes it won't. The problem occurs when mail comes in to an extension address like [EMAIL PROTECTED] Qmail will use the example.org:rthille-example line, *not* the [EMAIL PROTECTED]:jsmith line. qmail-send only looks for exact matches when it searches for virtual users. This means that no confirmation replies can get back to the correct user in situations like the above example (they will go to the user controlling the entire domain) and also that users like the 'jsmith' user cannot use any tagged addresses. The suggested patch would get us one step further into the delivery process (i.e., tmda-filter would correctly strip the prepend when invoked for the virtual user '[EMAIL PROTECTED]') but it doesn't solve the ultimate problem, which is that regardless of anything TMDA does, qmail will not deliver extension addresses to the correct virtual user. I'm not sure what we should do about this, because, with or without the patch, it's not going to work. Any thoughts are welcome. Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
