|
Pages: [1]
|
 |
|
Author
|
Topic: Anybody with POP Email experience using REBOL? (Read 344 times)
|
|
leke
|
From the example in the core guide: pop://user:pass@mail.example.com If system/schemes/pop/host: "mail.bluebottle.com"; my POP server should I use pop: open pop://r3bol:mypassword@bluebottle.com or pop: open pop://r3bol:mypassword@mail.bluebottle.com or pop://r3bol@bluebottle.com:mypassword@mail.bluebottle.com; (with or without the mail) I get an error for each. Here's my script: system/user/email: "r3bol@bluebottle.com" system/schemes/default/host: "smtp.bluebottle.com" system/schemes/pop/host: "mail.bluebottle.com" system/schemes/default/proxy/host system/schemes/default/proxy/port-id system/schemes/default/proxy/type
pop: open pop://r3bol@bluebottle.com:my_password@mail.bluebottle.com forall pop [print first pop] close pop
|
|
|
|
|
Logged
|
|
|
|
|
Anton
|
Probably it is the "@" character in the username which is causing the error. The url parser or the pop scheme handler gets confused by it. Anyway, the solution is probably to use a scheme spec block instead of a url. port: open [scheme: 'pop user: " r3bol@bluebottle.com" pass: "mypassword" host: "mail.bluebottle.com"] Or, more generically: port: open compose [scheme: 'pop user: (user) pass: (pass) host: (server)]
|
|
|
|
|
Logged
|
|
|
|
|
|
Pages: [1]
|
|
|
 |