Am 20.07.26 um 19:50 schrieb Doug Hardie:
Apparently sh and csh versions of echo are different.
Yes, the separate "echo" *executable*
$ which echo
/usr/bin/echo
usually gets superseded by the shell's "echo" builtin. Your csh's
version obviously doesn't support the "-e" (interpret escape sequences)
option.
However, in either case, vi still cannot handle that file.
Hmmmm. Can't reproduce that behaviour with my version of "vi", setting
my $LANG to your value seems not to have an effect. I have to admit that
the interaction between "vi", localization mechanisms, and
(still-)out-of-charset file contents is entirely unknown to me, though,
and suspect that that's where your exact distrib and version may start
to play a role.
I suppose that you could *convert* the file into something "vi" can work
on (note "-c" option to "iconv", in particular), but having to do so
with a *log*file is quite cumbersome IMHO (unless you do something like
a post-mortem deep-dive for a singular event, anyway) ...
Would you happen to have an idea what that e-mail's sender address
was/is being displayed like in the actual e-mail application? If it's
"broken" there as well (because of the external use of codepoints from a
private Unicode range), I'd say that problems processing the logfile
containing the same heavily lean to the "symptom, not cause" side.
(In the same vein, do the MSA's logs show that the recipient ever tried
to *reply* to that e-mail address? If so, what happened to that reply,
did it ever make it to remote servers?)
Kind regards,
--
Jochen Bern
Systemingenieur
Binect GmbH
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
