Today I made a couple of small tweaks to my systems. First of all I updated my email handling to allow further restrictions to be applied to incoming mail.
Generally the way I handle incoming mail is to first of all test the recipient, then apply spam checks. To allow mail for a new localpart to be received I'll run this:
cd /srv/example.com/users/valid touch localpart
The result of the file /srv/example.com/users/valid/localpart existing is that mail is accepted for [email protected].
As of today that still works - any file beneath users/valid allows the appropriate localpart to receive email. But now a directory indicates an ACL. So I can create:
rm /srv/example.com/users/valid/root mkdir /srv/example.com/users/valid/root/ touch /srv/example.com/users/valid/root/1.2.3.4 touch /srv/example.com/users/valid/root/2.3.4.5
Now only the named IP addresses may mail [email protected].
Finally I updated the proxy which is handling incoming access to my websites, so that I actually take advantage of the regular expression support.
'(xen-hosting.net|www.xen-hosting.net)': {
'rules': {
'^/': 'http://kvm-hosting.org/'
},
},
'(xen-hosting.org|www.xen-hosting.org)': {
'rules': {
'^/': 'http://kvm-hosting.org/'
},
},
Using regular expressions meant that I didn't have seperate matches for xen-hosting.org and www.xen-hosting.org. (Obviously I could have combined all four hosts into one regexp, but it looks cleaner this way.)
ObQuote: "Nobody likes a perky goth" - Blood Ties.
Tags: ms-lite, node-reverse-proxy, nodejs No comments