[Info-vax] Latest TCPIP Services seem irreparably horked...

VAXman- at SendSpamHere.ORG VAXman- at SendSpamHere.ORG
Sat Mar 3 17:22:21 EST 2012


In article <4f5295aa$0$59184$c3e8da3$dbd57e7 at news.astraweb.com>, JF Mezei <jfmezei.spamnot at vaxination.ca> writes:
>VAXman- @SendSpamHere.ORG wrote:
>
>> I have seen an issue with sftp/ssh.  Hoever, to belie Mr. Mezei's cluster
>> theory, this is on a standalone node.
>
>
>OK, thinking about it, the TOP_HEADERS would be done by the receiver
>when a message arrives.

Precisely!



>The pop server doesn't need to know this because it needs to be able to
>also parse native VMS messages without RFC822 headers and synthetise
>headers if there are none.

Precisely!



>Mr Vaxman, if you gosub MAIL and extract a message to tt: , do you see
>the RFC822 header at the top ?


I see the problem in the POP client.  When I ask the POP client to show
me the header, it shows me the VMS header.  The RFC822 header content it
part of the message and this is the problem.



>Also this has apparently been fixed, but it used to be that if you had a
>line longer tan 255 characters in the RFC header, the SMTP receiver
>woudl split the line in two, causing an invalid RFC header and the POP
>server would then synthetie a new header and use that one as part of the
>message contents (making it impossible to parse attachements)

Dunno.  Send me one! :)

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.



More information about the Info-vax mailing list