Re: Exim fail to receive mails !?!
[EMAIL PROTECTED] (George Bonser) wrote:
>
>Since I do UUCP, all of my installations are non-standard. I run Exim but
>Debian does not know that, it thinks I am running smail. I simply
>hand-copied the Exim binary into place on the target machines, created the
>needed directories, set all permissions as Debian does for exim. I have
>Exim facing the internet for SMTP and it hands off mail destined for my
>uucp sites to smail which does the routing/spooling. It is really a kluge.
This sounds really bogus.
Do you *really* need smail's bangpath handling? With this, I mean using
the uucp maps etc. to figure out the correct routing etc. If all you
have is a number of uucp neighbours with which you have to exchange
email, exim is fully up to the task, given a couple of changes to the
exim.conf file.
I use exim with uucp on two debian systems. These are globally the
changes needed:
In the global part:
trusted_users = mail:uucp
for receiving mail correctly.
In the transports section:
uucp:
driver = pipe
user = nobody
command = "/usr/bin/uux -r - $host!rmail ${local_part}"
return_fail_output = true
In the routers section, below any possible smtp entries:
xs4all:
driver = domainlist
transport = uucp
route_list = "xs4all.nl xs4all"
I only want to send emails over the uucp link if they're destined for
the xs4all.nl domain, which explains the route_list. However, "transport
= uucp" works fine for the smarthost and other entries as well.
Furthermore a rewrite rule may be necessary if your uucp partner sends
mail to a bang path. I don't need that with xs4all, but I can look it up
on the other system (not local for me at the moment) if necessary.
Paul Slootman
--
home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED]
http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
"In my opinion MS is a lot better at making money than it is
at making good operating systems." (Linus Torvalds, August 1997)
Re: Vim leaves ~ files
[EMAIL PROTECTED] (Miquel van Smoorenburg) wrote: >In article <[EMAIL PROTECTED]>, Danny ter Haar <[EMAIL PROTECTED]> wrote: >>Hint for the maintainer: please set a default of NO backups ! > >Has already been done in the version in slink IIRC That would be great (haven't checked yet). Note that other people's concerns for vim to do the "safe" thing (i.e. leave the backups until you know how vim works) is bogus, as I've been using vim for at least 5 years (hmmm, version 1.27) and "knew" that vim doesn't leave backups. Otherwise, if backups are preferred, put them somewhere all together like /tmp so that the system isn't littered with these ~ files everywhere. Now to remove the "set tw=78" which causes gratuitious line wraps, very painful when editing e.g. a shell script. Rely on the autocommands to turn this feature on for emails etc, that works fine! Also, put "set directory=~/tmp,/var/tmp,/tmp,.". This causes the "swap file" (where the backup stuff is kept if something happens in the middle of an edit session) to be put in one of those directories, the first if possible etc. That prevents those pesky ".swp" files appearing in the current directory, which screw up your terminal when you do "grep bla *" due to control characters in the swap file being printed. In fact, at one time in Vim development, the current directory was the default, until people protested for the reasons I listed above. Now debian's vim maintainer restored the old problems :-( The first thing I do on a new debian installation is edit /etc/vimrc :-( The second thing is 'rm /etc/vimrc~' ... Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands "In my opinion MS is a lot better at making money than it is at making good operating systems." (Linus Torvalds, August 1997)
Re: "standard" HAMM connecting on its own to internet?
[EMAIL PROTECTED] (Doug Thistlethwaite) wrote: > >I am having a strange problem with my recently upgraded BO --> HAMM system. I >have a router (pipeline 50) connected to a very small network (2 machines). I >have noticed that my ISDN line has been active when no one is using the >computers at all. > >Is there something in the "standard" (just upgraded) HAMM release that would >periodically connect to the internet by itself? During the day, I get charged >a I've noticed that samba is prone to causing dialouts. According to a cursory glance at the problem, samba binds to all available interfaces, and broadcasts regularly to announce its workgroups and stuff like that. Those broadcasts may be causing it. Alternatively, Win95 pc's also do similar broadcasts, which is a problem when using masquerading in combination with an isdn card in autodial mode... In both cases, ipfwadm can be your friend :-) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands "In my opinion MS is a lot better at making money than it is at making good operating systems." (Linus Torvalds, August 1997)
Re: Is there a Debian package for SANE 0.74 or 0.73?
[EMAIL PROTECTED] wrote: >Does anyone have, or know the whereabouts of, the latest SANE package >for Debian? Even 0.73 would be OK. I need support for my Agfa Snapscan >scanner which isn't in the 'current' 0.72 package. Tell dselect to use the 'unstable' distribution, it is in the 2.1-to-be version. Alternatively, if you don't want lots of other updates as well, get ftp://ftp.debian.org/pub/debian/dists/slink/main/binary-i386/graphics/sane_0.74-1.deb Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands "In my opinion MS is a lot better at making money than it is at making good operating systems." (Linus Torvalds, August 1997)
Re: "standard" HAMM connecting on its own to internet?
On Thu 03 Sep 1998, Doug Thistlethwaite wrote: > What is ipfwadm? I am almost positive it is my win 95 system but I have no > idea what Ipfwadm is the tool for IP FireWall ADMinistration. With it you can tell it not to accept certain IP packets, and to block forwarding. It's possible that forwarding (i.e. passing packets from one interface through to another) is turned on by default, so that if your win95 system does a broadcast for netbios, that gets sent to the isdn interface, which triggers a dialout. Try "ipfwadm -F -p deny". That tells the kernel not to allow any forwarding (forwarding default policy is deny). For more info, look at www.xos.nl/linux/ipfwadm/ . You can also check what IP packet is causing the dialout; debian isdn config by default logs the first outgoing packet which triggers the dialout, look in /var/log/kern.log for lines like: Sep 2 19:39:39 janux kernel: OPEN: 194.109.102.29 -> 194.229.27.42 TCP, port: 15907 -> 21 This shows that the packet originating from IP 194.109.102.29 going to 194.229.27.42 on tcp port 21 is causing the dialout. Port 21/tcp is ftp according to /etc/services, so here someone typed "ftp ftp.nluug.nl" (194.229.27.42 is ftp.nluug.nl). This information can help to track down what the problem is. > is doing it. I've also heard that turning DNS lookups on or off on the win95 system can help... Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Intel Pro 10/100 PCI ethernet adapter
[EMAIL PROTECTED] (justin honold) wrote: >On Mon, 7 Sep 1998, Bruce Jackson wrote: > >> Does this adapter work with Linux 2.0.35? >> >yes. running one fine here. Just make sure it's the "B" version. The first one, which has the 82556 chip, does not and will never work. As you can't check the chip number from the outside of the box, here's intel's code number for the damn thing: EJMNPDPILA8465 (maybe the EJMNPD is not listed on the box, just avoid PILA). Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Why does Debian use ncurses-1.9.9g and not 4.x
George Bonser wrote:
>
>I have modified a few packages in my day and make, for example, a modified
>package of vim with GUI support available on my FTP site.
I believe the current ("standard debian") version of vim is built with
GUI support.
Paul Slootman
--
home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED]
http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Mail reflector how to?
[EMAIL PROTECTED] wrote: >Does anybody know of a mail reflector how to for Debian and could recommend >a mail package to use as such? What exactly do you mean with a "mail reflector" ? Won't a simple alias with any MTA do the trick? Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: PS: moving in mutt.
[EMAIL PROTECTED] wrote: >> I just installed Debian 2.0 via ftp. >> I cannot move up and down in mutt to select individual mails using the >> arrow keys (is that the right expression?) in my keyboard. It just >> tells me: Key is not bound. A bug or a feature? Under Slackware I > >I just realised, that mutt started directly on my computer here at >home has no problems with cursor movement, but only if I rlogin to the >computer at work from an xterm. But both computers have Debian 2.0 >installed. The one at work a very recent installation via ftp (two >days ago), and the one here at home an installation made a few days >after Debian 2.0 was released. What does "echo $TERM" say when you're logged into the remote computer? It should say xterm... It sounds like the wrong TERM value is used. Or the wrong terminfo files are installed, but that sounds unlikely with a normal debian install. Anyway, you can also move in mutt with the "vi"-style keys, so j is the same as a down arrow, and k is the same as an up arrow. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: MTA Frustration: Exim
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] (Damir J. Naden) wrote: >Hi George Bonser; unless Mutt is confused, you wrote: >> On Sat, 19 Sep 1998, Johann Spies wrote: >> >> > I will support that. I have tried maybe a dozen times to get exim running >> > without success. The documentation most of the time explains some >> > technical detail that I am not interested in. I just want to know how to >> > set up the mail on my single PC with a dialup ppp connection to an ISP. >> >> And what I find so strange is that I have never had a problem getting exim >> running. > >I would have to second George here. I have set up my single PC w. the dial-up >connection without any problems. It ran the script at install and answering Me Too. Additionally, Exim is quite easy to use when using complicated stuff as well. On the internet gateway system here at work I have the following features working: - local mail (i.e. to domain .ah.nl) gets delivered via the ethernet to a smarthost. - mail bound for *.xs4all.nl gets routed over an UUCP link, with the From: lines adjusted accordingly. - mail bound for the rest gets queued until the ISDN link comes up. - When the ISDN link comes up, a subtlely different exim config file is put into place, that doesn't queue, but thinks that it's a permanently connected internet host, and the queue is flushed. - When the ISDN link goes down again, the "dial-on-demand" config is put back, and exim queues everything again. - A cron job flushes the queue every hour, for the (unlikely!) case that the link hasn't been up for an hour, leaving outgoing messages gathering dust in the queue. I've also found the exim mailing list more than helpful whenever I got stuck. I've noticed that Exim's author is often the first to respond. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Net problem with an AMD PCnet PCI card (newbie question)
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] wrote: > >I have tried adding the /etc/modules file, also tried rebuilding the kernel >with tulip and de4x5 linked (not as loadable modules). On boot, I get the >following message: > >/dev/tulip.o: init_module: Device or resource busy > >My /etc/conf.modules file: > >alias eth0 tulip >options tulip io=0x200 irq=10 > >Also, if I run tulip_diag with the -p 0x200 flag, it reports a tulip chip at >that address. Umm... For the AMD PCnet card, use the "pcnet32" driver. Even though they're commonly used in Tulip computers, it's not what's called a tulip card; those are manufactured by Digital (or should I say Compaq). Also, you should NEVER have to specify irq / io / whatever for PCI cards. That in itself is an indication that you're using the wrong driver. Of course, if there is another AMD PCnet card that is NOT the PCnet32 card, my apologies. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: exim and uucp
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] wrote:
>
>Then switched to exim (instead of sendmail), that worked better, I
>received email, got confident again, but configuring a mailer to UUCP is
>more work than I thought.
>
>Now I'm waiting for some good prince to come along and help me with that
>:-) (already posted the question "exim and uucp" here today).
Hmm, couldn't find anything with uucp in the subject, so following up
here.
I have exim and uucp working here. In the main configuration settings:
trusted_users = mail:uucp
uucp_from_pattern = "^From ([^ ]+).*remote from (.*)"
uucp_from_sender = "[EMAIL PROTECTED]"
You may have to tweak these, depending on what your upstream uucp host
sends.
In the transports configuration:
uucp:
driver = pipe
user = nobody
command = "/usr/bin/uux -r - $host!rmail ${local_part}"
return_fail_output = true
In the router configuration, below any routers for e.g. infranets:
uucphost:
driver = domainlist
transport = uucp
route_list = "* uucphost"
(replace uucphost with the name of your uucp feed)
Maybe you'll have to play with the "driver" and "route_list" entries
in the last stanza, but that's globally what you need.
Paul Slootman
--
home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED]
http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: how to set up isdn dial-in ?
In article <[EMAIL PROTECTED]> you write: >I've dial-out already running on ippp0. Now I'd like to setup dial-in w/ >PAP or CHAP on ippp1. Which files do I have to touch ... ? Use `isdnconfig' to create an ippp1 interface and an ipppd config for ippp1. Configure /etc/isdn/device.ippp1 and /etc/isdn/ipppd.ippp1 like you would for a dialout. Then, in /etc/isdn/ipppd.ippp1, you need to change the "#noauth" to "auth" (to force the remote side to authenticate itself to your side). I _think_ you can use "name X" to set your system's name to X as far as the other side is concerned. In /etc/isdn/device.ippp1, you need to enable the part of the script that allows incoming phone numbers. It's a "for i in ..." loop that adds all the numbers listed in $REMOTEMSN to the incoming list. >Is there a problem w/ Mickeysoft ? - I saw a ms-chap flag somewhere >(can't remember where it was). AFAIK you only need ms-chap for calling into a NT ppp server, not for calling into linux from ms-windows (any flavour). Otherwise I have one at ftp://ftp.murphy.nl/pub/isdnlinux/ Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: vim has no color after moving uo to slink
In article <[EMAIL PROTECTED]> you write:
>
>I found vim-rt on the debian site. It mentioned syntax highlighting in
>the description. I downloaded it and installed it. The error is gone
>(cuz I let it overwrite my /etc/vimrc), but I still get no syntax
>highlighting :(
Edit /etc/vimrc and remove the first " char from the beginning of these
lines:
"if has("syntax")
" syntax on" Default to no syntax highlightning
"endif
Paul Slootman
--
home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED]
http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: first-time exim
Did you get an answer already? you write: >[EMAIL PROTECTED]:[~]$ ll /var/spool/mail >total 2 >drwxrwsr-x 2 root mail 1024 Feb 1 07:42 ./ >drwxr-xr-x 9 root root 1024 Mar 10 11:27 ../ > >Note the conspicuous absence of /var/spool/mail/dbroseme! What does 'mailq' say? If there's a message in the queue, look at /var/spool/exim/msglog/* for explanation (there's some command to do that, but I like to do it by hand :) It may be a problem with permissions somewhere or whatever. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: truncated inode numbers in cpio
In article <[EMAIL PROTECTED]> you write: >When creating a cpio archive, cpio sometimes gives the message "inode nuber >truncated". > >Do I need to be concerned about this? It means that the default output format (the "old c" format) can't handle those inode numbers. Cpio uses the inode number info to restore hard links when reading an archive back. > or is there a way around the inode >problem? Use -Hnewc when writing (or -Hcrc). See the man page for more info. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: truncated inode numbers in cpio
In article <[EMAIL PROTECTED]> you write: >On 23 Dec 98 13:59:19 GMT, [EMAIL PROTECTED] (Paul Slootman) wroth: >> >>It means that the default output format (the "old c" format) can't >>handle those inode numbers. Cpio uses the inode number info to restore >>hard links when reading an archive back. >> > >I read about the "old c" format in the man pages, but as far as I could tell, >the default was a newer format, still ascii and portable, but without the Read again: -H FORMAT, --format=FORMAT Use archive format FORMAT. The valid formats are listed below; the same names are also recognized in all-caps. The default in copy-in mode is to auto ^^^ matically detect the archive format, and in copy- out mode is "bin".^ ^ Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Using ISDN in Germany
In article <[EMAIL PROTECTED]> you write: > >I'm helping a friend setting up his GNU/Debian machine in Germany. >Sofar we have managed to configure the Card (Fritz AVM1) install it >using modprobe and checking syslog - and everything seems to be alright. > >modprobe hisax type=5 protocol=2 io=0x300 irq=5 id=Fritz Note that previous versions of isdnutils expect the id to be "line0". >Then we configured ppp - using pppconfig - and as device specified >/dev/ttyI0 (thats a zero) You don't want to use syncPPP? >We created the device using /etc/MAKEDEV isdn-tty. You didn't install isdnutils then, I guess? >Jan 12 10:49:35 burchard chat[247]: NO MSN/EAZ^M > >Can anybody help clearify this. Explained already, but better to install the kernel-doc package for your kernel, and read Documentation/isdn/README >Content-Type: text/html; charset=us-ascii ARGHH!!! >I-21020 Ispra(VA) - >Italy > E-mail: [EMAIL PROTECTED] ARGHHH!!! Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: line printer problems / DEC Alpha
In article <[EMAIL PROTECTED]> you write: >Does the Debian distribution for the DEC Alpha have problems with certain >motherboards or other hardware? I am planning to get an alpha system, and >I would like to install Debian. The best thing to do is to ask on debian-alpha (I've cc'ed that and put that as the reply-to). That's where the knowledgeable people (AFAI alpha is concerned :-) hang out. >I have noticed occasionally some remarks that Linuc has some problems with >lp0. It seems that I am victimized by them (when I installed my system I >did change the line printer device from lp1 as suggested by the device >configuration to lp0. Now the spooler accepts print jobs, but they never >get printed (I use Berkeley lpr, have run it successfully in previous >lives, and installed and configured printing on several other systems >without problems). I was trying to reconfigure printing with lp1, but no >luck. Does anybody have a suggestion? Anyone? >Hartmann Schaffer > >PS. Please cc any replies Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: ISDN: HOW TO start?
In article <[EMAIL PROTECTED]> you write: > >I have a new Debian 2.0 distribution running well. I have recompiled the >kernel with PCMCIA and ISDN support, bought an AVM Fritz! PCMCIA card, I don't think that the AVM Fritz! PCMCIA card is supported. Have you managed to get the kernel (i.e. the hisax driver) to see it? >Can anybody post a detailed list of the actions he/she took to get an >ISDN connection done starting from scratch? As noted elsewhere, install isdnutils, and use the 'isdnconfig' script that is offered during the install. After configuring the syncPPP interface, you need to edit the example files the script generates (it also says which files those are). Of course, if you can't get the kernel to recognize the card, it's pointless to install isdnutils... Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: moving "/" sda4 --> sdb1
In article <[EMAIL PROTECTED]> you write: >On Sun, 4 Oct 1998, John Leget wrote: > > : greetings, > : > : I need to move debian from drive 1 to drive 2 ( just deep sixed NT >;0) > : ), what are the steps necessary. > >login as root > >mke2fs /dev/sdb1 >mount /dev/sdb1 /mnt >cd / >find . -xdev | cpio -padm /mnt >umount /mnt >vi /etc/fstab >reboot No, you also need to tell lilo to pass "root=/dev/sdb1" as parameter (and probably to boot the kernel on /dev/sdb1 as well, else there will be surprises when /dev/sda4 gets recycled). Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Need help with Internet connection ISDN.
In article <[EMAIL PROTECTED]> you write: >After hours of reading howto's and scratching my head I finally got Debian >to recognise my Teles 16.3 ISDN-card. It works, and I can call myself >between two TTY's with minicom. Talking to myself is quite boring in the >long run, and I just can't figure out how to connect to my ISP. Does anyone >know about some straight forward recepies for this ?. I am VERY newbie with >Linux, and or Unix. Don't know how to do this with an ordinary modem either. >Please help. Have you installed the 'isdnutils' package? When you install that, it offers to run the 'isdnconfig' script which can create some basic example config files which only need minimal tweaking to connect to most ISPs. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: HELP! how does Debian allocate scsi drives?
To: [EMAIL PROTECTED] Subject: Re: HELP! how does Debian allocate scsi drives? Newsgroups: linux.debian.user In-Reply-To: <[EMAIL PROTECTED]> Organization: Albert Heijn Winkelautomatisering Cc: Bcc: In article <[EMAIL PROTECTED]> you write: > >Now when I reboot the scsi controller sees the scsi drives on both >its channels (its an Adaptec 3940 which has two channels). >Debian seems to reset the controller successfully on both >channels but the boot up fsck reports that three of my drives aren't >there as ext2 filesystems. I'm pretty sure they're all on the same >(second) channel and that that's the channel where the cdrom >came out so I'd like to think the explanation is that removing the >cdrom has thrown the mapping from scsi device ids to /dev >mounts. This is not debian-specific, it's linux kernel specific. Anyway: scsi cdroms are in a different namespace from scsi disks, so adding or removing scsi cdroms will not in any way change the naming of the scsi disks. >I can't get into the machine to check documentation and I can't see >enough detail in "Running Linux" to know if this is the case and, if >so, how to fix it. However, that does read as if linux scans through >the scsi devices allocating /dev/sda /dev/sdb etc sequentially rather >than hard mapping to a scsi id. If so, maybe removing the cdrom True, linux allocates the first scsi disk it sees to /dev/sda, etc. >has thrown the mapping and I should be able to get in as root and >hack the mapping (is it in /etc/fstab?) and correct the problem. >(Seems odd as it allocates cdroms and rw drives separately but ...) > >If not, what's happening?! I can't see that there's likely to have >been a major destruction of the file system on all three drives >particularly given that the controller verifies them happily! You haven't changed the ribbon cables around in replacing the motherboard, and then maybe changed the boot order in the Adaptec setup? It will then boot up from the first disk on the second channel (hence find the kernel), however, linux will still scan the channels in the same order (i.e. first channel A and then channel B). The order is hence changed... >_ANY_ hints, help, thwacks over the head for stupidity gratefully >received. I'm holding back on thwacks for the moment :-) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: exim (was smail) problem
In article <[EMAIL PROTECTED]> you write:
>Problem is that exim doesn't know that
>[EMAIL PROTECTED] is "user" here. Had to set that up for fetchmail, and it
>works great. But when I send mail, my ISP thinks I'm unauthorized
>(obviously, I am) and kicks my mail back. How do I get exim to rewrite my
>header from [EMAIL PROTECTED] to [EMAIL PROTECTED] Can I just get exim to read
Let me check I've understood the problem correctly; your ISP sends you
email at the address <[EMAIL PROTECTED]>, and only accepts email from the
user <[EMAIL PROTECTED]>, but you login as "user" ?
If so, try this at the bottom of your exim.conf:
[EMAIL PROTECTED] "${if match {$header_from:[EMAIL PROTECTED] [EMAIL
PROTECTED] fail }" EFf
This is off the top of my head, but should be in the right direction.
Be sure to check out www.exim.org .
Paul Slootman
--
home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED]
http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: exim config
In article <[EMAIL PROTECTED]> you write: > >I previously used sendmail for my mail needs, but I am trying out exim. >However I am having one difficulty - is there a way to specify a place that >mail for unknown users should be forwarded to? I can't seem to find a way >to do it. Add the following to the end of the directors section: smartuser: driver = smartuser new_address = [EMAIL PROTECTED] Of course, fill in the real host name :-) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: exim queue
In article <[EMAIL PROTECTED]> you write: >On Mon, Nov 09 1998, Leon Breedt spake thus: > >i just noticed something else. > >> i'm running exim on a dialup box, with some success. i can get >> local messages (via fetchmail) delivered fine. >or maybe not so fine. after running fetchmail, i see local messages >aren't all delivered immediately, some of the fetchmail-forwarded messages >are still lurking in the queue. i have to do a runq to get them into >my mailbox. Put this in the main configuration section of /etc/exim.conf: queue_remote = true This should cause it to only queue messages for remote systems; locally delivered messages should then not be queued. For your other question: you can check whether there is an outgoing smtp connection: if netstat --ip -n | grep ':25 *ESTABLISHED' > /dev/null then: smtp connection is active else: no active smtp connection fi or check if there is a sendmail process active: if pidof exim > /dev/null then: exim is running else: no exim process found fi Hmmm, maybe the process is called sendmail and not exim. Experiment. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Exim as default mailer
In article <[EMAIL PROTECTED]> you write: >I was concerned when I >initially looked at it by the statement in the (version 2) manual >(section 39, "Intermittently connected hosts") where it says "Exim was >designed for use on permanently connected hosts, and so it is not >particularly well-suited for use in an intermittently connected >environment." > >As I have a single-user home PC with dial-up access to my ISP, I fall >squarely into the category of users for whom Exim is "not particularly >well-suited". Is this a real problem, or is Exim a good mailer for >dial-up systems? The alternatives are even less suited... I've created two exim.conf files, one for use when I'm online, and one for when I'm offline. I switch these around via /etc/ppp/ip-*.d/exim: ip-up.d/exim: #!/bin/sh case "$PPP_IFACE" in ippp0) cp /etc/exim.conf.online /etc/exim.conf.new mv -f /etc/exim.conf.new /etc/exim.conf # Flush exim queue if [ -x /usr/sbin/exim ]; then /usr/sbin/exim -qf fi ;; esac ip-down.d/exim: #!/bin/sh case "$PPP_IFACE" in ippp0) cp /etc/exim.conf.autodial /etc/exim.conf.new mv -f /etc/exim.conf.new /etc/exim.conf ;; esac I have "queue_remote" in my exim.conf.autodial which means it doesn't attempt to deliver these directly. Just either don't run the cron job that flushes the queue periodically if you don't want connections to happen solely for email delivery (or if you don't have dial-on-demand!). Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Sound recording over-run
In article <[EMAIL PROTECTED]> you write: >What does the message >kernel: Sound: Recording overrun >mean? It means that your application can't take the data out of the kernel buffers quickly enough, which means that the kernel buffers overflow (i.e. are overrun). This can be caused by ide disks and/or too much memory... if you have too much memory, the periodic flush of the buffer cache takes too long. There's a utility you can use to tune those parameters (it's not hdparm, at least not the debian version; I'm not sure what I mean _is_ in debian...). >I am also getting the error: >opening /dev/audio: Device or resource busy Any kernel error at the same time? `dmesg'. Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Sound recording over-run
In <[EMAIL PROTECTED]>: >In <[EMAIL PROTECTED]> Paul Slootman <[EMAIL PROTECTED]> wrote: >>>kernel: Sound: Recording overrun >> >>It means that your application can't take the data out of the kernel >>buffers quickly enough, which means that the kernel buffers overflow >>(i.e. are overrun). This can be caused by ide disks and/or too much >>memory... if you have too much memory, the periodic flush of the >>buffer cache takes too long. There's a utility you can use to tune >>those parameters (it's not hdparm, at least not the debian version; >>I'm not sure what I mean _is_ in debian...). >I'll try to find the utility Paul Slootman refers to. Regarding the kernel I'm pretty sure the utility was available in Slackware, if that helps... >Nov 10 17:08:03 solzhenitsyn kernel: Sound: Recording overrun >Nov 10 17:08:34 solzhenitsyn last message repeated 2975 times >Nov 10 17:08:39 solzhenitsyn last message repeated 718 times [oops] >Nov 10 17:08:39 solzhenitsyn kernel: Process xsynaesthesia (pid: 28300, [...] >Nov 10 17:08:39 solzhenitsyn kernel: Sound: Recording overrun >Nov 10 17:09:10 solzhenitsyn last message repeated 5332 times > >This raises some further questions. > >1) The offending process is dead & buried. Is there some way, short of >a re-boot (which I'd like to avoid at the moment) for the kernel to >"recover" (by which I guess I mean stop producing these error messages) Hmm, it looks like there's still something that has /dev/audio or whatever opened for input... "fuser -k /dev/audio /dev/dsp*" >2) Should I report this to the kernel list? Only if you have all the relevant info that's listed in the kernel's README, such as the symbol table etc. so that the stack trace is converted to a list of function names etc. If you don't have that, the report is useless. (Also look at Documentation/oops-tracing.txt.) Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: exim and local_part
In article <[EMAIL PROTECTED]>: >so everytime a send a message to any user, let say joe.user >exim correctly change the 'to:' field to "[EMAIL PROTECTED]" >but then it claims: > >[EMAIL PROTECTED]: > unknown local-part "joe.user" in domain "my.domain.name" Do you have a user "joe.user" in your password file? If not, then how is exim supposed to know how to deliver the email? If the user's login name is 'joe', you can put aliases into /etc/aliases, e.g.: joe.user: joe Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] | debian: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands
Re: Another Newbie question
On Sat 07 Mar 1998, Oleg Krivosheev wrote: > i installed hamm using disks from unstable > and found there is no > PS/2 mouse device (/dev/psmouse). The PS/2 mouse device is called /dev/psaux (it has been for a long time). Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands -- E-mail the word "unsubscribe" to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
Re: So, anyone knows wtf Apache.pm is? Was: Re: Testing upgrade and consequences
On Wed 14 Mar 2001, Dimitri Maziuk wrote: > > Hmm, interesting... Why tf did I install apache-perl in the first place? Because the combination apache + mod-perl had/has(?) a pretty bad memory leak? Which was why apache-perl was created in the first place. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
Re: ITP: estic (ISTEC ISDN PABX admin program)
On Wed 29 Dec 1999, W. Borgert wrote: > > I already have packaged estic: > > Section: utils > Priority: optional > Upstream Author: Ullrich von Bassewitz <[EMAIL PROTECTED]> > Recommends: isdnutils I'd make this "Suggests:" at most. There are lots of people out there that use an external ISDN TA or router, and who may also have one of these PABXes. "Recommends" means that dselect bugs them _every_ time about this. Does estic properly handle device locks? I.e. write a lock into /var/lock/ ? Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Exim] Re: setting up spamassassin
On Wed 16 Jan 2002, martin f krafft wrote:
>
> sounds like (a) exim does it just like postfix. maybe they document it
> more sophisticatedly, (b) you doubling the load unnecessarily, and (c)
> you are asking for trouble. why not let procmail be MDA?
procmail is in no way light-weight; I'd hesitate to claim that procmail
is less of a load than exim (especially since exim is already in memory,
shared pages and all that).
To keep it on topic: this is how I've configured exim to filter just
about everything through spamassassin before delivery. As a bonus also a
filter to automagically send marked messages to spamcop for reporting.
As a transport:
spam_scan:
driver = pipe
user = uucp
restrict_to_path
path = "/usr/local/sbin:/usr/bin:/bin"
suffix =
command = "spamassassinpipe '${if eq
{$sender_address}{}{mailer-daemon}{$sender_address}}' $pipe_addresses"
Don't ask about the uucp, I have uucp already as a trusted user because
of uucp email, and I couldn't be bothered to add another.
spamassassinpipe is a script in /usr/local/sbin which I'll show below.
As a director, before userforward:
spamcheck:
driver = smartuser
transport = spam_scan
condition = "${if or {{eq {$received_protocol}{spamscanned}} \
{eq {$sender_host_address}{127.0.0.1}}}\
{0}{${if >{$message_size}{100K}{0}{1"
This is the spamassassinpipe:
#!/bin/sh
from="$1"; shift
/usr/bin/spamassassin -P | /usr/sbin/sendmail -oMr spamscanned -f "$from" --
"$@"
That's basically it. This is based on an installation of spamassassin
debian packages from before it was actually in the debian distribution;
so it uses system-wide preferences etc.
This is the relevant begin of my .forward:
# Exim filter
if $h_subject: begins "*SPAM*"
then
pipe "/home/paul/bin/spamtospamcop $sender_address $h_from $h_subject "
save Mail/SPAM
endif
spamtospamcop is a simple script to send the spam to spamcop with a
suitable subject line (so that I can see from spamcop's reply subject
whether it possibly may be non-spam):
#!/bin/sh
sender="$1"; shift
h_from="$1"; shift
subject="`expr \"$1\" : '...\(.*\)'`"
exec spamassassin -d | mailx -s "SPAM [$sender: $h_from: $subject]" [EMAIL
PROTECTED]
Paul Slootman
Re: restarting isdnutils fails
On Wed 29 Nov 2006, Rainer Dorsch wrote: > > I am running a sarge system with an AVM Fritzcard DSL providing ISDN as well. Note: I have no experience with active ISDN cards whatsoever... > vbox3 serves as answering machine. Sometimes the card hangs and I restart the > connection completely using > > silverboxy:/etc/init.d# cat /usr/local/bin/restartPPP > #!/bin/bash > > if ! /sbin/ifconfig |grep ppp0 > /dev/null; then > echo killing pppd > kill -15 `ps uaxwww|grep pppd| grep -v grep | cut -c 10-15` > > echo shutting down DSL connection > /etc/init.d/isdnactivecards stop > /etc/init.d/isdnutils stop > /etc/init.d/capiutils stop My instinct says it would be better to stop isdnutils first, then isdnactivecards. Note also that vboxgetty is run out of inittab, so that will probably keep the ISDN devices busy as well, preventing the removal of the modules. (Sorry for the delay in responding, the fact it was sent to a debian list caused it to be dumped in that folder instead of my inbox.) Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
