The next auditing technique that we are going to talk about is e-mail logs.
In fact the e-mail logs is one of the technique for auditing which we can use for e-mail information
for tracking all the e-mail information.
So basically these e-mail logs they have.
They include information about the for every single man we have the sender information the recipient
information date time delivery status whether it was delivered successfully or if there is any error
and if yes if there are any errors then what does the associate editor codes.
So all this information they are London e-mail logs so I don't see any admin whenever you are facing
any issue regarding emails saying that the e-mail notifications we not sent to some particular user
are.
If you if you really want to check if e-mails are getting delivered properly this would be the first
place for you to check generating e-mail logs and checking out if all the e mails are getting sent out
properly.
E-mail logs will be of great help.
So now let's see and cesspools help generate these e-mail logs.
So this is a letter that we put in addition here look for e-mail logs
under logs you will have e-mail log files and a note that this e-mail log feature this is available
only for those users with modify all data upload mission.
So basically admins would have that.
So arguments can generate requests for e-mail logs and a venue request for an e-mail logs in sales force
these e-mail logs are available only went for the past 30 days.
So basically if you choose
so this is the maximum that is available.
That is only for the last 30 days.
All the e-mail conversations they are recorded incestuous and flawed.
One particular e-mail log request the maximum duration that we can request for this seven days.
So that does what is mentioned here.
So for at most seven days we can delete e-mail log request but assets to the whole e-mail logs they
are available for all 30 days.
So if you want for multiple durations and you have to request multiple logs accordingly and here you
also have a say that include one of the e-mails I got our to and from.
So what if you are interested in a particular user or if you are looking only for some e mails that
are sent to or from or a particular domain then you can include only those e-mails and all those emails
are the domain names they should be separated by commas so then you give all this information and you
submit that request the e-mail logs will get generated.
And as I mentioned the e-mails are available for 30 days.
However one e-mail log request it can span only to a maximum of seven days.
So here and all that like it's more than seven days yes.
So it seems like you know it is incorrect and it is asking me to correct information so let me modify
the stop a mind.
In time I have done that so that it spans only seven days.
Now I hit submit request for effect.
So now it says the request is submitted your log request is successfully submitted and a notification
will send to the E.
Then the log file is available for download and you can see that it is under pending because we have
only submitted a request and it will be available based on the data.
And once that law files are successfully generated you will also get an e-mail notification from the
same and now after a few minutes I got an email notification saying that the email log successfully
generated and we can see that here.
So let me download that and this is the CSB find that God generated this being a pretty new order that
we do not have basically have any email conversations as such.
But I still wanted to show you the CSP five because Fisher know what all the details I got captured
in the email logs we see that the sender details the recipe and details and which stands for dot com
user and I like what does a delivery stage.
So basically in fact like all the details of electrical and an email.
So everything is captured in email logs.
Maybe let's go to some of the important ones.
Phyllis is the dateline.
Basically the date and the time the message was sent and all this date and time is recorded in GMT.
The incoming message I.T. is the unique internal I.T. of the message.
There are some system generated I.T. as such.
And this email even to something that is so very important and this is very much readable does mail
even it will indicate what does the find them maybe even in the mail said look something like a deception
if it is a deception it means that the e-mail was successfully received it's Fitz's a delivery that
e-mail was successfully sent out if there is any failure during the transmission then it would say a
transient failure or if it is permanently fair then it would say a prominent failure.
So it does may leave into this column is actually pretty much readable.
And there's a recipe to send that information as the name says the recipe and information and then send
it in for me.
The remote host basically the IP address of the application server that was the e-mail to the email
server and the bytes transfer that would be the size of the e-mail Salesforce dot com you said even
this is an important to information out here.
This is the salesforce idea of the user who sent the IMET and the message I.T. header.
Again not just saw system generated.
Basically do we have the I.T. head that at the beginning of every e-mail and the reach icon.
So whenever the message just gets fed Salesforce every tries to deliver the message.
So the e-trade called will be the number of attempts made to deliver the e mail the second zero and
how long it has been in that stage and the delivery stage.
So delivery stage will basically indicate at the stage of the delivery just before this email log was
requested.
So just before when the e-mail log those requests are generated what does this day delivery stage of
that particular be met.
And that really addresses again specific tool or system generated information.
So so as I mentioned earlier.
So all of this information related to e-mails they are recorded in e-mail logs so as a senior admin
it is definitely a very essential tool that we can use whenever we choose this.