Bartosz Oudekerk <bartosz@see_my_gnupg-key.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

pgp trash troll delete

> Floyd Davidson <floyd@barrow.com> is thought to have
> typed the following text on 2003-11-30:

> > Bartosz Oudekerk <bartosz@see_my_GnuPG-key.com> wrote:
> >>["Followup-To:" header set to alt.os.linux.slackware.]
> >
> > Why do you continue trying to direct followups away from where
> > others who are reading this thread can read it?
> >
> Continue? This is my first post in this thread.

> Because I see no need to have this crossposted. Plus I explicitly
> stated in the body of my post, that the Followup-To header was being
> set, so that those who would indeed like to follow this thread can
> choose to do so and know where it'll be continued.

Yes but you did not create the thread so you have no right to try to
manipulate its audience.

This is just one more example of your arrogance. Another is your
use of pgp in situations that don't require it.

When are you going to learn to show some respect for the other
posters on usenet?

cordially, as always,

rm

/dev/rob0 <rob0@gmx.co.uk> wrote:
>One other nitpick / question:
>
>In article <87r7zqky7z.fld@barrow.com>, Floyd Davidson wrote:
>> There are other ways to do it. One other is to use a "dummy"
>> network interface, which acts just like a loopback and can be
>
>IIUC a dummy interface is like a /dev/null for network packets. Packets
>come in, but they don't go out. In contrast a loopback returns them.
>They are analogous to celestial black holes and mirrors, respectively.
>Is this understanding correct? It appears so:
>#v+
>/* dummy.c: a dummy net driver
>
> The purpose of this driver is to provide a device to point a
> route through, but not to actually transmit packets.

But, as with any other network interface, if you use it as a loopback,
the actual packets go through the lo device. So while a dummy device
is only something to point a route at, if you do that you can use
it as a loopback.

/home/floyd/ >ifconfig dummy0
dummy0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
...

/home/floyd/ >telnet 192.168.3.1
Trying 192.168.3.1...
Connected to 192.168.3.1.
Escape character is '^]'.

tanana login: floyd
Password:
Last login: Sun Nov 30 13:29:06 -0900 2003 on pts/16 from dummylink.ukpeagvik.net.
~ >exit
logout
Connection closed by foreign host.

/home/floyd/ >grep dummy /etc/hosts
192.168.3.1 dummylink.ukpeagvik.net dummylink


All of the activity counts on the dummy0 device (snipped above for
brevity) remain at 0, and activity such as the above increases the
counts on the lo device.

It can be a fairly useful device to play with now and then.

--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@barrow.com

On Sun, 30 Nov 2003 08:33:06 -0900, Floyd Davidson wrote:

> Whatever, sometimes it's hard to convince people that 127.0.0.1
> shouldn't have *anything* other than localhost associated with it.
> But I'm always afraid to tell anyone with a RedHat system to do
> it right, because I have no idea what RH munged to make that
> work without problems.

I've been running RH9 with this /etc/hosts for a few months, with
no visible problems:

127.0.0.1 localhost localhost.localdomain
127.0.0.2 zenith.homelinux.net zenith

I've just changed it to the following, and will drop a followup if
any adverse effects result:

127.0.0.1 localhost
127.0.0.2 zenith.homelinux.net zenith
127.0.0.3 localhost.localdomain

Ed Murphy <emurphy42@socal.rr.com> wrote:
>On Sun, 30 Nov 2003 08:33:06 -0900, Floyd Davidson wrote:
>
>> Whatever, sometimes it's hard to convince people that 127.0.0.1
>> shouldn't have *anything* other than localhost associated with it.
>> But I'm always afraid to tell anyone with a RedHat system to do
>> it right, because I have no idea what RH munged to make that
>> work without problems.
>
>I've been running RH9 with this /etc/hosts for a few months, with
>no visible problems:
>
>127.0.0.1 localhost localhost.localdomain
>127.0.0.2 zenith.homelinux.net zenith
>
>I've just changed it to the following, and will drop a followup if
>any adverse effects result:
>
>127.0.0.1 localhost
>127.0.0.2 zenith.homelinux.net zenith
>127.0.0.3 localhost.localdomain

Great! Thanks!

--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@barrow.com

On Sun, 30 Nov 2003 08:54:42 -0800, /dev/rob0 wrote:


> The requisite .fetchmailrc line is this:
> mda "/usr/bin/procmail -t -d $USER"
> (probably substituting the local username for $USER; I am not sure.)
> With this you don't get into the complexities of MTA spam filtering, but
> you're still free to play with procmail filtering at your leisure.
>
> Such difficulties as these in a user's early GNU/Linux days often lead
> to frustration and burnout.

In RH9 I do have a .forward file having the following line

"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #srikanth"

Then with Spamassassin I use to filter out spam.

The same .forward file I created in my home directory in Slack also
(at the time of original posting itself). Still it did not work!

I am at my wits' end.

After using RH, I thought of using slack to use a true unix like OS,
But I am struggling to get thru initial steps itself.
Ok , but I am not going to give up!

Cheeka

On Sun, 30 Nov 2003 08:54:42 -0800, /dev/rob0 wrote:

> In article <87r7zqky7z.fld@barrow.com>, Floyd Davidson wrote:

> but instead point him to this section:
> -m <command> | --mda <command>
> (Keyword: mda) You can force mail to be passed to
> an MDA directly (rather than forwarded to port 25)
> with the --mda or -m option. To avoid losing mail,
> use this option only with MDAs like procmail ...

Hi

Finally as pointed out above the following retrieved may mails

fetchmail -u srikanthns -p pop3 -m "/usr/bin/procmail -d %T" mail.vsnl.com

This was in "man fetchmail", but it was mentioned that it was the
default listening behaviour on SMTP port 25, so I left it.

Now I gave it in command line and it smoothly downloads all the
mails and puts it in var/spool/mail/srikanth.

Now major problem solved and one small grouse.
Spamassassin does not seem to be working though the setup I
did was similar to what I did in RH9.
Must have got some thing to do with Perl shipped with Slack.

Hmmm... Let me see

Thanks for all the help.

Cheeka

In article <pan.2003.12.01.13.46.17.136249@hotmail.com>,
N S Srikanth wrote:
> In RH9 I do have a .forward file having the following line
>
> "|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #srikanth"

You do not need a ~/.forward file to pass incoming mail to procmail,
which is the default LDA anyway.

> Then with Spamassassin I use to filter out spam.

I don't use this so I don't know. Check their docs and maybe
comp.mail.misc or other *.mail.* groups?
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

On Sun, 30 Nov 2003 22:37:44 -0900, Floyd Davidson wrote:

> Ed Murphy <emurphy42@socal.rr.com> wrote:

>>On Sun, 30 Nov 2003 08:33:06 -0900, Floyd Davidson wrote:

>>> Whatever, sometimes it's hard to convince people that 127.0.0.1
>>> shouldn't have *anything* other than localhost associated with it.
>>> But I'm always afraid to tell anyone with a RedHat system to do
>>> it right, because I have no idea what RH munged to make that
>>> work without problems.

>>I've just changed it to the following, and will drop a followup if
>>any adverse effects result:
>>
>>127.0.0.1 localhost
>>127.0.0.2 zenith.homelinux.net zenith
>>127.0.0.3 localhost.localdomain

> Great! Thanks!

No problem. It's been fine so far. (Unless the system has cached
the old contents or something, but I'm not particularly interested
in rebooting just to find out. If it *does* break, it'll be plenty
easy to fix.)