Sam Varshavchik wrote:
You can have a situation where the original message was addressed to
different recipients, but each one forwarded the message to the same
forwarding address.
Although 99.9% of the time this situation simply results in two copies
of the same message coming in, one from each forward, theoretically it's
possible that -- depending on the addresses involved, and the
intermediate mail relay logic, you can end up with both forwards coming
in as a single message, with two RCPT TO: addresses naming the same
recipient address, but a different original recipient address. Now what?
Drop one of them as a dupe? Can't do that. What if you'll end up
forwarding this message?
I guess I don't understand why that's a problem. If courier happens to
know that the two original addresses have the same destination, and
decides not to only list that destination in the recipients file, what
breaks? I know I'm a little slow today (failure to sleep adequately),
but could you maybe present an example situation and explain where this
really causes something bad to happen?
You received it with two RCPT TO: addresseses,
and a different original recipient address, and after forwarding you're
going to send a single RCPT TO: address, with whatever was the original
recipient address in the first RCPT TO: statement. That definitely
doesn't sound right.
Sounds OK to me. I expect that I'm not grasping what you're trying to
tell me.
14 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: duplicate del...
