Mailsecure: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(11 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
Premade's | |||
This is setup for you. | |||
<pre> | |||
Hello, | |||
I have activated MailSecure for the DOMAINHERE domain. You'll begin to see emails coming in with a [spam] tag in the subject line; these are the emails the firewall found to be suspicious or spam-like but were not rejected by the firewall. The firewall will automatically reject emails that are confirmed as spam/viral in nature, so those will not make it to your inbox. | |||
Please let us know if you have any questions or concerns, or if the service is not working as expected. | |||
</pre> | |||
Letting the customer know that we dont have have a way for them to access it. | |||
<pre> | |||
Hello, | |||
Unfortunately, at this time, we do not have a means for customers to view or alter the MailSecure settings. This may be something available in the future, but for the time being, we will need to make any changes on your behalf, and we are always happy to do so. | |||
I have the firewall set up not to block any of the emails, but to put them into the spam folders under the email accounts. | |||
For a few days, I would like you to make sure that none of your legitimate emails are being flagged as spam. Then, once the filter level is working well, we can switch the firewall to block the emails outright, rather than filter them. | |||
Please let me know if you have any further questions or concerns. | |||
</pre> | |||
Let the customer know to update their MX records so we can finish the installation. | |||
<pre> | |||
Hello, | |||
During the course of installing your MailSecure service, I noticed the DNS for this domain is hosted upon a server which is not on our network. Thus, for the service to work correctly, someone with access to update the MX records on that server would need to please change the MX records to the following: | |||
* domain.com . 300 IN MX 0 bmx01.sourcedns.com . | |||
* domain.com . 300 IN MX 0 bmx02.sourcedns.com . | |||
Please let me know once this change has been completed, and I'll be happy to finish the activation process for you. | |||
If you are uncertain as to what an MX record is, or how to change us, please let us know, and we will do our best to provide assistance. | |||
</pre> | |||
What the DNS records need changed to. | |||
domain.com. 300 IN MX 0 bmx01.sourcedns.com. | |||
domain.com. 300 IN MX 0 bmx02.sourcedns.com. | |||
<div class="mw-collapsible mw-collapsed"> | |||
Make domain list(put the domains the want in here) | Make domain list(put the domains the want in here) | ||
vim /root/mailsecurelist | vim /root/mailsecurelist | ||
Run this for loop to use the domain list to backup each domains zone file, then remove the old mx entries, and add the new ones as well as update the ttls and serials all at once. | Run this for loop to use the domain list to backup each domains zone file, then remove the old mx entries, and add the new ones as well as update the ttls and serials all at once. | ||
<pre style="white-space: pre-wrap; | |||
white-space: -moz-pre-wrap; | white-space: -moz-pre-wrap; | ||
white-space: -pre-wrap; | white-space: -pre-wrap; | ||
Line 11: | Line 53: | ||
word-wrap: break-word;">for i in `cat mailsecurelist`; do sed -i.lwbak -e '/IN[[:space:]]*MX/d' /var/named/$i.db; echo "$i. 300 IN MX 0 bmx01.sourcedns.com." >> /var/named/$i.db; echo "$i. 300 IN MX 0 bmx02.sourcedns.com." >> /var/named/$i.db; sed -i -e 's/^\$TTL.*/$TTL 300/g' -e 's/[0-9]\{10\}/'`date +%Y%m%d%H`'/g' /var/named/$i.db; done | word-wrap: break-word;">for i in `cat mailsecurelist`; do sed -i.lwbak -e '/IN[[:space:]]*MX/d' /var/named/$i.db; echo "$i. 300 IN MX 0 bmx01.sourcedns.com." >> /var/named/$i.db; echo "$i. 300 IN MX 0 bmx02.sourcedns.com." >> /var/named/$i.db; sed -i -e 's/^\$TTL.*/$TTL 300/g' -e 's/[0-9]\{10\}/'`date +%Y%m%d%H`'/g' /var/named/$i.db; done | ||
</pre> | </pre> | ||
test work | test work | ||
<pre style="white-space: pre-wrap; | |||
white-space: -moz-pre-wrap; | |||
white-space: -pre-wrap; | |||
white-space: -o-pre-wrap; | |||
word-wrap: break-word;">for i in `cat /root/mailsecurelist`; do grep --color "\$TTL" /var/named/$i.db; grep --color -e '[0-9]\{10\}' /var/named/$i.db; egrep --color 'IN[[:space:]]*MX' /var/named/$i.db; done</pre> | |||
Reload name server. | Reload name server. | ||
rndc reload | rndc reload | ||
</div> |
Latest revision as of 05:18, 30 April 2016
Premade's
This is setup for you.
Hello, I have activated MailSecure for the DOMAINHERE domain. You'll begin to see emails coming in with a [spam] tag in the subject line; these are the emails the firewall found to be suspicious or spam-like but were not rejected by the firewall. The firewall will automatically reject emails that are confirmed as spam/viral in nature, so those will not make it to your inbox. Please let us know if you have any questions or concerns, or if the service is not working as expected.
Letting the customer know that we dont have have a way for them to access it.
Hello, Unfortunately, at this time, we do not have a means for customers to view or alter the MailSecure settings. This may be something available in the future, but for the time being, we will need to make any changes on your behalf, and we are always happy to do so. I have the firewall set up not to block any of the emails, but to put them into the spam folders under the email accounts. For a few days, I would like you to make sure that none of your legitimate emails are being flagged as spam. Then, once the filter level is working well, we can switch the firewall to block the emails outright, rather than filter them. Please let me know if you have any further questions or concerns.
Let the customer know to update their MX records so we can finish the installation.
Hello, During the course of installing your MailSecure service, I noticed the DNS for this domain is hosted upon a server which is not on our network. Thus, for the service to work correctly, someone with access to update the MX records on that server would need to please change the MX records to the following: * domain.com . 300 IN MX 0 bmx01.sourcedns.com . * domain.com . 300 IN MX 0 bmx02.sourcedns.com . Please let me know once this change has been completed, and I'll be happy to finish the activation process for you. If you are uncertain as to what an MX record is, or how to change us, please let us know, and we will do our best to provide assistance.
What the DNS records need changed to.
domain.com. 300 IN MX 0 bmx01.sourcedns.com. domain.com. 300 IN MX 0 bmx02.sourcedns.com.
Make domain list(put the domains the want in here)
vim /root/mailsecurelist
Run this for loop to use the domain list to backup each domains zone file, then remove the old mx entries, and add the new ones as well as update the ttls and serials all at once.
for i in `cat mailsecurelist`; do sed -i.lwbak -e '/IN[[:space:]]*MX/d' /var/named/$i.db; echo "$i. 300 IN MX 0 bmx01.sourcedns.com." >> /var/named/$i.db; echo "$i. 300 IN MX 0 bmx02.sourcedns.com." >> /var/named/$i.db; sed -i -e 's/^\$TTL.*/$TTL 300/g' -e 's/[0-9]\{10\}/'`date +%Y%m%d%H`'/g' /var/named/$i.db; done
test work
for i in `cat /root/mailsecurelist`; do grep --color "\$TTL" /var/named/$i.db; grep --color -e '[0-9]\{10\}' /var/named/$i.db; egrep --color 'IN[[:space:]]*MX' /var/named/$i.db; done
Reload name server.
rndc reload