|
|
|
|
|
by kstrauser
1539 days ago
|
|
For the benefit of those fortunate enough to have never had to configure that beast, you can find any number of terrifying examples. Here's one: https://tldp.org/LDP/nag2/x14661.html#X-087-2-SENDMAIL.MC.UU... From that, we see LOCAL_NET_CONFIG
# This rule ensures that all local mail is delivered using the
# smtp transport, everything else will go via the smart host.
R$* < @ $* .$m. > $* $#smtp $@ $2.$m. $: $1 < @ $2.$m. > $3
dnl
Clear as day, right? |
|
anyways, after staring at this for a few minutes and without looking up any syntax, a few things became noticeable:
R$* < @ $* .$m. > $* is matching a pattern, with each $* being assigned to $1, $2 and $3 respectively.
$m must contain the local domain. so effectively this pattern matches any mail addressed to a host with the local domain.
$#smtp if that pattern matches, use smtp,
$@ $2.$m. by connecting to $2.$m. (which means, just use the host that was specified in the original mail)
$: $1 < @ $2.$m. > $3 (not sure what this part does. my guess is: rewrite the email address as specified here, that is in this case don't rewrite it at all.)
it's terse, but regular expressions are worse than this particular example.
now i need to go look up the syntax to see how much i actually got right.
for example i have no idea what the $3 parameter is for. i am guessing $1 is the part before the @ in an email. $3 could be the From address or have something to do with alternate addressing schemes