World: r3wp

Why you think it will be difficult for parse to work natively on 
files?

After all a file is just a binary! series

No Jaimie, i wanted only say: "there are NOT workaround for checksum 
 - there are workarounds for parse"

Ok. Then. Can we put feature requests in RAMBO?

Romano: thanks, I will try it - I have a version of rebzip decompressing 
a file while it's downloaded, but the code isn't pretty (two nearly 
same funcs.)

Is there a way to get the name, file, or line number of a function's 
caller?

no

the maillist archives will have some very good discussions on the 
subject

ok, thanks

How does one lookup MX records ?

but it boils down to the fact that code is data, i.e. these function 
calling can emitted from functions which are constructed on the fly, 
so there is no home to phone to.

http://www.webmaster-toolkit.com/mx-record-lookup.shtml

So, there is no nslookup utility for rebol ?

must be http://www.compkarori.com/soap/index.shtml

you lost me ...

print read dns://www.coolnamehere.com/

or is that not what you were thinking of?

hmm.

that is what I was looking for

I want to find the mail server for a given email address...

so I can implement outgoing smtp mail ...

finger? whois?

I'm behind a firewall, so I don't know which (if either)

read join dns:// mailhost

but how do you know the mailhost ?

from the part agrer the @ in the email address I wouls think

after

nope ..

I have an email ... [gchiu-:-compkarori-:-com] .. 
How would you get the MX record for that?

... trying to find something useful right now :-)

this is the answer : 203.79.110.37

because I know it :)

leave me a message here if you find anything :)

Will do :-)

http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=dig.r
maybe?

Dig.r does appear to support MX...

ahh... I looked for digger but not dig

>> res: read dig://203.96.152.4/MX/www.compkarori.com
connecting to: 203.96.152.4
>> print res/to-str
;; REQUEST: MX(15) for www.compkarori.com

;; id: 52715 AA: 0.0 RD: 1.0 RA: 1.0 ANSWER(s): 0 AUTHORITY(s): 1 
ADDITIONAL(s): 0

;; ANSWER(s):

;; AUTHORITY(s)

compkarori.com. 531 SOA ns1.webxess.net.  postmaster.webxess.net. 
 2005030501  10800  3600  1209600  600

;; ADDITIONAL(s)

Doesn't give me the correct answer :(

what about
	read dig://www.comparori.com/MX

.oO(firewalls are annoying at moments like this)

hey, that works :)

good, had to guess my way through in my head :-D

Now I can start coding my smtp server for outgoing mail.

actually, this is the form I used 

>> res: read dig://203.96.152.4/MX/compkarori.com
connecting to: 203.96.152.4
>> probe res/to-str
{;; REQUEST: MX(15) for compkarori.com

;; id: 53188 AA: 0.0 RD: 1.0 RA: 1.0 ANSWER(s): 2 AUTHORITY(s): 3 
ADDITIONAL(s): 3

;; ANSWER(s):
compkarori.com.^-247^-MX^-0   pop.compkarori.com.
compkarori.com.^-247^-MX^-10   pop.compkarori.com.

;; AUTHORITY(s)
compkarori.com.^-596^-NS^-ns3.webxess.net.
compkarori.com.^-596^-NS^-ns1.webxess.net.
compkarori.com.^-596^-NS^-ns2.webxess.net.

;; ADDITIONAL(s)
pop.compkarori.com.^-596^-A^-203.79.110.37
ns1.webxess.net.^-69731^-A^-216.166.83.11
ns2.webxess.net.^-69731^-A^-216.166.83.12
}

oh, the www was confusing it?

yeah ..

>> res: read dig://203.96.152.4/MX/compkarori.com
connecting to: 203.96.152.4
>> probe res/additionals/1/Rdata/ip
203.79.110.37
== 203.79.110.37

Graham depends on the tool. With dig. You do
dig MX domain.dom

what does this mean?


   * Generate 64 bits of randomness from a good, well-seeded random 
   number generator;

ie. how large a seed do I need to get 64 bits ?

http://www.jwz.org/doc/mid.html
	

 In summary, one possible approach to generating a Message-ID would 
 be:

    * Append "<".


    * Get the current (wall-clock) time in the highest resolution to 
    which you have access 

    (most systems can give it to you in milliseconds, but seconds will 
    do);


    * Generate 64 bits of randomness from a good, well-seeded random 
    number generator;


    * Convert these two numbers to base 36 (0-9 and A-Z) and append the 
    first number, 

    a ".", the second number, and an "@". This makes the left hand side 
    of the message ID be only about 21 characters long.


    * Append the FQDN of the local host, or the host name in the user's 
    return address.

    * Append ">".

enbase doesn't accept a value of 36