[Devel] Provisioning
I'm curious... Is it on purpose that there's no provisioning check of the sender but only of the recipient? -- Sren Hansen [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature ___ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
[Devel] CVS access
Hello All, I am pleased to announce that the CVS repository is now ready for prime time. Repository is /cvsroot/mbuni/ on cvs.sf.net and we will be using this for development. Please note however that http://mbuni.sf.net/ may be a couple of steps behind the main site. Do let me know if you experience any problems. Short primer: For anonymous access: cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/mbuni login then followed by cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/mbuni co mbuni ___ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
Re: [Devel] Provisioning
fre, 11 03 2005 kl. 08:05 +0300, skrev Paul Bagyenda: It is on purpose. The thinking was: why should we check that the sender is provisioned? If they can send, then we know they are. The way I see it, if they can send, they've guessed the URL for our MMSC. That doesn't necessarily mean that they should be allowed to use the MMSC... Or how would you block that? Can the billing module return an error somehow? -- Sren Hansen [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature ___ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
