i wrote:
|i wrote:
||SZÉPE Viktor wrote:
| ...
|||s-nail is very popular, it is included in my Debian server deployment \
|||script!
|||https://github.com/szepeviktor/debian-server-tools/blob/master/debian-setu\
|||p\
|||2\
|||.sh#L41
|
|While looking some more, i have some suggestions for possible
|improvements, just in case i understand your concerns right.
...
|In monitoring/cse/can-send-email.sh, ohwowwow! Despite said
|address errors there is:
...
| LC_ALL=C s-nail -:/ -Ssendwait -Sttycharset=utf8 \
| -s "[cse] bounce message / Hüh-hüpf" \
| -r "${CSE_ADDRESS}" "$RECIPIENT" \
||| echo "Trigger failed ($?) for ${URL}"
Even better if option processing is explicitly terminated and send
mode forced via -. as in
LC_ALL=C s-nail -:/ -Ssendwait -Sttycharset=utf8 \
-s "[cse] bounce message / Hüh-hüpf" \
-r "${CSE_ADDRESS}" -. \
"$RECIPIENT"
I think i will make "fail" the default for *expandargv*.
Maybe invalid addresses in *from* should cause the same hard error
as setting an invalid address via -r, on the other hand s-nail
error logs and why wouldn't you ensure an acceptible setting in
*from*? The problem is that the function in question was never
able to return a hard error, what it reports as an "error" is just
seen as "leave the task of detecting who is 'from' to the MTA"!
However, i have fixed an error in that the faulty *from* is
returned as NULL and so in an SMTP configuration you will see
s-nail: An address given in *from* is invalid: bla <CSE>
s-nail: Your configuration requires a *from* address, but none was given
s-nail: >>> Would (try to) write $DEAD /home/steffen/dead.letter
s-nail: ... message not sent
in that situation. Pushed as [c59a20ff] to [master] etc.
Thanks!
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
