>> can users really expect fetchmail to use the same syntax rules as the FTP client?
> Re 3 - Yes, users can expect as much
When attempting to escape quote characters using a backslash (“…\'…”), fetchmail does not treat the quote char as literal (it probably treats the backslash as literal). According to Tim Ruehsen, netkit-ftp treats the backslash as an escape so the char that follows it is taken literally:
If that’s true, then it would be wrong for fetchmail docs to simply refer to netkit-ftp docs (even if netkit-ftp is installed). The netrc man page in the FTP pkg currently only gives a partial spec for .netrc as it neglects password syntax. But what if one day they were to correct that oversight and explicitly state that the backslash is an escape char?
Perhaps the fetchmail man page should say something like:
“See the ftp(1) man page for the general layout of the ~/.netrc file, but not for password syntax.”
>> can users really expect fetchmail to use the same syntax rules as the FTP client?
> Re 3 - Yes, users can expect as much
When attempting to escape quote characters using a backslash (“…\'…”), fetchmail does not treat the quote char as literal (it probably treats the backslash as literal). According to Tim Ruehsen, netkit-ftp treats the backslash as an escape so the char that follows it is taken literally:
https:/ /savannah. gnu.org/ bugs/index. php?62586# comment1
If that’s true, then it would be wrong for fetchmail docs to simply refer to netkit-ftp docs (even if netkit-ftp is installed). The netrc man page in the FTP pkg currently only gives a partial spec for .netrc as it neglects password syntax. But what if one day they were to correct that oversight and explicitly state that the backslash is an escape char?
Perhaps the fetchmail man page should say something like:
“See the ftp(1) man page for the general layout of the ~/.netrc file, but not for password syntax.”