World: r3wp

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.

If any user wants to extend its capabilities to make a complete sendmail/qmail/postfix/... 
replacement, you're welcome.

MTA support much appreciated.

SVN r27

FIX: better integration of scheduler in Cheyenne's event loop.
FIX: bug fixes in deferred task (MX or SMTP retries)

In the www directory there's a demo file called email.rsp which you 
can use to test the MTA.  Change line 58 to your own from address.

This r27 is the first version that successfully attempts to resend 
a greylisted email ... so far it has retried twice to send my mail 
to google, but google keeps temp failing my mail :(  Guess my IP 
address is marked as a spam source.

Moved to a different IP adddress to test ..gmail still temp fails 
me!

Does it return a 421?

Maybe the retry delay is too short (or too long)?

Yes... 421 I think 15 mins is too long for the retry ...i would think 
5mins is better.

I finally got gmail to accept mail from cheyenne.  I changed the 
from address in emai..rsp to one that matched the sending domain, 
and changed the greylisting delay retry period to 5 mins from 15 
mins.  It went thru after the 2nd attempt.

email.rsp

So, this could be an issue for a server with no mx record

of course applies to any MTA .. just not to cheyenne's.

I should add a From: field in %email.rsp. I'll set the retry delay 
to 5 mn also.

I was relying on info from http://en.wikipedia.org/wiki/Greylisting
about other MTA default delay :


Most open-source MTAs have retry rules set to attempt delivery after 
around fifteen minutes (Sendmail default is 0, 15, ..., Exim default 
is 0, 15, ..., Postfix default is 0, 16.6, ..., Qmail default is 
0, 6:40, 26:40, ..., Courier default is 0, 5, 10, 15, 30, 35, 40, 
70, 75, 80,...). Microsoft Exchange defaults to 0, 1, 2, 22, 42, 
62 ...