that is somewhat overly complex. why not require all the resellers to put on their subject account number and webpage and than add their subject. Use perl to sort your email by account for verification and autorespond for receipt. You can respond appropriately. The idea of unique key, etc is one more thing a reseller doesn't need to memorize or write down. The idea of support is suppose to be transparent and not a process.
----- Original Message ----- From: "Dave Warren" <[EMAIL PROTECTED]> To: "Charles Daminato" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, April 16, 2002 12:05 AM Subject: Re: [EMAIL PROTECTED] > I was actually thinking of a unique key used only for support email. > Doesn't even have to be a MD5 hash, come up with some formula for > hashing an RSP's name into 8 characters, or assign random strings... > Just can't be something guessable, lest a malicious RSP abuse the format. > > The principle, unique addresses, with an automatic priority drop once > abused, would allow RSPs to be penalized if they share the support > address without compromising other RSPs. > > Charles Daminato wrote: > > Of course, this means that you're sending your md5hash key in plain text, > > and if you send it to the wrong address... > > > > *eep* > > > > Charles Daminato > > TUCOWS Product Manager > > [EMAIL PROTECTED] > > > > On Mon, 15 Apr 2002, Dave Warren wrote: > > > > > >>The new secret support address should be > >><md5hash-RSPname>@rspsupport.opensrs.net and should only accept email > >>from an RSP supplied list of authorized RSP representatives. > >> > >>Any mail which is sent to an invalid address @rspsupport.opensrs.net or > >>which comes from an unauthorized address should be dropped into the low > >>priority [EMAIL PROTECTED] address. > >> > >>If anybody gives out their private support address, you simply route > >>them into the main pool from then on. Problem solved. > >> > >>But I'm not a bitter support monkey, noooooo no. > >> > >>Charles Daminato wrote: > >> > >>>Yeah, we were - some people make mistakes occasionally. Don't worry, the > >>>next address will be virtually impossible to actually type without a dvorak > >>>keyboard so you'll have to cut and paste it from the reseller's interface or > >>>enter it into your address book so it'll be harder to ruin ;) > >>> > >>>We've made it a policy, also, to explicitly not answer end user questions > >>>when sent to that particular address, but frankly, sometimes it's hard to > >>>tell :) > >>> > >>>Remember, if it leaks too much, the only people that really get harmed are > >>>resellers. I appreciate you "chuck-ifying" the address below in your reply > >>>(which everyone should to in order to prevent further mistakes) > >>> > >>>Ross - no comments from you! ;) > >> > >>-- > >>The nice thing about standards, there is enough for everyone to have their own. > >> > >> > >> > > > > > > -- > The nice thing about standards, there is enough for everyone to have their own. > > >
