On Tue, Jan 25, 2005 at 05:48:14PM +0200, David Jacobson wrote:
Client A e-mails User A,B and C instead of his server sending one e-mail it is sending responses to User A,B and C seperately (so the
This is appropriate behavior. If Joe sends an email to Bob, Alice, and Fred, Joe should receive seperate challenges from each user.
Except that the original poster was using a single TMDA installation as a proxy/filter for an entire organisation's email, then delivery the results forward to another server for end-user delivery.
Thus, what he want to have happen is for the TMDA filter host to challenge once, and then after confirmation acceptance, deliver the original email once to the next SMTP server.
The problem is with the qmail configuration on the TMDA filter SMTP server. Well, actually, it's not a config problem, just the way it works...
This is just a rehash of what an earlier poster said:
The thing is, on the TMDA box, qmail is configured to accept email for the domain in question as local. It must be setup this way, or such email would simply be queued and then dumped on whatever MX was setup for the domain.
So, qmail now knows it's delivering email locally. In 99.9% of the cases, every local address is a separate user, separate mailbox etc.
Hence, for each user that a message is sent to, qmail will attempt local delivery. It invokes a separate local delivery for each user. Thus, an email sent to 3 people will be locally delivered 3 times, to 3 different users.
The fact that your qmail setup routes all those different users to the same TMDA installation is something qmail can't possibly know, since this is all done by the virtualdomains routing, and the content of .qmail files. qmail doesn't look at these and make grouping decisions based on the content, it simply follows whatever mappings are defined in virtualdomains, and executes the commands in the .qmail file, blindly for each local address.
...
I can certainly conceive of an MTA that could be configured not to do this. Perhaps setting up TMDA as an milter in sendmail, or some kind of filtering agent (not sure of terminology) in postfix, would do the trick. The thing is, you'd have to hook TMDA into the queueing part of the MTA, not the local delivery part, which is where it's typically setup.
That said, I have no clue how to do this - someone else might? _____________________________________________ tmda-users mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-users
