Re: bind

2001-02-04 Thread Marc A. Donges
.com. ns.emergeknowledge.com. 86400 IN MX 10 mail.emergeknowledge.com. ns.emergeknowledge.com. 86400 IN A 64.59.157.18 Now where I left a line blank add: emergeknowledge.com.86400 IN A 64.59.157.18 -- _ _ Marc A. Donges+49 791

Re: partitioning 45 gig HD

2001-02-04 Thread Marc A. Donges
YI, I currently have: hda1 50MB /boot [Primary] hda2 2000MB /home [Primary] hda5100MB / [Logical] hda6 2500MB /usr [Logical] hda7 1000MB /var [Logical] Where '/usr' is too big and '/home' and '/var' are too small... -- _ _ Marc A. Donges

Re: AMD, Cyrix and 2.2r don't mix

2001-02-04 Thread Marc A. Donges
flavors of i386 machines, including a dual Pentium (old Compaq Proliant), several self-built systems (with Intel 486, AMD 486, Cyrix P166+, AMD K6-II, AMD Athlon processor) and a notebook of unknown origin. What Version of Debian are you using? Are you booting from the CD? Did you provide any

Re: .procmailrc multiple actions

2001-02-02 Thread Marc A. Donges
t;'" on the sendmail-command-line to create a zero-return-address. Another problem exists in the recipy. Strange things, that you will not understand at first glance will happen, if the rewritten Mail contains any Resent-(To|Cc|Bcc):-Headers. They take precedence over the (To|Cc):-he

Re: mutt + seperate folder for lists

2001-02-02 Thread Marc A. Donges
ders? I honestly don't know what will happen... Marc -- _ _ Marc A. Donges+49 791 51804 'v' <[EMAIL PROTECTED]> / \ PGP-Key(DSA): 1024D/1C9ECFF2 W W Fingerprint: 58B9 07A6 CBB1 7016 EB1D 7D35 EEBE 67DC 1C9E CFF2

Re: email headers from 'russian porn'

2001-02-02 Thread Marc A. Donges
be fully qualified, and sendmail and postfix (dunno about >> qmail) will both canonicalize the address to themselves. > > oddity? i'm using exim and look at this: > > From: "Lovely Johny" This is being added by fetchmail, I guess. Marc -- _ _ M

Re: unwanted log-message from icmplogd

2001-02-02 Thread Marc A. Donges
ds. So PLEASE how can I prevent our systems from > producing this message in particular? Wow, that is often. I'm receiving this once every three minutes in our network (which is also large, BTW), it is caused by rwhod-packets. You could of course try to find out which service sends out the pack