I'm not sure whether that was intentional or
not, but as best I can figure out, your example
is, indeed, valid Perl syntax. Hang on...
*checks* indeed it is.
The long, boring explanation: Take the hash
%Magical, look up the key 'Perl' in it. The
value will be a reference to an array. You then
take the element of the array with index
corresponding to the highest index of the array
to which $syntax holds a reference. The result
is either the name of an existing hash or a
reference to one. The result of the expression
is a reference to the hash so determined.
First off, RFCs 821 and 822 have already been
rewritten; check RFCs 2821 and 2822 at your
friendly neighbourhood RFC repository.
And I wouldn't consider the rule "Reply-To
must match the IP or domain of the incoming
connection" to be very good. What about
forwarding addresses? Say, someone has an
account with abc@example.com which actually
forwards to realaddress@isp.net. Then that
person may send out mail from isp.net's mail
servers with a "From" and/or "Reply-To" of
abc@example.com -- but it's still his address
even though the domains don't match at all!
Not really. You don't need to run your own
mail server to be able to operate a domain of
your own -- there are lots of companies out there
that are willing to host email for you, and
it shouldn't cost too much, either. So you could
register, say, myfavouritedomain.com with
somebody and this company (often even the
domain registrars offer services like this)
could be set to send mail to
<anything>@myfavouritedomain.com to
myrealaddress@dialup-isp.net . Or perhaps they
only permit five POP3 mailboxes if they're cheap,
but that doesn't stop you calling one of them
"abuse" and then polling it from your dialup
account.
Something similar works fine for me; I use
a dialup ISP and have a couple of vanity domains,
one of which is my primary email domain for
making up tracked email addresses and the
like.
A good idea in principle, but you'll end up
looking clueless to people who think that role
accounts should be used for those roles.
Like the respect that is given in, say, Linux
support newsgroups to people posting from
root@example.com -- many may reply "don't do
everything as root". Similarly, I'd consider
that postmaster, abuse, and other role accounts
shouldn't be used for general things.
Slashdot Mirror
I'm not sure whether that was intentional or not, but as best I can figure out, your example is, indeed, valid Perl syntax. Hang on... *checks* indeed it is.
The long, boring explanation: Take the hash %Magical, look up the key 'Perl' in it. The value will be a reference to an array. You then take the element of the array with index corresponding to the highest index of the array to which $syntax holds a reference. The result is either the name of an existing hash or a reference to one. The result of the expression is a reference to the hash so determined.
First off, RFCs 821 and 822 have already been rewritten; check RFCs 2821 and 2822 at your friendly neighbourhood RFC repository.
And I wouldn't consider the rule "Reply-To must match the IP or domain of the incoming connection" to be very good. What about forwarding addresses? Say, someone has an account with abc@example.com which actually forwards to realaddress@isp.net. Then that person may send out mail from isp.net's mail servers with a "From" and/or "Reply-To" of abc@example.com -- but it's still his address even though the domains don't match at all!
Not really. You don't need to run your own mail server to be able to operate a domain of your own -- there are lots of companies out there that are willing to host email for you, and it shouldn't cost too much, either. So you could register, say, myfavouritedomain.com with somebody and this company (often even the domain registrars offer services like this) could be set to send mail to <anything>@myfavouritedomain.com to myrealaddress@dialup-isp.net . Or perhaps they only permit five POP3 mailboxes if they're cheap, but that doesn't stop you calling one of them "abuse" and then polling it from your dialup account.
Something similar works fine for me; I use a dialup ISP and have a couple of vanity domains, one of which is my primary email domain for making up tracked email addresses and the like.
A good idea in principle, but you'll end up looking clueless to people who think that role accounts should be used for those roles.
Like the respect that is given in, say, Linux support newsgroups to people posting from root@example.com -- many may reply "don't do everything as root". Similarly, I'd consider that postmaster, abuse, and other role accounts shouldn't be used for general things.
Other than that, it sounds useful :)
Which OS is Theo de Raadt's?