System and method for an email firewall and use thereof

• US 20070033258A1
• Filed: 07/28/2006
• Published: 02/08/2007
• Est. Priority Date: 08/04/2005
• Status: Abandoned Application

• Current Assignee: Internet Software Architects, Inc.
• Original Assignee: Internet Software Architects, Inc.
• Inventors: Devi, Murali, Vasilaky, Walter
• Application Number:
  US11/495,476
• Publication Number:
  US 20070033258A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/212 using filtering or selective blocking

Abstract

One aspect of the present invention provides an Email Firewall system and/or method, which is a system for selective delivery of electronic mail (email), within the framework of conventional email protocols, and authentication of the source of electronic mail, with an objective of blocking unwanted email. In one embodiment of the present invention, the system resembles a firewall in the sense that the Email Firewall checks if the sender has “clearance” before forwarding the email message to the recipient and a means for providing “clearance”.

Claims

1. A method for an email firewall in a client-server environment where a sender using an email client emails an email from an associated source email address to a destination email address associated with a recipient, the method comprising the steps of:

providing the sender with a privatized recipient email address that the sender can use for emailing email to the recipient via an email networking infrastructure, said privatized recipient email address being configured to be operable, from designated source address(es), for enabling the email networking infrastructure to direct an email addressed to said privatized recipient email address to a firewalled destination email server; and

upon receiving an email addressed to said privatized recipient email address, said firewalled destination email server validating that the received email was sent from a registered sender address at least by searching a validation database for the sender'"'"'s email address and the associated privatized recipient'"'"'s email address, and if the sender'"'"'s email address and the associated privatized email address are found, replacing said privatized recipient email address with a public email address associated with the recipient and forwarding said received email for delivery to the recipient'"'"'s email server and subsequently to the recipient'"'"'s email client.

2. The email firewall method of claim 1, further comprising the Step of if after searching said validation database for the sender'"'"'s email address the sender'"'"'s email address is not found, sending an email to the sender indicating the email was blocked and optionally providing information on how to register.

3. The email firewall method of claim 1, in which, the Step of registering comprises the Step of after the sender registers, emailing said privatized recipient email address to the sender'"'"'s email address.

4. The email firewall method of claim 1, in which, generating said privatized recipient email address comprises the Step of embedding a unique identifier into the destination email address.

5. The email firewall method of claim 4, in which, replacing said privatized recipient email address with a public email address comprises the Step of removing said unique embedded identifier alter it is verified by said email firewall.

6. The email firewall method of claim 1, in which, the email networking infrastructure is a conventional fundamental store-and-forward model within the framework of conventional email protocols.

7. The email firewall method of claim 1, in which, email sender is not a subscriber to a service based on said email firewall method, and the email recipient is such a subscriber.

8. A method for an email firewall in a client-server environment where a sender, having a public source email address protected by an email firewall and using an email client, emails an to a destination email address, not protected by an email firewall, associated with a recipient, the method comprising the steps of:

a firewalled source email server checks a validation database to determine if the destination address is in the validation database;

if the destination address is not in the validation database, the email-firewall generating a privatized return address associated with the source public address and the recipient'"'"'s email address and enters them into said validation database;

if the destination address is in the validation database, the email-firewall retrieves a return private address associated with the destination address from the validation database;

replacing the public return address associated with the sender with said privatized return address, thereby enabling the email to be emailed via an email networking infrastructure to the destination address;

encrypting the public source address and inserting it into a hidden header field, said hidden header field being configured Such that said hidden header field will be ignored by all email transfer agents except for a destination email server is an email-firewall server of the present method; and

reconfiguring said return privatized email address to be operable for enabling the email networking infrastructure to direct a reply email sent from the recipient back to said firewalled source email client.

9. The email firewall method of claim 8, in which, generating said privatized sender email address comprises the Step of embedding a unique identifier into the local part of the public source email address associated with the sender.

10. The email firewall method of claim 8, in which, the email-firewall encrypts the public source address and inserts the encrypted address in a hidden email header field;

the encrypted header file will be ignored by all email transfer agents and the destination email server unless the destination server is a firewall email server.

11. The email firewall method of claim 8, in which, the email networking infrastructure is a conventional fundamental store-and-forward model within the framework of conventional email protocols.

12. The email firewall method of claim 8, in which, email recipient is not a subscriber to a service based on said email firewall method, and the email sender is such a subscriber.

13. A method for an email firewall in a client-server environment where a sender using an email client emails an email having a public source email address protected by an email firewall to a public destination email address protected by an email firewall associated with a recipients the method comprising the steps of

a firewalled source email server checking, a first (source) validation database for the destination address;

if the destination address is not in the validation database, the email-firewall generating a privatized return address associated comprising the source public address and the recipient'"'"'s email address;

storing said privatized return address into said validation database;

replacing the public return address associated with the sender with said privatized return address, thereby enabling the email to be emailed via an email networking infrastructure to the destination address;

encrypting the public source address and inserting it into a hidden header field, said hidden header field being configured such that said hidden header field will be ignored by all email transfer agents except for a destination email server is an email-firewall server of the present method; and

reconfiguring said return privatized email address to be operable for enabling the email networking infrastructure to direct a reply email sent from the recipient back to said firewalled source email client.

14. The email firewall method of claim 13, further comprising the Steps of providing the recipient email firewall with a privatized return email address that the recipient Firewall can use for emailing email back to the sender firewall via the email networking infrastructure, said privatized sender email address being configured to be operable for enabling the email networking infrastructure to direct an email addressed to said privatized sender email firewall:

upon receiving an email said firewalled recipient'"'"'s email server searching if the received email was sent from a sender email address that is registered in a validation database associated therewith;

if not found, checking for said encrypted hidden header field;

if the encrypted header field is found, generating a private address associated with the decrypted public address of the sender;

storing in a validation database associated with said firewalled recipient'"'"'s email server, said generated private address and said decrypted public source address;

storing in a validation database associated with said firewalled recipient'"'"'s email server, said privatized source address and the destination public address;

said firewalled recipient'"'"'s email server transmitting the sender using the sender'"'"'s private address and the associated private return address with the associated encrypted public address in a hidden header field, the sent email being operable as a verified email that is from a legitimate source address, as confirmed by the encrypted hidden header field; and

transmitting said verified email to the recipient email server, which in turn forwards it to the recipient client.

15. The email firewall method of claim 14, further comprising the Steps of said sender firewall Upon receiving the automated return message from the recipient firewall checks that it is a message from a firewall by checking the encrypted hidden header field and further checks its validation database if the private return address is in the database and if not stores the return private address together with the associated sender'"'"'s public address and the decrypted recipient'"'"'s public address The sender and the recipient can from now on communicate using public address because the firewall logic in each firewall can look up the respective private address in their respective validation databases.

16. The email firewall method of claim 15, where the firewalled source email server checks the first (source) validation database if the destination address is in the validation database. If the destination address is in the validation database, the firewall logic retrieves the corresponding, destination private address, the return private address and the return pubic address and inserts them into the To:

header field, the From;

header field and, the hidden encrypted header field respectively and forwards the message to the destination; and

, upon the arrival of the email at the destination firewall the destination private address is validated at the second (destination) validation database, the private addresses are replaced by their corresponding public addresses in the To; and

From;

header fields and the email is forwarded to the recipient email server which in turn forwards the email to the recipient email client.

17. The email firewall method of claim 15, in which said hidden header field is configured such that it Would be ignored by email transfer agents comprised in the email networking infrastructure but can be parsed by the destination email firewall software of said email firewall method.

18. The email firewall method of claim 15, when the recipient email firewall detects through the encrypted header field that the email is from an email firewall can optionally switch to communication via a secure socket layer.

19. The email method of claim 18, is such that it is does not require a central database to keep track of all the installed email firewalls:

A firewall can detect a message from another firewall by checking for an encrypted header field.

20. The email method of claim 13 retrieves the destination private address and the return private address from the validation database and places them in the respective To:

and From;

header fields for outgoing mail and for incoming mail the destination firewall logic removes the private addresses and replaces them with their corresponding public address before forwarding the email to the destination email server;

this renders communication between firewalls to be completely transparent.

21. The email method of claim 18 can optionally switch to a secure socket layer communication once the destination email firewall determines that a message is from an email firewall.