Email anonymizer / redirector

At a high level, I need a system that allows me to generate temporary email addresses linked to real email addresses that I can distribute for temporary use to clients. Basically the client should be able to email someone in our database under restricted and time limited conditions without having visibility into their real email address. The recipient should be able to email back to the client without having visibility to the client's email address. The client should be able to get mail back from the recipient with only the temporary email address replaced back inside it.

Specifically, I need a system that is able to offer the following admin interface and email handling functions:


0) restricted (username, password) access

1) admin able to add/remove admins from the system (username, password)

2) admin able to add/maintain a list of active clients in the system (say McDonalds, Burger King - name only)

admin can set each client to be active/inactive; no delete (clients page)

3) admin able to request a temporary email forwarding address be produced by the system entering: (request token page A)

a) "real" email address (say test/at/[url removed, login to view])

b) selecting a client (say McDonalds)

c) setting an expiry time in days (say 14)

4) system produces an anonymized email address: (request token page B)

test/at/[url removed, login to view], McDonalds, 14 -> a3dfhad3/at/[url removed, login to view]

5) admin can view all active "temporary" email addresses and deactivate any of them manually from the list (view tokens page)

a) 50 views per page in list

b) admin can search tokens by searching active/inactive, client or "real" email address

c) admin can view the number of emails sent to each token

d) admin can click to view the content of each email sent to each token


6) "temporary" emails are uniquely associated with test/at/[url removed, login to view], McDonalds and expires after 14 days.

7) any time someone sends an email to a3dfhad3/at/[url removed, login to view] the following steps are taken:

a) System checks if token email has expired... if so the email is redirected to [url removed, login to view] instead of

b) System checks if client is active .... if not the email is redirected to [url removed, login to view] instead of

c) If client and token is active, mail is forwarded on to the "real" address with the following modifications

i) from & reply-to addresses are also tokenized (client = McDonalds, expiry = 365)

e.g. John Smith < jsmith/at/[url removed, login to view] > => John Smith (McDonalds) < abc123 /at/ [url removed, login to view] >

d) mail content is stored in database associated with token, to enable 5d (above)

NOTE: when a recipient (say Bob Test < test/at/[url removed, login to view] >) replies to an email from John Smith (McDonalds) < abc123 /at/ [url removed, login to view] > , the reply will go back through the anonymizing server because of 7c above. The server should be smart enough to know that this email has come from test/at/[url removed, login to view], with an existing McDonalds token of a3dfhad3/at/[url removed, login to view] so the reply email should be reanonymized with reply-to/from of Bob Test < a3dfhad3/at/[url removed, login to view] >

Compétences : Perl, Architecture Logicielle

en voir plus : system level architecture, mcdonalds com, handling e mail, handling Email, e mail handling, checks in the mail, b. e. smith, architecture of email system, our time has come, email g, tokens, the burger, smart client, Mcdonalds, emails handling, email searching, email handling and, client is not reply me on, forwarded email, real time server architecture, email username password access, mail server setting, real active email address list, password level software, set 365 server

Concernant l'employeur :
( 19 commentaires ) Princeton, Australia

Nº du projet : #2364062

Décerné à:


High Proficiency in Perl together with QA and QC best practices. Post release corrective support is included.

%selectedBids___i_sum_sub_7% %project_currencyDetails_sign_sub_8% USD en 30 jours
(1 Évaluation)

4 freelance font une offre moyenne de $1575 pour ce travail


I can do it.

%bids___i_sum_sub_35% %project_currencyDetails_sign_sub_36% USD en 30 jours
(3 Commentaires)

I'll provide clean and test-driven development. Support for 7days once promote to production.

%bids___i_sum_sub_35% %project_currencyDetails_sign_sub_36% USD en 15 jours
(0 Commentaires)

Hi, I have a good experience in Software development. Please refer my PM. THanks

%bids___i_sum_sub_35% %project_currencyDetails_sign_sub_36% USD en 20 jours
(0 Commentaires)