Thank you Scott (Jones) and Charles (Mougel), Scott's scheme does not quite work. Without change I get:
** User Error: Server error: tcp 550 Sender address is invalid ** Near: insert port reduce data ------ If I do not encode "myusername" I get: ** User Error: Server error: tcp 535 Authentication failed ** Near: smtp-port: open [scheme: 'smtp] ----- But (very, very strange) I get the same result if I encode "myusername" but do not encode "mypassword". ------ I will experiment some more and let you know. ------ But somehow it must be kind of a standard protocol. Because both the Mozilla mail client and Outlook Express do it with no problems at all. ------ Regards Steffen ++++++++++ Jones, Scott wrote: > Behalf Of Steffen Pedersen > >>My internetprovider wants me to use "asmpt"=20 >>when sending email. (Instead of "smpt").=20 >>For security reasons. This means I have to=20 >>provide "username" and "password" when=20 >>establishing contact to the "outgoing mailserver". >>... >>But, how do I do this in the Rebol send-function? > > > Hi, Steffen, > > The ease with which this can be done may depend on which=20 > SMTP server your provider is using. The most common=20 > request has been for Microsoft's Exchange server which=20 > may be set to its extended SMTP mode requiring encoded=20 > authentication. The following patch should work for that=20 > server (watch for line wrap): > > system/schemes/smtp/handler/open-check: [none "220"=20 > ["EHLO" system/network/host] "250" "AUTH LOGIN"=20 > "334" [port/user] "334" [port/pass] "235"] > system/schemes/smtp/user: copy enbase/base myusername 64 > system/schemes/smtp/pass: copy enbase/base mypassword 64 > > ;...in which myusername and mypassword are set appropriately > > This method alters the current running copy of the protocol=20 > scheme that manages the SMTP connection. It tests with=20 > the extended HELO command, "EHLO", for the extended SMTP=20 > command set. Exchange frequently uses the "AUTH LOGIN" for=20 > encoded authentication. The script looks for this option=20 > and then offers the base 64 encoded version of the username=20 > and password. E-mail is then sent using the standard 'SEND=20 > command. > > However, there is no standardization of extended SMTP, and=20 > so many varieties exists. In theory, there is a work around=20 > for many or most; however, the list ran into one 3 months=20 > back that used a variety of SSL that did not have an "easy"=20 > work around. > > If the above script fragment does not work, there is a way=20 > for you to find out more about your SMTP server, if you are=20 > adventurous and you have the TELNET client software (most=20 > machines do). > > Let us know what you find. > > --Scott Jones -- To unsubscribe from the list, just send an email to rebol-request at rebol.com with unsubscribe as the subject.
