Page 57 - ASBIRES-2017_Preceedings

AVOID EMAIL SPAMMING BY SERVER AUTHENTICATION AND SAILJS ORM

5 RESULTS Table 1: Details of spamming before
implement
The result obtained before applying
proposed method, are shown in Figure 2. Identifier Pass/Fail
This indicates that the probability of not SPF Fail
being spammed is 6 out of 10.This is highly DKIM Fail
based on the statistical methods used in the
online spam checker software. SenderID Fail

SpamAssasin Pass
API Pass
Priority issue Resolution Fail

After applying the proposed method
the final results are shown in table 2. It can
be noted that emails are not blacklisted and
method is successfully implemented.

Table 2: Results which was taken after
applying the proposed method

Identifier Pass/Fail

SPF Pass
Figure 2: Results of spam filters DKIM Pass

Before applying proposed method SenderID Pass
the pass fail ratio of different kind of keys SpamAssasin Pass
and records of the current system are shown API Pass
in Figure 3. It depicts that the SPF and Priority issue Resolutio Pass
DKIM records which are failed to find
during the email sending process. 6 DISCUSSION

6.1 Strength of the System
 Provide attractive and user friendly
interfaces which enriches the applying
process.
 Avoid spamming to all kinds of email
templates
 Timestamp error were resolved
 Very efficient and accurate system - there
are no good systems found or Coding
procedures on the internet used in the
modern world developed using Sails.JS
and waterline Object Relational Mapping
Figure 3: Result sheet to solve this problem. Before applying
these method lots of complaints were
Before applying propose method, received from the users. But after using
full detailed description of the company’s Sails.JS new method email spamming
specific domain with the details and failures problem was solved.
are shown in Table1.

47