Skip to contentSkip to conversation

FETCHMAIL over AX25?

DISCUSSION Wilbert Knol 2 participants 2 messages Apr 30, 2002 – May 2, 2002

lore
Share & tools
lore
#0 lore raw

Thanks for reading this. At home, I get my E-mail via packet radio from a remote POP3 host with the fetchmail client. It's done with TCP/IP over AX25.

The POP3 server hangs off a (remote) XROUTER node, on a LAN, and I am using that node as my gateway to the POP3 mail host.

The TCP/IP doesn't seem to work particularly well over this path, which is a combination of 1k2 AX25 and Ethernet. I have done some extensive tweaking at my end, and I have finally decided it's a lost cause.

The plan now is, to open a plain AX25 session to the XROUTER node, and, from there, telnet straight into the POP3 server.

Fetchmail allows the use of a 'plugin', and I have played with various Expect scripts, and also with the call program, to try and present Fetchmail with an open connection to the POP3 server.

The trouble is, that fetchmail doesn't like the link status messages that the call program throws up. As soon as it gets to see anything other than a valid POP3 prompt, it aborts the operation.

I have butchered the call.c code with some degree of success to stop it from writing to STDOUT until it sees the "+OK" from the POP3 server.

But I am having trouble faking the "telnet <pop3host> 110" command. The call.c code waits for a keyboard hit before it sends the hard-coded "telnet" string, which never comes.

I was wondering if anyone else has managed to do this, or has suggestions on how to go about it.

Wilbert, ZL2BSJ

#1 lore raw

Well, it's working now. I cannibalised the ax25_call.c code, which is now being used as the FETCHMAIL plugin. It sets up the AX25 session to the XROUTER node, and, from there, telnets into the POP3 server.

Result: better through-put (40 bytes more pay-load in each AX25 packet), no fragmentation, no hassles with TCP/IP timers defeating the AX25 ones. And free E-mail.

Wilbert, ZL2BSJ