World: r3wp

I can maybe add an option for that in the config file.

>> read dns://compkarori.co.nz
== 203.97.98.9
>>

works instantly

that query is traversing a lot of layers...some of them might implement 
some sort of retries if first request doesn't work.

opendns is too slow for me for web browsing .. but it should be okay 
for just email

I'd like to test first a more robust MTA. Going to sleep now. Thanks 
for the time you took for testing.

np

I guess you're going to have to use queues for greylisting servers

Is there a way that I can use a a href to invoke a program on the 
local drive or does the security prevent this?

no matter ... I found a way to do this via content-type  ...


just need to translate this php to rsp http://www.dklevine.com/general/software/tc1000/jarnsample3.php

Re: greylisting, the plan was to use the freshly integrated scheduler 
library : scheduler/add [in 5 mn do [resend <email-id>]]

have you  tried it yet?  Or have you just got up ?  :)

I guess Gmail is selectively graylisting users ...since you havent 
seen it happen to you.

Tried: going to try it today, scheduler is working ok inside Cheyenne, 
just need to add more logging info.

Gmail: as I've retried several times at beginning (but manually), 
I may have passed the greylisting without noticing it.

just wondering if url-encode should also take file! as a parameter

doesn't sound like a common case? Using FORM should be enough : 
<%= url-encode form %file %>

Btw, I didn't understood what you wanted to achieve by "use a a href 
to invoke a program on the local drive"? You mean running an executable 
on the server with a hypertext link? (I guess you're targeting a 
server on localhost?)

If it's for local server, file:// in href can work (see http://en.wikipedia.org/wiki/File_URI_scheme).

didn't know about file://  ... yes, I can use that.

yes I am using form already .. but forme it's a common scenario to 
display files from the web server's directories

SVN r23 :


FEAT: improved logging and error handling for dig/SMTP/MTA modules.

FEAT: integration of deferred retries in MTA for temp errors recovering 
and greylisting passing.

FEAT: new config keyword in global section: dns-server. (see changelog.txt)

FIX: in email generation, added a missing CRLF between headers and 
body.
FIX: logger sub-second times output padding fixed.
FIX: minor code cleanups.

22/9-10:18:36.371-## Error in [uniserve] : On-received call failed 
with error: make object! [
    code: 300
    type: 'script
    id: 'no-value
    arg1: 'startegy
    arg2: none
    arg3: none
    near: [pick dns-server switch startegy [
            round-robin [first head reverse dns-server]
            random [pick dns-server random length? dns-server]
        ]]
    where: 'on-init-port
] !

source code version ... will now try encap.

this is with dns-server [ 203.96.152.4 230.96.152.12 ] in my httpd.cfg 
globals

In dig.r line 174 should read

			pick dns-server switch strategy [
as there is a typo there.

actually I think line 174 should read

			switch strategy [

and lose the "pick dns-server"

Thanks, the part was messed up. Fixing that.

SVN r24

FIX: more conforming handling of 4xx SMTP return codes
FIX: typo and coding error fixed in dig.r (Thanks Graham)

SVN r25

FEAT: encap paths are now in a separate file (%encap-paths.r)

sorry for ignorance, but can't find link to SVN archive ...

in MTA.r, line 135 change this line

						scheduler/plan compose/only/deep only  [

to 

						scheduler/plan compose/only/deep [

http://cheyenne-server.googlecode.com/svn/

there is an extraneous "only" in that line

Thanks Graham - what should I do with the first run of Tortoise? 
I suppose I better don't do Check-out? Should I create a "working 
copy"? I don't remember how I did it for Rebgui, as I am long time 
issuing Update item from the context menu. I need to do first sync 
of Cheyenne now, and would not like to screw something on the server 
side :-)

You can't screw up the server .. you don't have any rights

you want to do a SVN update

doc is the only person with write access to the repo

r26 is now up fixing this error.

I create Cheyenne local dir, and there is no SVN Update in the context 
menu. I first need to somehow create copy of the SVN. OK, there was 
Check-out in the context menu, hopefully Doc does not kill me that 
I have checked-out sources to myself, blocking others from submissions 
:-)

What does Cheyenne MTA means? (sorry for coming late to the topic) 
- does it mean I can turn-off Sendmail for e.g.? :-)

mail transport agent

well, it's not working yet ffor me ... when meeting a greylisting 
server

but otherwise it should work .

The goal is to send sendmail to trashcan when you need to send emails 
from Cheyenne scripts or webapps.

OK, but it can't replace Linux MTA generally, can it? I mean - installing 
Cheyenne with MTA can I replace the need for Sendmail for e.g. entirely?

Cheyenne's MTA doesn't support yet all the SMTP features found in 
others MTA, but should be enough for general usage.

Btw, it doesn't accepting other mail clients than Cheyenne's CGI 
and RSP scripts.

It's for Cheyenne only usage. Sending email is often required in 
web applications, setting up and maintaining a third party MTA like 
sendmail is costly and complicated. Having a MTA built in Cheyenne 
will save everyone a lot of time and troubles.

Still need some work for debugging and fine-tuning as said by Graham.