16 Sep 16 13:01, you wrote to me:

 ML>> you have to think old school... fidonet has been doing this gating
 ML>> thing since the '80s... FRED was one of those i used way back but
 ML>> then GIGO came out and i switched to it because there was a native
 ML>> OS/2 version...

 AP> I've ran both GIGO and FRED.  I could still use GIGO but I need
 AP> something that captures the SMTP inbound and puts it into a file that
 AP> GIGO can read. Thaat's the tricky part is getting something to listen
 AP> on the SMTP port.

for GIGO, there's something in the GIGOTCP or TCPGIGO package... its name
is something like that... OS/2 native, though, AFAIR... simply puts all the
posts into BAG files which GIGO chews on...

 ML>> good grief... it is only a piddly little mailing list that you're
 ML>> after... not top secret nuclear facility access and launch codes...
 ML>> set up a gmail, yahoo or hotmail account as AP_elebbs{at}whatever and
 ML>> get your mailing list support as needed... set up one address for
 ML>> each list or

 AP> No not top secret stuff... but I can see why the new mail servers like
 AP>  Exchange are doing what they do.  Now they are checking all received
 AP> e-mails against an embedded SPF "Seed" in the message to
verify if you
 AP> actually sent it.

not "you" but the server that is connecting... it has to check if
the connecting server is really who it says it is...

 AP> What happens with older mailing list servers is that they send the
 AP> message
 AP> as if the user actually sent it which doesn't cut the validation.

i receive mailing lists that operate both ways... on some i get the list
mail as if the original user sent it direct and on others it is from the
list...

anyway, i gotta let this stack of mail get exported for processing and propogation...

)\/(ark

Always Mount a Scratch Monkey

... Couch Potatoes - People into Transcendental Vegetation.
---