KS>> outbound /usr/local/mail/out
KS>> dosoutbound p:\out.002
KS>> dosoutbound p:\out.003
PS> ??? You can only have one AFAIK.
PS> Try with 'dosoutbound p:\out' instead.
PS> And look into the *.?lo files to see what is written.
KS> The *.?lo files agree with this,
KS> since they're written by the OS/2
KS> tosser. CASE may be a factor, though.
Dos 'ifstat' see the files referenced in the *.?lo ones ?
(if the outbound/dosoutbound is correct they should be seen)
BTW, I did some experimentation:
and when doing a packet for zone 6 I have in the *.?lo :
There seems to be a bug in the handling of dosoutbund (but I don't know
if it is was on 2.14 or if I introduced it on some of my patches;
I should check in 2.15 too).
The extra '\' bug doesn't seem to affect ifcico, only ifgate.
So it should work correctly for you.
But I still don't know if you have configured ifcico correctly.
Could you post a sample *.?lo file, its real path as seen by Linux,
the output of ifstat command, and the outbound and dosoutbound lines
of your ifcico config file
PS>> Note that for each domain with a nodelist line ifmail will use
PS>> a directory *without hexadecimal zone extension*.
KS> This is getting interesting! As I am using Binkley with*out* domains, I
KS> also removed the domains from Ifmail. So far everything *seems* to be
KS> pointing to the right directories, and the domain-based directories are
KS> no longer being created. I.e. everything is based on p:\out or
PS> Myself I just do the symlinks, eg francom -> francom.065; but that
KS> As I don't have domain directories, should I create symlinks from the
KS> main p:\out into the .??? directories?
Note also that if you use domains in the 'address' lines in config file
then ifcico will use domains; to disable completly domain handling you
need to set 4D only addresses.
If you can do symlinks however, do them, so you are allways safe.
PS> may be a concern if you can't do symlinks...
KS> No trouble doing symlinks, if I know what I'm trying to achieve. :)
Ah... so the SMB export is from Linux to OS/2; I thought it was the
The symlinks I do are:
domain.xxx -> domain for each domain that has a nodelist
entry in config file
fidonet.xxx -> domain.xxx ('fidonet' is the name of default outbound here
I choose that name even when in Binkley on DOS,
to keep consistency among all domains) the
symlink is to handle people calling without
domain configuration (they are showed under
the default domain)
dom_ain.xxx -> domain.xxx the possible weird variations resulting of
a total lack of standardization on domain
naming (most FTN tools don't handle domains
at all, so people don't care; but ifmail is
a *good* program, it handles domains, and
"foonet" and "foo-net" are for it different
ones, as it should be)
chanae:/var/spool/ifmail$ ls -od *.065 francom
lrwxrwxrwx 1 root 11 Oct 11 1998 fm.065 -> francom.065
lrwxrwxrwx 1 root 11 Oct 11 1998 fmed.065 -> francom.065
lrwxrwxrwx 1 root 12 Oct 11 1998 fmedia.065 -> francom.065
lrwxrwxrwx 1 root 11 Oct 11 1998 franco-média.065 -> francom.065
drwx------ 13 fnet 1024 Sep 8 02:01 francom
lrwxrwxrwx 1 root 7 Oct 11 1998 francom.065 -> francom
lrwxrwxrwx 1 root 12 Oct 11 1998 francomedia.065 -> francom.065
lrwxrwxrwx 1 root 11 Oct 11 1998 francom?.065 -> francom.065
lrwxrwxrwx 1 root 11 Oct 11 1998 francomédia.065 -> francom.065
the normalized domain I use: "francom", and I have a nodelist entry
in config file, so a direcotry 'francom'. I have a francom.065 symlink
(zone is 101) so if I decide to suppress the nodelist entry in config
it still works (and indeed I think I have done currently).
There is no fidonet.065 in this case, as all my links show domain information
for that FTN network.
However they seem to almos all use a different domain name :-(
and I had to create lost of symlinks to handle all those variations
('fm','fmed','fmedia','franco-média','francomédia','francom?'(a dos accent
used in this one) and 'francomedia').
-- À bientôt, Pablo Saratxaga PGP Key available, key ID: 0x8F0E4975