How to simulate spam mail?

And also the answer is – to try our current mail safety infrastructure.

In a modern mail environment, the necessity for implementing some “security mechanism” which will protect our mail infrastructure from spam mail as well as other threats, start thinking about as being a mandatory need.

Offered I know if our mail security gateway is functioning and how he “react” to the event of spam mail that we implement a mail security gateway; the big question could be – how do?

For instance, a situation in which we define a particular rule in which, whenever our mail protection gateway recognizes spam mail, a notification are sent to a designated recipient and so forth.

The very g d news is that the possibility of fabricating a contact message which will be defined as – “spam mail” is current, and also the utilization of simulating a scenario of “spam mail,” is quite easy.

All we have to do would be to create an email message that includes a predefined text sequence and delivers this email message to the location recipient which is “protected” by our mail protection gateway.

This nice trick is implemented using a unique procedure which was defended by Apache SpamAssassin company.

his is the GTUBE — the Generic Test for Unsolicited Bulk e-mail.

If the spam filter supports it, the GTUBE supplies a test through which you are able to verify that the filter is installed precisely and is detecting incoming spam, in an identical fashion towards the EICAR anti-virus test file.

Spam filter developers should add a rule, where possible, to identify the next string that is 68-byte the message human body, and trigger about it

Observe that this would be reproduced in a single line, without whitespace or line breaks. a mail that is suitable in RFC-822 structure could be downloaded here.

This string and mail could be reproduced easily, without attribution; these are typically hereby put in the domain that is public.

Simulate spam mail

A send spam E-mail message to recipient B in the following section, we will simulate a scenario in which recipient

simulate spam mail | Scenario description

In our scenario, Justin will deliver “spam mail” ( [email protected] ) to a receiver an additional organization known as – Bob ( [email protected] ).

Bob is just a user whom his mailbox is hosted in Office 365 (Exchange Online server).

Sending the spam mail

Into the mail human anatomy, we are going to add the text string that is following

And send the email message.

Getting the spam mail

In the screenshot that is following we can begin to see the E-mail message which was provided for Bob.

Even as we can see, the email message was delivered to the Junk mail folder.

The reason for that is because, in a working office 365 based environment, the component that serves as a mail security gateway is – the EOP (Exchange on line Protection) host.

Each E-mail message that is sent to Office 365 recipient is checked and examined by the EOP server.

EOP recognizes the written text string in the E-mail message, and categorizes the E-mail message as “spam mail,” by setting the worth associated with the SCL (spam self- confidence degree) to “9.” When the email message reaches the recipient mailbox, because the value that is high of SCL, the mail is sent to the spam folder.

Watching and analyzing this content regarding the email message by using email header

In this section, I would like to show the “behind the scenes” associated with the spam E-mail message, therefore I will be in a position to understand better that way that any office 365 EOP server usage for “stamping” specific email message as “spam mail.”

The method for classifying E-mail message as “spam mail” is, by define a particular value in the SCL parameter in Exchange based environment. Within our scenario that is specific Online will set the SCL value to “9”.

Viewing the information for the mail header.

In order to understand given information that is included in the email message, we will be using the OWA mail client. We will “fetch” the content of the mail flingster header regarding the spam mail that was delivered to Bob.