[英]Advantage of uuencode over mailx -a
当我们可以通过mail -a
或mailx -a
附加文件时, uuencode
提供的特殊优势是什么。
Maybe you have a mailx
with a -a
option, but you're writing a script that should be portable to an older unix without it. 也许您有一个带有-a
选项的mailx
,但是您正在编写一个脚本,如果没有该脚本,它可以移植到较旧的unix中。
Maybe you just have an old script you're maintaining. 也许您只是要维护一个旧脚本。
Maybe you're sneaking something past a mail filter that blocks MIME attachments. 也许您正在通过阻止MIME附件的邮件过滤器潜行。
Maybe you're actually making productive use of the permissions in the uuencode begin
line. 也许您实际上是在uuencode begin
行中有效地使用权限。
Maybe you're sending to a recipient that finds uudecode easier than MIME parsing (such a recipient would probably be a unix-based bot of some sort). 也许您正在发送给发现uudecode比MIME解析更容易的收件人(这样的收件人可能是某种基于Unix的bot)。
It's maybe an easy to understand educational example for people learning about pipes. 对于学习管道的人们来说,这可能是一个易于理解的教育示例。
In general, if you have no technical or personal connection to the pre-MIME mail system of the early 90's, nobody expects you to use uuencode, at least for mail purposes. 通常,如果您与90年代初的MIME之前的邮件系统没有任何技术或个人联系,那么没有人希望您至少在邮件目的上使用uuencode。 You might still use it if you have to cram a file transfer through some other text interface, like a serial console. 如果您必须通过其他文本界面(例如串行控制台)填充文件传输,则可能仍会使用它。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.