<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.3">
</HEAD>
<BODY>
Your timing for todays post is ironic Maiko...<BR>
<BR>
Speaking to the topic of your post directly, I and those who I rub elbows with in my jnos world would ask for nothing of you in terms of features and performance. Your jnos is nicely done. I remain dedicated to publishing a documentation pointed at jnos but must report my publishing date has slipped drastically for lack of man hours. I pray you will deal with adjustments for platform variation via this reflector so I can pick up the gist and include it in my work for future users.<BR>
<BR>
Speaking to your timing, I have run into an interesting hitch in fleshing out my jnos environment. I have been partially successful in hooking up my regular mail agent to jnos via POP and SMTP. Here is the background:<BR>
My node is k8rra.ampr.org, 44.102.132.20, and I am POPing mail for k8rra from jnos mail queue to Evolution, and Mozilla, and I expect also Outlook Express (but not tested), successfully.<BR>
This puts all my mail from both Internet and jnos sources into the same "basket".<BR>
<BR>
I am partially successful at reply delivery to (or thru) jnos. Mail to <A HREF="mailto:call@44.102.132.20">any-call@44.102.132.20</A> or <A HREF="mailto:call@k8rra.ampr.org">any-call@k8rra.ampr.org</A> is delivered faithfully to the jnos mail queue "locally". Should I reply from the jnos BBS mail agent, all is fine. But regretfully address of the nature <A HREF="mailto:call@44.">any-call@44.</A>(any other subnet) fails to be accepted from Evolution, the message is "mailbox not available.". My understanding of this is that jnos SMTP will accept only mail directed to the "local" mail queue, and will not act to forward mail to remote mail queues, and because Evolution is built to deliver mail to only one ISP URL for all addresses I can not configure Evolution to deliver "remote" mail via jnos.<BR>
<BR>
Now, the fact is I probably don't understand all I need to know to be successful in the above effort. The other possibility is that jnos SMTP is somehow different from the SMTP present at my ISP. Can you speak to this?<BR>
<BR>
I'd like it if I need to revise my configuration a little. I'd like it a lot less if SMTP in jnos required you to revise jnos to accommodate remote mail visa vie SMTP at my ISP. I've recently seen the use of fetchmail with jnos for incoming mail, and I guess as a fall-back solution I'd accept interposing a utility between Evolution and jnos if that would permit jnos to deliver remote mail from Evolution.<BR>
<BR>
I am NOT the the first to exercise this feature set (or something similar) in this way - perhaps I'm not exactly replicating others. I directed a brief request to Jay WB8TKL from jnos but I believe I botched his address there... In any case this subject is certainly open to comment from anywhere.<BR>
<BR>
Thanks for any light you can shine on this situation.<BR>
<BR>
On Fri, 2007-02-02 at 09:50 -0600, Maiko Langelaar (ve4klm) wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Greetings all,</FONT>
<FONT COLOR="#000000">Time again to update people as to the happenings of the JNOS 2 project.</FONT>
<FONT COLOR="#000000">Many of you have probably noticed that I have not released alot of upgrades</FONT>
<FONT COLOR="#000000">lately, </FONT><A HREF="http://www.langelaar.net">>>SNIP<<</A>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>