fidogate-list Mailing List for FIDOGATE

On Nov 17, 2008, at 5:48 AM, Christian G. von Busse wrote:

> Apologies for posting a rather lengthy mail. But despite working
> through the documentation (and preparing config files accordingly), I
> am still a little bit lost: How should I actually RUN fidogate?


    I just have BinkD run the following in a script after an FTN  
session completes:

===<cut>===============================================

# Inbound tosser and ticker processing
$FGBINDIR/runin

# Inbound gateway (Fido -> Internet and FTN -> FTN) processing
$FGBINDIR/rungate

# Outbound gateway for mail (Internet -> Fido) processing
$FGBINDIR/runmail

# Outbound gateway for news (Internet -> Fido) processing
$FGBINDIR/runnews

# Outbound packet processing (various sources)
$FGBINDIR/runout

===<cut>===============================================


Robert James Clay
ja...@ro...

Thanks again, the hints posted here for Postfix are working.

A small (and maybe obvious) additional hint for other users who want
to try this setup:

> ### defaults for fidonet
> .z1.fidonet.org                 ftni:
> .z2.fidonet.org                 ftni:
> .z3.fidonet.org                 ftni:
> .z4.fidonet.org                 ftni:
> .z5.fidonet.org                 ftni:
> .z6.fidonet.org                 ftni:

If you want to use this with other domains (e.g., fido.example.com),
omit the first point in the domain:

fido.example.com      ftni:

Christian

Apologies for posting a rather lengthy mail. But despite working
through the documentation (and preparing config files accordingly), I
am still a little bit lost: How should I actually RUN fidogate?

The example lead node configuration says in 5.4, I should regularly
run rungate, runin, runmail, runnews and runout from cron (all
together? Simultaneously? Or subsequently? In which order?). But since
I fail to understand how these scripts interoperate (despite the
description in 5.4), I struggle to implement this appropriately here:

What I am looking for:
----------------------
fidogate shall operate as 2:240/2188.911, and as such shall
gate e-mails and news between Internet and Fido. I have inn and
postfix up and running.

My node system, 2:240/2188, is running on the same machine (with husky
and some more stuff), but on a separate binkley style outbound than
fidogate. I know how to locally transfer ftn packets between two
binkley style outbounds - fidogate & husky, so that should not be an
issue.

What I have done:
-----------------
I had a look at rungate, which, besides locking & unlocking,
essentially contains two main parts:

/usr/lib/fidogate/ftnin -x %L/ftninpost

and

/usr/lib/fidogate/ftn2ftn -A 2:2/242 -B 242:242/2

The doc says that ftn2ftn is a netmail gateway program, and that A and
B specify my addresses in two networks... Now - neither of these
addresses is a NM of mine. And I don't want to gate any NMs between
two different FTNs.

What happens on my system:

inn is fed news through suck about every 30 mins. inn then produces a
batch for fidogate. Ideally, at this point I would like to call
fidogate to gate/process this batch. Would this be the "ftnin"-call
from "rungate"? Should I remove the ftn2ftn call from this script?

And thereafter, I need to start runin, right?

For Internet -> Fido mail I guess I will need to call runin (only, no
rungate?) regularly, as I don't think that postfix passing e-mails to
ftnmail will be sufficient (or will it?).

For Fido -> Internet, I should run "runin" once there is a bundle for
fidogate in my husky outbound, right? And after runin, I should run
runmail and runnews? Or runout? Or all three?

Thanks, Christian

On Nov 14, 2008, at 8:19 PM, Robert James Clay wrote:
> On Nov 14, 2008, at 2:22 AM, Christian G. von Busse wrote:
>
>> (Not sure if I should rather post in English here. In a nutshell, my
>> question below is: Is there a possibility to run fidogate with  
>> postfix
>> rather than sendmail, and if so - what would I need to do? Thanks.)
>
>       This is what I have added to /etc/postfix/main.cf on the system
> where Fidogate & Posftfix is running:

       Hmm...   A couple of the lines in that main.cf entry wrapped  
unexpectedly.    If anyone has troubles with that, please let me know.

       The other part of the postfix configuration for Fidogate is in  
the transports file, like as follows:

### defaults for fidonet
.z1.fidonet.org                 ftni:
.z2.fidonet.org                 ftni:
.z3.fidonet.org                 ftni:
.z4.fidonet.org                 ftni:
.z5.fidonet.org                 ftni:
.z6.fidonet.org                 ftni:
  #



Robert James Clay
ja...@ro...
rj...@gm...
Sysop, 1:120/545

On Nov 14, 2008, at 2:22 AM, Christian G. von Busse wrote:

> (Not sure if I should rather post in English here. In a nutshell, my
> question below is: Is there a possibility to run fidogate with postfix
> rather than sendmail, and if so - what would I need to do? Thanks.)


      This is what I have added to /etc/postfix/main.cf on the system  
where Fidogate & Posftfix is running:

# FIDOGATE  
###################################################################
#
ftn       unix  -       n       n       -       -       pipe
     flags=F user=news argv=/usr/lib/fidogate/ftnmail -- $recipient
ftni      unix  -       n       n       -       -       pipe
     flags=F user=news argv=/usr/lib/fidogate/ftnmail -i -- $recipient
ftna      unix  -       n       n       -       -       pipe
     flags=F user=news argv=/usr/lib/fidogate/ftnmail -a $nexthop -i  
-- $recipient
ftno      unix  -       n       n       -       -       pipe
     flags=F user=news argv=/usr/lib/fidogate/ftnmail -a $nexthop -O  
outpkt/$nexthop -i -- $recipient
#
# FIDOGATE  
###################################################################

    That reminds me;  if there isn't a note about that in the  
Fidogate archive, I should add it to the repository...





Robert James Clay
ja...@ro...
rj...@gm...
Sysop, 1:120/545

Christian,

2008/11/14 Christian G. von Busse <Cv...@kr...>:
> (Not sure if I should rather post in English here. In a nutshell, my
> question below is: Is there a possibility to run fidogate with postfix
> rather than sendmail, and if so - what would I need to do? Thanks.)

     Certainly, you can;  don't recall if there are notes with the
Fidogate archive or if I got the info elsewhere, but one can have it
work with postfix as that is how I run it...    I'll check my notes
about it when I get home...


-- 
Robert J. Clay
rj...@gm...
Sysop, 1:120/545

(Not sure if I should rather post in English here. In a nutshell, my
question below is: Is there a possibility to run fidogate with postfix
rather than sendmail, and if so - what would I need to do? Thanks.)

Danke, Viktor. Nun lief die Kompilierung ein Stückchen weiter. Das
bringt mich zu der Frage, die ich eigentlich erst später, nach ein
bißchen Rumprobiererei mit fidogate stellen wollte:

make[1]: Betrete Verzeichnis '/usr/src/fidogate-4.4.10/sendmail'
make[1]: *** Keine Regel vorhanden, um das Target /usr/share/sendmail-cf/README, 
  bentigt von README, zu erstellen.  Schluss.
make[1]: Verlasse Verzeichnis '/usr/src/fidogate-4.4.10/sendmail'
make: *** [all] Fehler 1

Den Fehler verstehe ich. Das Verzeichnis existiert nicht, denn hier
ist kein sendmail installiert - sondern postfix.

Ich habe in den docs gesucht, dort aber "nur" die Anleitung für
sendmail und eine alternative Beschreibung für qmail gefunden. Google
findet was, was vielleicht eine Anleitung für fidogate und postfix
sein könnte - allerdings kyrillisch. Gibt es eine Anleitung, um
fidogate mit postfix zu betreiben? Oder eine Beschreibung des
Prinzips, das realisiert werden müßte, um ein solches Setup zum Laufen
zu bringen? Und muß die Kompilierung nach dem o.g. Fehler noch
weiterlaufen, oder reicht der bis dahin abgelaufene Teil, um fidogate
mit postfix zu betreiben?

Kurze Erläuterung zum Hintergrund: Mein aktuelles System läuft unter
OS/2 mit Watergate als Gateway (und Weasel als MTA). Ich bin nun dabei
ein neues System unter Linux aufzusetzen. Postfix läuft, der Fido-Teil
(husky) auch in den wichtigen Grundzügen. Nun fehlt noch die
Verbindung beider Teile...

Danke, CvB

Hallo,

On Donnerstag 13 November 2008 13:31:38 wrote Christian G. von Busse:

> Ist das ein bekanntes Problem, für das es eine bekannte Lösung gibt,

Ja. Zumindest Emil Schuster und ich hatten das auch schon. Wahr hier 
zuletzt im Mai diesen Jahres Thema.

Damals schrieb ich am 19.05.08 zum Abluß dieses hier:

==================================================
On Montag 19 Mai 2008 12:49:30 wrote Dirk Meyer:

> Try this patch:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/news/fidogate/fil
>es/patch-rfc2ftn.c?rev=1.1;content-type=text%2Fplain
>
> kind regards Dirk

Thank you, Dirk.

Emil Schuster kindly sent me a forward of a mail from Martin Junius with 
another solution. In short (and in German):

|> ../../src/include/prototypes.h:53: error: previous declaration of
|> 'i_flag' was here
|
|Die Deklaration in prototypes.h ist ein Überbleibsel, das falsch ist,
|kann dort gelöscht werden.
|
|> dbz.c:303: error: conflicting types for 'malloc'
|> dbz.c:304: error: conflicting types for 'calloc'
|
|Ebenso diese Deklarationen in dbz.c, die im Konflikt zu stdlib.h stehen,
|kann auch komplett entfernt werden.

So, the declarations of i_flags in prototypes.h and malloc/calloc dbz.c are 
obsolete and simply can/should be removed. Works fine here.
=======================================================

Ciao,
-- 
Viktor Kafke <vi...@ka...>
Mühlenweg 60 * D-31515 Wunstorf
Tel.: 05031-5150017 * Fax.: 05031-5150016
PGP-Key AE474634 at http://www.visyn.net/vik-key.asc

Hallo,

ich versuche gerade, fidogate 4.4.10 (letzte stable...?) zu
kompilieren. "make depend" läuft ohne Fehler durch. Bei "make"
erhalten ich folgenden Fehler:

make[2]: Betrete Verzeichnis '/usr/src/fidogate-4.4.10/src/gate'
gcc -g -I../.. -I../../src/include -Wall  -c ftn2rfc.c
gcc -g -L../../src/common  -o ftn2rfc ftn2rfc.o -lfidogate
gcc -g -I../.. -I../../src/include -Wall  -c ftnin.c
gcc -g -L../../src/common  -o ftnin ftnin.o -lfidogate
gcc -g -I../.. -I../../src/include -Wall  -c rfc2ftn.c
rfc2ftn.c:102: Fehler: Statische Deklaration von i_flag folgt nicht-statischer Deklaration
../../src/include/prototypes.h:53: Fehler: Vorherige Deklaration von i_flag war hier
make[2]: *** [rfc2ftn.o] Fehler 1
make[2]: Verlasse Verzeichnis '/usr/src/fidogate-4.4.10/src/gate'
make[1]: *** [all] Fehler 1
make[1]: Verlasse Verzeichnis '/usr/src/fidogate-4.4.10/src'
make: *** [all] Fehler 1

Ist das ein bekanntes Problem, für das es eine bekannte Lösung gibt,
oder muß ich jetzt mit trial-and-error versuchen, im source code zu
fummeln?

Danke, CvB

On Montag 19 Mai 2008 12:49:30 wrote Dirk Meyer:

> Try this patch:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/news/fidogate/fil
>es/patch-rfc2ftn.c?rev=1.1;content-type=text%2Fplain
>
> kind regards Dirk

Thank you, Dirk.

Emil Schuster kindly sent me a forward of a mail from Martin Junius with 
another solution. In short (and in German):

|> ../../src/include/prototypes.h:53: error: previous declaration of
|> 'i_flag' was here
|
|Die Deklaration in prototypes.h ist ein Überbleibsel, das falsch ist,
|kann dort gelöscht werden.
|
|> dbz.c:303: error: conflicting types for 'malloc'
|> dbz.c:304: error: conflicting types for 'calloc'
|
|Ebenso diese Deklarationen in dbz.c, die im Konflikt zu stdlib.h stehen,
|kann auch komplett entfernt werden.

So, the declarations of i_flags in prototypes.h and malloc/calloc dbz.c are 
obsolete and simply can/should be removed. Works fine here.

Ciao,
-- 
Viktor Kafke <vi...@ka...>
Mühlenweg 60 * D-31515 Wunstorf
Tel.: 05031-5150017 * Fax.: 05031-5150016
PGP-Key AE474634 at http://www.visyn.net/vik-key.asc

Hi,

i tried to compile the fidogate 4.4.10 source on a new machine (OpenSuse 
10.3 with gcc version 4.2.1) and got this:

make[2]: Entering directory `/root/Downloads/fidogate-4.4.10.vk/src/gate'
gcc -g -I../.. -I../../src/include -Wall  -c ftn2rfc.c
gcc -g -L../../src/common  -o ftn2rfc ftn2rfc.o -lfidogate
gcc -g -I../.. -I../../src/include -Wall  -c ftnin.c
gcc -g -L../../src/common  -o ftnin ftnin.o -lfidogate
gcc -g -I../.. -I../../src/include -Wall  -c rfc2ftn.c
rfc2ftn.c:102: error: static declaration of ‘i_flag’ follows non-static 
declaration
../../src/include/prototypes.h:53: error: previous declaration of ‘i_flag’ 
was here
make[2]: *** [rfc2ftn.o] Fehler 1
make[2]: Leaving directory `/root/Downloads/fidogate-4.4.10.vk/src/gate'
make[1]: *** [all] Fehler 1
make[1]: Leaving directory `/root/Downloads/fidogate-4.4.10.vk/src'
make: *** [all] Fehler 1

The exactly same source code compiles under SuSE Linux 9.3 and gcc version 
3.3.5 20050117 (prerelease) without any problem.

As google said, this "static declaration of ... follows non-static 
declaration" error occurs often on "old" code with new gcc version.

Martin, can you fix that?

Ciao,
-- 
Viktor Kafke <vi...@ka...>
Mühlenweg 60 * D-31515 Wunstorf
Tel.: 05031-5150017 * Fax.: 05031-5150016
PGP-Key AE474634 at http://www.visyn.net/vik-key.asc

Hi All.

I can't getting Fidogate to manage 4 thing b running.
1. it seem not to find any news articles from INN self if there is several
new article to gate.

2. and when it try to gate fidonet and other echoes is it first comes with
malformet files/messages + ID's
   then is it not lie to post mail to newsgrops by coming with cant't find
or run ctlinnd.
3. Fidogate just not like to work to put mails from .pkt out/frc files to
newsgroup of spcial groups like rmini.* and just rename the mail pkt to .bad
and badxxxxx.pkt

4. I have trying to just fidogate gate mail echoes there is packed t0 node
2:236/140.98 to echoes for 900:900/0.1 and too to newsgroups.
 Areas.bbs:
 - bbs_promation 2:236/150.98
 - mf_bbs_promotion 900:900/0.1

 areas:
 bbs_promotion    rmini.bbs_promotion    -l -z 2 -8
 mf_bbs_promation rmini.bbs_promotion    -l -z 900 -8

Some times come fidogate with malformed and wring zone.

Why whis and how can I get it to work right to gate as it shall do. ??
Some hel p on this will do me glad.

Regards,
Gert Andersen
ge...@ko...

Hi.

What user is the best one to run fidogate by for it can gate newsgroup to
fido inbound ?
Root or daily user there ruins all fido systems.
My news ser and client INN have put its directory as this
/etc/news/*
/usr/lib64/news/bin/*
/var/log/news/
/var/spool/news/*

And a other thing can fidogate run in daily user directories asc
/home/kofo/bin /lib /etc/
My inbounds is /in/in_sec /in/un_sec /in/loc_in /in /tmp
Outbound is /home/kofo/out/outb + outb.[zones]

Take care,
Gert Anderen

Hi.

Can Fidogate rename echoes fro 1 zones echoes to another zones echo.
Like hpt pack mail to point 8:7606/150.99 -> 900:100/1 and do gen_oklahoma
-> r_oklahome.gen ?

Taka care,
Gert Andersen

Hi,

sometimes I find entries in my fidogate-log like

| Jul 27 16:30:07 ftn2rfc MSGID 67405.fidonews@1:249/303 0b102a20:
| malformed or unknown zone, not gated=20

I don't know which kind of fido software generates such MSGIDs. My question=
=20
on that is:

How risky is it to force fidogate to gate such messages (by patching the=20
source code). In which format should I translate the MSGID? What can=20
happen in the worst case?

In this specific case the echo ist gated in a private local hierarchy (I'm=
=20
sure that there are no other gateways around, no peers, only few known=20
readers)

Ciao,
=2D-=20
Viktor Kafke <vi...@ka...>
M=FChlenweg 60 * D-31515 Wunstorf
Tel.: 05031-5150017 * Fax.: 05031-5150016

    I had gotten started on updating the Debian packageing but ended
up having to take a bit of a break because the system I was doing the
package testing on decided it didn't want to work anymore...   I'll be
putting another system together but in the mean time I decided I'd
make changes in how the package gets built.

     As it was, I had been able to get the programs updated to the
current version & I had an operational node running using those
programs.   Installs, however, were still broken;  missing directorys,
it still installing an old version of the config files, etc.  Since I
need to do changes anyway now that v4.0 of Debian (Etch) has been
released, I've decided to update the packageing using the more current
standards;  need to do that in any case, in order to possibly get the
package back in to the Debian distribution...


-- 
Robert J. Clay
ja...@us...
rj...@gm...

Benoit Panizzon wrote:

> Did I do something worng in the config, or is fidogate not intended
> to convert emails back from FTN to RFC?

FIDOGATE is not really intended for a (sort of) transparent RFC-FTN-RFC 
operation. There were some hacks around PASSTHRU_NETMAIL, but this is 
not really what you want.

So if you desperately ;-) need this feature, you must implement it 
yourself. As headers can be transported using ^ARFC-xxx, this is 90% 
feasible.

What is the reason for your requirement? Having multiple gateways in a 
gateways in a chain converting to and fro is IMHO asking for many problems.

Martin

Hi all

Is there a way to preserver the RFC Received Headers while they trespass a FTN 
Gateway?

I have two Gateways working here...

One accepts RFC Emails and converts them in FTN Netmails. They seam to contain 
all headers in @A Kludges.
They then get moved to the next Gateway where they get converted back into 
SMTP Emails.

Now split emails don't get joined and most of the original Headers are 
missing.
So if the final recipient forwards such emails that contain spam to spamcop 
it's my FidoNet Gateway that get's blacklisted.

Did I do something worng in the config, or is fidogate not intended to convert 
emails back from FTN to RFC?

Regards
-Benoit-

   =================================================================
     FIDOGATE 4.4.10, a stable version of the new FIDOGATE release
   =================================================================

			   FIDOGATE Version 4
		      ===========================
		       * Fido Internet Gateway
		       * Fido Zone Gateway
		       * Fido Tosser
		       * Fido Ticker
		       * Fido Areafix and Filefix
		      ===========================


   Internet:
   =========
     http://www.fidogate.org/


   Download:
   =========
     http://sourceforge.net/project/showfiles.php?group_id=10739

     ftp://ftp.fidogate.org/pub/fidogate/
     http://www.fidogate.org/pub/fidogate/

     ftp://metalab.unc.edu/pub/Linux/system/fido/
     http://metalab.unc.edu/pub/Linux/system/fido/
     (maybe still in .../pub/Linux/Incoming)

     fidogate-4.4.10.lsm			   1 Kbyte
     fidogate-4.4.10.tar.gz		1170 Kbyte
     fidogate-4.4.10-1.fc2.src.rpm	1170 Kbyte
     fidogate-4.4.10-1.fc2.i386.rpm	1100 Kbyte



======================================================================

Changes in 4.4.10:

* SECURITY BUG in all setuid news programs fixed (environment
   variables FIDOGATE_LOGFILE, LOGFILE allowed local append to
   all files writable by news).

* rfc2ftn: new config option SilentBounces, causes EX_NOHOST,
   EX_NOUSER errors to return OK without any message.  Useful in the
   never ending fight against spam, when your gateway is flooded with
   messages to unknown adresses, such as Fido.DE :-(

* rfc2ftn: "Sysop" is always a valid name.

* logsendmail2: new log analysis script.

* send-fidogate: added optimized handling for INN 2.4, must be enabled
   by modifying this script.

* Compile time conflict with Standard-C function log() solved.

* ftn2rfc: if the UseOriginForOrganization option is set, don't
   convert empty * Origin lines to Organization header, use default
   instead.

Thanks to Viktor Kafke and Niels Heinen for their input, which
triggered this release ... ;-)



Changes in 4.4.9:

* send-fidogate: fixed INN interface (using batcher) for INN 2.3.

* RPMs build for RedHat 9 (release rh9x).



Changes in 4.4.8:

* Minor changes, new sendmail mc configuration files for building
   FIDOGATE on RedHat 9. New RPMs for RedHat 9.



Changes in 4.4.7:

* rfc2ftn: new options RegisteredHostsOnly (not yet implemented!),
   kinda reverse function to -i --ignore-hosts, and
   RegisteredAliasesOnly, allowing only mail to recipient addresses
   registered via the ALIASES file, both al...@ho... and
   Use...@ho...; bounced mails (host, user) are now logged,
   logging of messages now more sendmail-like.

   The RegisteredAliasesOnly option is quite useful for bouncing spam
   to non-existing addresses right at the gateway (used that way at
   Fido.DE).



Changes in 4.4.6:

* ftn2rfc: new DontIgnore0x8d aka DontIgnoreSoftCR config option.

* ftnhatch: new -r --replaces FILE command line option.

* ffxqt: increased number of possible command args to 256.



Changes in 4.4.5:

* sendmail related scripts and sendmail config files updated for
   version 8.11

* first version at sourceforge.net



Changes in 4.4.4:

* rfc2ftn: fixed severe bug in handling of long header lines,
   e.g. References, which caused missing or incorrect ^AREPLYs. Thanks
   to Stephan Heitbrink <hei...@gm...> for reporting the bug and
   providing the test input news article files.

* hosts2dns: default MX changed



Changes in 4.4.3:

* runpoll-binkd: updated for binkd 0.9.4

* out-ls: updated, uses fidogate.conf

* i386 RPM: fixed missing /var/lib/fidogate/seq/

* ftnafutil: new "listdownlinks" for areassucksync

* areassucksync: new script for sync'ing areas.bbs and sucknewsrc

* runafutil: new run script for ftnafutil

* outb: new wrapper script for out-ls

* outb-kill: new script, remove outbound stuff for a node

* rfc2ftn: new config options DontChangeContentTypeCharset,
   DontProcessReturnReceiptTo



Changes in 4.4.2:

* Some changes to the various scripts.

* Code clean-up, got rid of all insecure strcpy(), strcat(), sprintf()
   functions.

* ffx, ffxqt: support for job compression removed (ftnpack does this
   anyway), several changes to improve security.



Changes in 4.4.1:

* ftn2rfc: fixed bug in handling of invalid ^ACHRS for input charset.

* rfc2ftn: fixed memory leak.

* ftn2rfc: fixed memory leak.



Changes in 4.4.0:

* NEW STABLE RELEASE based on 4.3.6.

* charset.map: translation tables completed.

* ftn2rfc: line formatting changes (filling to MessageLineLength only
   for lines >= 80 chars).

* Distribution now as i386 and src RPM for RedHat 6.0 (should work
   with other glibc-based distributions as well). Binary RPM installs
   new sample config files for FIDOGATE point.

* Some minor bugfixes to scripts and C source.



======================================================================

Needed:

* GNU CC or ANSI C compiler
* GNU make
* GNU flex/bison or lex/yacc
* Perl5
* sendmail m4 configuration files
* GNU m4 for the sendmail m4 configuration

======================================================================

$Date: 2004/08/26 20:56:00 $
Martin Junius
mailto:mj...@fi...

Viktor Kafke schrieb:

> One of the Points in 2437 is using an empty! Origin-Line in his postings. 
> After gating such a Message, my INN is whining:
> 
> Aug 21 18:50:19.494 - p99.worf.pfnz.de 
> <MSG...@fi...> 437 Body of header is all blanks 
> in "Organization" header
> 
> an refuses the Posting. Can you solve this problem or should i patch it (and 
> post it here)?.

Please try the following patch, it should avoid empty Organization 
headers, using the default from the config. This fix is also in the 
current CVS.

Martin


===================================================================
RCS file: /cvsroot/fidogate/fidogate/src/gate/ftn2rfc.c,v
retrieving revision 4.63
diff -u -3 -p -r4.63 ftn2rfc.c
--- ftn2rfc.c	22 Aug 2004 10:30:02 -0000	4.63
+++ ftn2rfc.c	22 Aug 2004 20:05:26 -0000
@@ -1090,6 +1090,7 @@ int unpack(FILE *pkt_file, Packet *pkt)
  	}
  	
  	/* Common header */
+	p = NULL;
  	if(use_origin_for_organization && body.origin)
  	{
  	    strip_crlf(body.origin);
@@ -1104,12 +1105,13 @@ int unpack(FILE *pkt_file, Packet *pkt)
  	    p = buffer + strlen(" * Origin: ");
  	    while(is_blank(*p))
  		p++;
-	    tl_appendf(&theader, "Organization: %s\n", p);
-	}
-	else
-	{
-	    tl_appendf(&theader, "Organization: %s\n", cf_p_organization() );
+	    if(!*p)
+		p = NULL;
  	}
+	if(!p)
+	    p = cf_p_organization();
+	tl_appendf(&theader, "Organization: %s\n", p);
+
  	tl_appendf(&theader, "Lines: %d\n", lines);
  	if(gateway)
  	    tl_appendf(&theader, "X-Gateway: FIDO %s [FIDOGATE %s], %s\n",

On Sunday 22 August 2004 10:56, Martin Junius wrote:

> Thanks for the patch, I included a modified version in send-fidogate.sh.
> Viktor, can you please try the attached send-fidogate.sh (uncomment
> OPTIMIZE=3Dyes at the beginning).

Done. Works fine, thanx

Another Problem:

I'm gating the hannover.*-Hierarchy using your fidogate 4.4.9 with the=20
settings

UseOriginForOrganization
UseOrganizationForOrigin

One of the Points in 2437 is using an empty! Origin-Line in his postings.=20
After gating such a Message, my INN is whining:

Aug 21 18:50:19.494 - p99.worf.pfnz.de=20
<MSG...@fi...> 437 Body of header is all =
blanks=20
in "Organization" header

an refuses the Posting. Can you solve this problem or should i patch it (an=
d=20
post it here)?.

=2D-=20
Viktor Kafke <vi...@ka...> /| Phone: +49-5031-5150017
M=FChlenweg 60                  / | Fax:   +49-5031-5150016
31515 Wunstorf, Germany      /__| Cell:  +49-173-6659750
\___________________________/___|________________________|

Dear list,

please apply the following patch to all FIDOGATE versions up to 4.4.9. 
This fix is already included in the current CVS and will be part of the 
upcoming release 4.4.10.

The problem is that the FIDOGATE setuid news programs could be used by a 
  local user to append data to all news owned files on the system. Given 
the complexity of the news system, this may lead to all sorts of problems.

Martin


===================================================================
RCS file: /cvsroot/fidogate/fidogate/src/common/log.c,v
retrieving revision 4.21
retrieving revision 4.23
diff -u -3 -p -r4.21 -r4.23
--- log.c	16 Feb 2003 15:38:56 -0000	4.21
+++ log.c	22 Aug 2004 08:59:00 -0000	4.23
@@ -2,7 +2,7 @@
 
/*****************************************************************************
   * FIDOGATE --- Gateway UNIX Mail/News <-> FIDO NetMail/EchoMail
   *
- * $Id: log.c,v 4.21 2003/02/16 15:38:56 n0ll Exp $
+ * $Id: log.c,v 4.23 2004/08/22 08:59:00 n0ll Exp $
   *
   * Log and debug functions
   *
@@ -279,9 +279,4 @@ void log_program(char *name)
      char *p;

      BUF_COPY(logprog, name);
-
-    if( (p = getenv("LOGFILE")) )
-       log_file(p);
-    if( (p = getenv("FIDOGATE_LOGFILE")) )
-       log_file(p);
  }

Viktor Kafke schrieb:

> The Format of the Newsbatches has changed since 2.3. To convert the batches, 
> you can use sm (and sed).
> 
> Here are my changes to send-fidogate for using with my INN 2.4.1:

Thanks for the patch, I included a modified version in send-fidogate.sh. 
Viktor, can you please try the attached send-fidogate.sh (uncomment 
OPTIMIZE=yes at the beginning).

Martin

Hi Folks,

for those of you, who would like to use Fidogate with INN > 2.2:

The Format of the Newsbatches has changed since 2.3. To convert the batches=
,=20
you can use sm (and sed).

Here are my changes to send-fidogate for using with my INN 2.4.1:

worf:/usr/lib/fidogate/bin # diff send-fidogate=20
/root/fidogate-4.4.9/src/gate/send-fidogate
66c66
<     "INN 2.4"*)
=2D--
>     "INN 2.2"*)
68,75d67
< # changed by vik
<     echo $BATCHFILE
<       ( while read a b ; do
<               echo `sm -i $a` $b | sed -e "s/\:\ /\//" >> $BATCHFILE.bak
<       done < $BATCHFILE ) 2> /dev/null
< # end changed by vik
<
<         mv $BATCHFILE.bak $BATCHFILE
worf:/usr/lib/fidogate/bin #

Best Regards,
=2D-=20
Viktor Kafke <vi...@ka...> /| Phone: +49-5031-5150017
M=FChlenweg 60                  / | Fax:   +49-5031-5150016
31515 Wunstorf, Germany      /__| Cell:  +49-173-6659750
\___________________________/___|________________________|