Nick, Your English is great, no need to apologize. Now, to use another similar expression, you have "hit the nail on the head" with your suggestion to modify /etc/services to add the imap "alias" on the imap2 lines. Everything seems to work properly now. Thanks again for all of your help on this problem! Jim --On Tuesday, September 25, 2001 10:45 PM -0400 Nicolas Riendeau <[EMAIL PROTECTED]> wrote: > Hi James! > >> >> Thank you for the suggestion, Nicolas. However, EXTERN_DHCP is set to >> YES, so that is apparently not the problem. I am puzzled that SSH is >> portforwarded through the box without problems and without generating >> error messages, but IMAP is not. > > I read your message a little too fast yesterday and for some weird reason > I thought I had read that the config you had done with a static IP had > two forwards (ssh & imap) while the new one with the dynamic IP had only > a port forward for imap... (I reread your message today and realized that > I had misread, sorry...) > > I do think I found the real reason this time however... (and it's > actually your original message that gave me a good clue as to where to > look (-; ) > > BTW, I reread what Jeff had suggested and he was actually right on the > bullet (hope I got that expression right (ie remember that English is not > my mother tongue)). > > Replace the two lines in /etc/services which contain imap2 so that they > read as follow: > > imap2 143/tcp imap # Interim Mail Access > Proto v2 imap2 143/udp imap > > I added imap to the list of aliases for imap 2. I looked at the > /etc/services of a pc which use a "full" distribution of Linux and this > what these lines looked like... I also looked at the /etc/services of > another *nix variant and these lines were actually defined that way: > > imap 143/tcp imap2 imap4 # Interim Mail Access > Proto v2 & V4 imap 143/udp imap2 imap4 > > which I think I would prefer over the previous definition since I think > IMAP, whatever the version and as long as it is not encrypted, uses port > 143 and imap2 and imap4 are simply versions of this protocol and should > probably only be defined as alias (but take this with a grain of salt > since I'm no *nix or imap guru... (-; ). > > Why will this work? If you have the same /etc/services I have (ie without > the definition for imap) if you used "0/0_imap" no port was actually > opened on the firewall but once you used "0/0_imap2" you could see that > rules were added to open this port but no forwarding rules for IMAP were > added. > > The port forwarding "rules" are actually added in /etc/ipfilter.conf > (what "rules" are added and where they forward to depends on the content > of /etc/network.conf) and the relevant lines in ipfilter.conf which add > that "rule" refer to this protocol as imap and not imap2 (so that's why > it complains) > > << > if [ -n "$INTERN_IMAP_SERVER" ] ; then > $IPMASQADM portfw -a -P tcp -L $EXTERN_IP imap -R $INTERN_IMAP_SERVER > imap fi ---- > ---- >>> > > Which is perfectly ok for a "normal" /etc/services but not for the one > Lrp uses (or at least the Eiger variants...). > > Let me know if that works... (ie the modification to /etc/services) > > Good luck! > > Nick > _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
