Browse Prior Art Database

Method and System of Email Filtering for Spam Using LDAP Schema

IP.com Disclosure Number: IPCOM000174819D
Original Publication Date: 2008-Sep-26
Included in the Prior Art Database: 2008-Sep-26
Document File: 9 page(s) / 201K

Publishing Venue

IBM

Abstract

Disclosed is a mechanism to extend directory server schema in such a way that directory servers can cater to SPAM FILTERING in Email Environments. A directory server is an implementation of the LDAP protocol. It is basically a read-centric repository, wherein customers can store any kind of data viz. users, applications, files, printers, network resources etc. The most common use of directory servers is authentication and authorization. By means of this disclosure, SPAM FILTERING is also added to the list of capabilities of the directory server.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 20% of the total text.

Page 1 of 9

Method and System of Email Filtering for Spam Using LDAP Schema

          Authors
Ramakrishna J Gorthi, Chandrajit G Joshi, Romil J Shah

Disclosed is a mechanism to extend directory server schema in such a way that directory servers can cater to SPAM FILTERING in Email Environments. A directory server is an implementation of the LDAP protocol. It is basically a read-centric repository, wherein customers can store any kind of data viz. users, applications, files,

printers, network resources etc. The most common use

of directory servers is authentication and authorization. By means of this disclosure, SPAM FILTERING is also added to the list of the capabilities of the directory server.

LDAP schema is a set of rules that governs the way data can be stored in a directory. Schema is the backbone of all entries in the directory server. Schema defines the type of entries allowed, their attribute structure and the syntax of the attributes. Schema comprises of object class definitions, attribute type definitions, syntax definitions and matching rule definitions.

Typical Deployment of Directory Servers in Email Environments:

Shown below is a figure of a typical deployment of directory server in email environment.

in

DB

the mail

Mail Database

7. Save

6. OK

5. OK

Mail Server

1. Validate

Email Validation Engine

Spam& Virus Filtering Component

Incoming Mail

4. Check for Spam& Virus

3. OK

2. Authenticate

Directory Server

When the mail server receives an email, following tasks are performed before saving the mail in the database:

Mail server offloads the task of validation of an email to an

Email Validation Engine.

The

Email Validation Engine

asks the directory server to authenticate the mail ID of the

1

Page 2 of 9

recipient i.e. it asks the directory server to check if the email address present in the "To" field is / are existing.

If the reply is OK, it asks the Spam Filtering Component to validate the mail i.e. whether it is conforming to the rules set for a valid email. The rules could include, but are not limited to:

Total size of email should not exceed a threshold.

o
Email attachment size should not exceed a threshold.

o
Sender email ID should not be one of a specific predefined set.

o
Contents of Subject field should not contain one or more of a specific predefined

o

set of words.

Contents of the email body should not contain one or more of a specific

o

predefined set of words.

Extension of email attachments should not be one of a specific predefined set.

o


If the filtering component's reply is OK, the email is saved in the database.

As seen above, the directory servers seem to be used mainly for authentication, authorization and email account management. This disclosure proposes a method for Spam Filtering in Email

Environments

using Directory Server.

Both these implementations share the following characteristics:

A special schema file is shipped along with the regular schema files of a directory server. This f...