If you can hack a daemon to do X.400 handshaking, you could perhaps hack
backupd to accept it's input over an AF_UNIX socket from a receiving
X.400 daemon and output over the same sort of socket to a sending
X.400 daemon. backupd isn't going to know where one message begins and
another ends, so the sending X.400 deamon has to be able to parse
message begin and end. This has the advantages that the firewall
just gets generic ip packets destined for a non-privileged port
on a remote machine and you don't have to rewrite message headers
at either end.
You do need control of both ends of the mail connection, though, so you
can install the backupd server behind the firewalls. If you need to
connect to X.400 servers that your client doesn't own, spend money or do
some substantial coding (or perhaps just substantial debugging, which is
often the same thing as substantial coding). The available of a free
solution to a problem like this depends on whether anyone capable of
coding it actually needs it or thinks it would be a public service to
write it. In an smtp world, it's not surprising that not many free X.400
solutions are known.
Regards, Clayton Weaver [EMAIL PROTECTED] (Seattle)
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
