David Illsley wrote:
Tough on who? AFAIK the first response will be processed by Axis2
regardless of which original recipient received it.
Yes. Its user error for messing it up ..
Basically, I don't think we should be limiting the ability for someone to
use the underlying transport fully. The alternative is that Synapse will
write their own version of mail-send which will allow a Cc .. that makes
no sense at all to me.
Yuk, surely if a mediation does that it has some responsibility for
aggregating the responses? Also this sounds like a case where
Notification/Eventing might be most appropriate?
Even Eventing doesn't solve this problem - if I get a message I have to
know whether I'm going to reply or not .. whether it was delivered via
eventing or not doesn't make a difference.
Yes, but in user e-mail there's some expectation that the user looks
at how they were addressed to, perhaps because of the message content.
We don't (AFAIK) have any notion of that in SOAP/email, or do we?
No, there isn't ... agreed. However, its again up to the people setting
this up to make sure that wrong stuff doesn't happen.
Example: Lots of people have bots sign up to mailing lists (for archiving,
for spammers to easily gather data etc. etc.). Obviously they receive all
the mail but they never reply. If they reply (and then reply to the reply
etc.) a loop will occur. Has happened before .. I used to run email for
Sri Lanka and back in those days (early 90s) it was common for badly
configured mail servers to start bouncing bounces and keep doing that. I
used to have to manually notice this and fix it. Mail software is smarter now.
Of course we could add a none ReplyTo to the copies which would have
the desired effect, but if we do that, it really calls for multiple
messages to be sent at the ServiceClient level rather than relying on
smtp cc, bcc.
Yeah that's an option but that's a different thing. I think the underlying
principle at question is whether a transport impl should restrict any of
the properties of the transport .. my opinion is basically that we should
not. Obviously we should configure it correctly for the default config,
but if an advanced user wants to set a bcc or whatever, we shouldn't get
in the way.
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
