Re: local mail delivery
On Thu, Jun 03, 1999 at 11:48:45PM -0400, Carl Mummert wrote: >Unfortunately, that seems to not be the case...all of the mail is >deliverd to the account which invokes fetchmail. The To: header points >to a local user, but is not delivered to that user. Are you running fetchmail as root, as the procmail manpage suggests? haven't been... just gave it a try...now, instead of all the mail ending up in my normal user account, it ends up in root's mailbox. meteu# cat /etc/aliases | grep root | grep flip root: flip meteu# and I've run newaliases since making this entry... all the mail seems to end up in root's mailbox anyway...like it's skipping sendmail, basically...which is what it's doing, since I'm invoking procmail, sendmail aliases aren't going to do anything... just changed the mda line to "/usr/sbin/sendmail -oem -f%F %T" so, it's accepting the senmail aliases now... however, I'm back to where I started...all of the mail ending up in the flip account even though it is addressed to [EMAIL PROTECTED] (a sendmail alias) or [EMAIL PROTECTED] (a login account)... - flip - [EMAIL PROTECTED]/[EMAIL PROTECTED] -- "Nobody knows where you are, how near or how far... Pile on many more layers, and I'll be joining you there..." -- Pink Floyd, Shine on You Crazy Diamond
Re: local mail delivery
>Unfortunately, that seems to not be the case...all of the mail is >deliverd to the account which invokes fetchmail. The To: header points >to a local user, but is not delivered to that user. Are you running fetchmail as root, as the procmail manpage suggests?
local mail delivery
Alright...got a question...probably has an easy answer, but it's got me stumped I have a virtual hosting system set up; all of the email to my machine is put into a single user mail account at a fulltime host. I then grab this mail using fetchmail and, theoretically, it should be delivered to the local users. However, it's not doing that... the relavent line from my .fetchmailrc file is: poll sakima.octoraro.org user pass mda "/usr/bin/procmail -d %T" Which, according to the fechmail manpage should deliver the mail according to the To: header. Unfortunately, that seems to not be the case...all of the mail is deliverd to the account which invokes fetchmail. The To: header points to a local user, but is not delivered to that user. I am running fetchmail and sendmail from Potato, current as of sometime this afternoon... (though I have no particular attachment to sendmail and probably shouldn't be using it...I just have a smattering of experience with it from my slackware days, whereas I have none with any other mailer...) TIA, - flip - [EMAIL PROTECTED]/[EMAIL PROTECTED] -- A pessimist says the glass if half empty. An optimist says the glass is half full. An engineer says the glass is twice as large as it needs to be.
Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software. A message that you sent could not be delivered to all of its recipients. The following address(es) failed: [EMAIL PROTECTED]: generated |cat >>$home/Mail/test/foo: "cat" command not found for address_pipe transport -- This is a copy of the message, including all the headers. -- Return-path: Received: from localhost (mail.alfaskop.net) [127.0.0.1] (anton) by camilla.emmerfors.net with esmtp (Exim 2.05 #1 (Debian)) id 10oBZB-0001z3-00; Sun, 30 May 1999 21:48:17 +0200 Received: from murphy.debian.org (murphy.debian.org [209.41.108.199]) by mail.alfaskop.net (8.9.1a/8.9.1) with SMTP id TAA19162 for <[EMAIL PROTECTED]>; Sun, 30 May 1999 19:44:52 +0200 Received: (qmail 11057 invoked by uid 38); 30 May 1999 17:43:52 - Resent-Date: 30 May 1999 17:43:51 - Resent-Cc: recipient list not shown: ; X-Envelope-Sender: [EMAIL PROTECTED] Date: Sun, 30 May 1999 19:43:39 +0200 From: "J.H.M. Dassen" <[EMAIL PROTECTED]> To: debian-user@lists.debian.org Subject: Re: ISDN PROBS : Message-ID: <[EMAIL PROTECTED]> Mail-Followup-To: debian-user@lists.debian.org References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <[EMAIL PROTECTED]>; from Rene Feenstra on Sun, May 30, 1999 at 06:29:09PM + Resent-Message-ID: <"pH9mj.A.bsC.XjXU3"@murphy> Resent-From: debian-user@lists.debian.org X-Mailing-List: archive/latest/51064 X-Loop: debian-user@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] On Sun, May 30, 1999 at 18:29:09 +, Rene Feenstra wrote: > Still can't get my ISDN card to connect to my isp It get's installed ok > I've made an chatscript for it using pppconfig . I can't recall having to write a chatscript for ISDN; its setup is somewhat different from an analogue modem setup. See ftp://ftp.cistron.nl/pub/cistron/linux/isdn/ for example scripts and check www.deja.com's archives of nl.comp.os.linux; I'm sure someone wrote up a complete description on how to configure ISDN for use with demon. HTH, Ray -- PATRIOTISM A great British writer once said that if he had to choose between betraying his country and betraying a friend he hoped he would have the decency to betray his country. - The Hipcrime Vocab by Chad C. Mulligan -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to all of its recipients. The
following address(es) failed:
[EMAIL PROTECTED]:
generated |cat >>$home/Mail/test/foo:
"cat" command not found for address_pipe transport
-- This is a copy of the message, including all the headers. --
Return-path:
Received: from localhost (mail.alfaskop.net) [127.0.0.1] (anton)
by camilla.emmerfors.net with esmtp (Exim 2.05 #1 (Debian))
id 10oBZ8-0001z3-00; Sun, 30 May 1999 21:48:14 +0200
Received: from murphy.debian.org (murphy.debian.org [209.41.108.199])
by mail.alfaskop.net (8.9.1a/8.9.1) with SMTP id TAA09154
for <[EMAIL PROTECTED]>; Sun, 30 May 1999 19:36:35 +0200
Received: (qmail 4237 invoked by uid 38); 30 May 1999 17:35:47 -
Resent-Date: 30 May 1999 17:35:47 -
Resent-Cc: recipient list not shown: ;
X-Envelope-Sender: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: XFMail 1.3 [p0] on Linux
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <[EMAIL PROTECTED]>
Date: Sun, 30 May 1999 17:35:52 - (UTC)
Reply-To: Pollywog <[EMAIL PROTECTED]>
Organization: The Pond
From: Pollywog <[EMAIL PROTECTED]>
To: debian-user list
Subject: Re: Changing IP address
Resent-Message-ID: <"qEjYB.A.8BB.ybXU3"@murphy>
Resent-From: debian-user@lists.debian.org
X-Mailing-List: archive/latest/51063
X-Loop: debian-user@lists.debian.org
Precedence: list
Resent-Sender: [EMAIL PROTECTED]
Content-Transfer-Encoding: 8bit
On 30-May-99 George Bonser wrote:
> On Sun, 30 May 1999, Doug Thistlethwaite wrote:
>
>> So far I have had a couple of people help and this is what we have come up
>> with.
>>
>> To change the IP address of a system the following files need to be
>> modified.
>>
>> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
>>
>> executes without any errors.
>>
>> route add -net ${NETWORK}
>>
>> executes and gives the error SIOCADDR: invalid argument
>
> Yeah, if you are using a 2.2.x kernel, comment this line out, the network
> route is auto-added when you ifconfig the interface.
I was having this problem just last night and could not figure out where this
SIOCADDR error was coming from.
--
Andrew
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Problem with mail delivery (Exim+Fetchmail)
Hi, With Exim as the MTA and Fetchmail as the POP agent, I'm having the following problem: $ fetchmail -v -a -u my_id seems to download correctly all mail stored in my ISP, but I always get to read (with Mutt) all messages EXCEPT FOR one. Since fetchmail downloads a number "x" of mail messages, and then I can only see "x-1", I imagine this being a problem with exim. Can anyone help with this? Also, could anyone explain to me how do I get exim to work with procmail and the .forward file? TIA P.S. Just in case it helps, this is how I have exim.conf configured to deliver mail locally: local_delivery: driver = appendfile group = mail mode = 0660 mode_fail_narrower = false file = /home/user/Mail/mbox and this is the only indication for .forward I've seen in exim.conf (perhaps I should change it to something like `file = ~/.forward' or `/home/user/.forward'? userforward: driver = forwardfile no_verify check_ancestor file = .forward modemask = 002 filter -- Horacio [EMAIL PROTECTED] Valencia - ESPAÑA
Re: Fw: Mail delivery failed: returning message to sender
Subject: Fw: Mail delivery failed: returning message to sender Date: Sun, Apr 11, 1999 at 12:14:13AM -0500 In reply to:Chris Hoover Quoting Chris Hoover([EMAIL PROTECTED]): > First off, let me say thanks to those of you who replied to my other posting > about my mail system being hosed. I ended up having to reinstall since it > looked more an more like the first install did not go well. After that I > applied what you guys said and I now have a working email system. > > However, there is still one kink. When I just tried to email myself, it was > bounced back by exim. How can I prevent this? Below is the bouned email > message. > > Thanks, > > chris Chris I know there is a lot to read in the /usr/doc/exim dir, but you should be checking there and the man pages. 1. Have you set up the /etc/email-addresses file? 2. Have you run exim_dbmbuild? 3. Have you looked in /usr/doc/exim/spec.txt? Give a man a fish and you feed him for a day, teach a man to fish and you feed him for life. -- A language that doesn't affect the way you think about programming is not worth knowing. ___ Wayne T. Topa <[EMAIL PROTECTED]>
Fw: Mail delivery failed: returning message to sender
First off, let me say thanks to those of you who replied to my other posting about my mail system being hosed. I ended up having to reinstall since it looked more an more like the first install did not go well. After that I applied what you guys said and I now have a working email system. However, there is still one kink. When I just tried to email myself, it was bounced back by exim. How can I prevent this? Below is the bouned email message. Thanks, chris On Sun, 11 Apr 1999 00:08:42 Mail Delivery System wrote: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to all of its recipients. The > following address(es) failed: > > [EMAIL PROTECTED]: > unknown local-part "wax_man" in domain "bellsouth.net" > > -- This is a copy of the message, including all the headers. -- > > Return-path: <[EMAIL PROTECTED]> > Received: from choover by debian.foo.bar with local (Exim 2.05 #1 (Debian)) > id 10WCU6-00089B-00; Sun, 11 Apr 1999 00:08:42 -0500 > Date: Sun, 11 Apr 1999 00:08:42 -0500 > From: Chris Hoover <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: test test test test test > Message-ID: <[EMAIL PROTECTED]> > Reply-To: Chris Hoover <[EMAIL PROTECTED]> > Mime-Version: 1.0 > Content-Type: text/plain > Content-Transfer-Encoding: x-unknown > X-Mailer: Balsa 0.4.9 > Sender: Chris Hoover <[EMAIL PROTECTED]> > > test test test > abcdefg > this is a test
no local mail delivery
I've just installed a fresh slink box, and selected the "Basic" profile during installation. I can't deliver mail locally (exim is installed), and there are no files in /var/spool/mail. Sending an email to a valid user has no effect - it just sits in the mailq, frozen. What can be wrong with it? -- Graham
Re: Slow mail delivery
Zack Brown writes: > I had that problem. But in /etc/init.d/smail change the "-q10m" to "-q10s" > and see if that helps. Now you have smail waking up and running the queue every ten seconds. Put this in /etc/ppp/ip-down.d/runq: #!/bin/sh runq And type 'chmod 750 runq'. Now the mail queue will run every time your ppp link goes down. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: Slow mail delivery
> [EMAIL PROTECTED] wrote: > > > > I'm reposting this message since I've never seen my original come > > through: > > > > I'm having problems with mail delivery on my local box. When I d/l my > > mail from my isp (using fetchmail), it is taking over 5 minutes > > (probably closer to 10) for the mail to get delivered, i.e. for the > > machine to say I have new mail, not for it to come down from my isp. > > Any ideas on what could be causing this, and how to fix it? > > > > You are not alone. smail and fetchmail here. I had that problem. But in /etc/init.d/smail change the "-q10m" to "-q10s" and see if that helps. I don't know why the default is a ten minute wait. We should at least get an option during installation. Anyway, good luck. Zack > Paul Serice
Re: Slow mail delivery
[EMAIL PROTECTED] writes: > I'm reposting this message since I've never seen my original come > through: > > I'm having problems with mail delivery on my local box. When I d/l my > mail from my isp (using fetchmail), it is taking over 5 minutes > (probably closer to 10) for the mail to get delivered, i.e. for the > machine to say I have new mail, not for it to come down from my isp. > Any ideas on what could be causing this, and how to fix it? I use exim and I have the same behaviour; when more than 10 messages arrive exim doesn't deliver them at once; in the log file there is: no immediate delivery: more than 10 messages received in one connection this is controled by some exim options (see queue_only_load) Hubert Fauque
Re: Slow mail delivery
[EMAIL PROTECTED] wrote: > > I'm reposting this message since I've never seen my original come > through: > > I'm having problems with mail delivery on my local box. When I d/l my > mail from my isp (using fetchmail), it is taking over 5 minutes > (probably closer to 10) for the mail to get delivered, i.e. for the > machine to say I have new mail, not for it to come down from my isp. > Any ideas on what could be causing this, and how to fix it? > You are not alone. smail and fetchmail here. Paul Serice
Re: Slow mail delivery
Hi .. This has been a problem for myself aswell. I used to run a few mailing lists (500+ people on each) with smartlist and smail. Things worked great and as an email came in it was sent out to the list vary quickly. Since I have upgraded to sendmail 8.8.8-20 i'm almost afraid to start the larger lists back up. After the mail comes in it sits in the /var/spool/mqueue directory for about 5 minutes then can take up to another 10 minutes to forward it to a list of 50 people. I believe it also queues all out-going mail aswell. This is not good. I have been told that there is an option to not queue incoming mail but no-one has been able to tell me what it is and i have not been able to find it in the docs. If anyone can tell me (and obviously a few others) how can we speed up the processing and sending of mail. Opinions of changing from sendmail to smail of qmail are not a solution or option. Any help to sort this problem is very much needed. -Rob On Sat, 21 Nov 1998 [EMAIL PROTECTED] wrote: > I'm reposting this message since I've never seen my original come > through: > > I'm having problems with mail delivery on my local box. When I d/l my > mail from my isp (using fetchmail), it is taking over 5 minutes > (probably closer to 10) for the mail to get delivered, i.e. for the > machine to say I have new mail, not for it to come down from my isp. > Any ideas on what could be causing this, and how to fix it? > > Thanks, > > Chris
Slow mail delivery
I'm reposting this message since I've never seen my original come through: I'm having problems with mail delivery on my local box. When I d/l my mail from my isp (using fetchmail), it is taking over 5 minutes (probably closer to 10) for the mail to get delivered, i.e. for the machine to say I have new mail, not for it to come down from my isp. Any ideas on what could be causing this, and how to fix it? Thanks, Chris
Slow mail delivery
Can someone tell me why my mail delivery on my local machine is so slow? When I d/l my mail using fetchmail from my isp, the mailer daemon takes over 5 minutes to deliver it. Why, and how do I fix it? Chris
pros and cons for procmail as local mail delivery agent?
Michael Grimm <[EMAIL PROTECTED]> writes: > I recently installed procmail in order to sort incoming > mail into specific mail folders. ... > According to the docs one can install procmail as the > local mail delivery agent (MDA), and one can get rid of > the procmail entry in the .forward file. ... > Before doing so I have some questions for the experts: > > 1. What are the pro and cons for MDA substitution ? > 2. If I substitute my MDA by procmail will that break >future smail and/or procmail upgrades ? > 3. Is there a config utility for procmail available ? Procmail sucks. In particular, its code is such an mass of spaghetti that no human could maintain it with any confidence. This is very dangerous in a mail handling program because when it loses mail you may not notice. This is not idle speculation; Red Hat shipped a broken procmail (as their MDA) for a year before anybody reported it. It was losing mail (on occasion) all that time, for thousands of people. The only thing that could prevent this sort of problem is a mail auditing system: When a message is received, it is logged. When a MUA examines a message, that is logged too. A cron job scans the log periodically and reports messages received but not examined even after later messages have been examined. FWIW its language, for describing how to handle mail, sucks too. Nathan Myers [EMAIL PROTECTED]
pros and cons for procmail as local mail delivery agent?
Hi - I have installed smail receiving mail via UUCP; runs perfectly well. I recently installed procmail in order to sort incoming mail into specific mail folders. And that works well with a .forward and .procmailrc file in my users home directories. But I'm a bit puzzeled by the docs in /usr/doc/procmail, and I have to admit that I'm not an expert when it comes to email ;-( According to the docs one can install procmail as the local mail delivery agent (MDA), and one can get rid of the procmail entry in the .forward file. But in order to do so one needs to remove the current MDA, and one needs to edit the /etc/smail/transports file as well. Before doing so I have some questions for the experts: 1. What are the pro and cons for MDA substitution ? 2. If I substitute my MDA by procmail will that break future smail and/or procmail upgrades ? 3. Is there a config utility for procmail available ? Thanks to all, Michael -- We are living in a world without walls and fences, now. So why should one need Windows and Gates, then ? - Unknown
Re: exim: never stop Mail delivery failed
There is one alias for root and that is maric and is real. The host 193.231.157.5 exists in the DNS database. On Fri, 16 Oct 1998, Nathan E Norman wrote: > On Fri, 16 Oct 1998, ing.Bubulac Angela Tatiana wrote: > > : Ok. It work but now I receive in that user a lot of messages like that: > : Cron<[EMAIL PROTECTED]> /usr/sbin/exim -q && false with the next contnBet > : 1998-10-16 12:09:01 queue run: process 23976 crashed with signal 11 while > : delivering 0zUD7c-0004xc-00 > : 1998-10-16 12:09:02 queue run: process 23981 crashed with signal 11 while > : delivering 0zUDM9-00055V-00 > : 1998-10-16 12:09:03 queue run: process 23986 crashed with signal 11 while > : delivering 0zUDaf-0005Cy-00 > : 1998-10-16 12:09:03 queue run: process 23991 crashed with signal 11 while > : delivering 0zUE3h-0005TT-00 > : 1998-10-16 12:09:04 queue run: process 23996 crashed with signal 11 while > : delivering 0zUElF-0005qr-00 > : > : The paniclog and mainlog files increase rapidly. I installed exim when I > : installed debian with dselect and I was root. > : > : this is a sample from mainlog file: > : 6 12:23:10 0zTurN-98-00 => maric ([EMAIL PROTECTED]) > : <[EMAIL PROTECTED]> D=localuser T=local_del > : 6 12:23:10 0zTurN-98-00 Completed > : 6 12:23:11 0zTucu-8t-00 => maric ([EMAIL PROTECTED]) > : <[EMAIL PROTECTED]> D=localuser T=local_del > : 6 12:23:11 0zTucu-8t-00 Completed > : 6 12:23:11 0zTvKP-AT-00 => maric ([EMAIL PROTECTED]) > : <[EMAIL PROTECTED]> D=localuser T=local_del > : 6 12:23:11 0zTvKP-AT-00 Completed > : ... > : 1998-10-16 12:46:51 refused relay > : (host reject) to <[EMAIL PROTECTED]> from <[EMAIL PROTECTED]> > : H=(maric)... > : 1998-10-16 12:53:01 Start queue run: pid=24401 > : 1998-10-16 12:53:28 0zTnfQ-4E-00 ** root@: unrouteable mail domain "" > : 1998-10-16 12:53:28 0zUFwG-0006Lb-00 Error while handling error message: > : at least one malformed recipient > : 1998-10-16 12:53:28 0zTnfQ-4E-00 Process failed (1) when writing error > : message to root@ > : 1998-10-16 12:53:28 0zTtRH-us-00 Message is frozen > : 1998-10-16 12:53:28 0zTq92-pr-00 Message is frozen > : > : rejectlog file: > : 1998-10-16 12:14:57 refused relay (host reject) to <[EMAIL PROTECTED]> > : from <[EMAIL PROTECTED]> H=(maric) [193.231.157.5] > : > -- > : 1998-10-16 12:46:51 refused relay (host reject) to <[EMAIL PROTECTED]> > : from <[EMAIL PROTECTED]>H=(maric) [193.231.157.5] > : > -- > : > : Any suggestion? > > Last time I saw this I had not set up an alias for the root account. > Exim seems to dislike selivering mail to the root account. > > Edit /etc/aliases and make sure that ONE alias exists for the user > "root", and that it refers to a real mail account somewhere. > > -- > Nathan Norman > MidcoNet 410 South Phillips Avenue Sioux Falls, SD > mailto:[EMAIL PROTECTED] http://www.midco.net > finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) > > >
Re: exim: never stop Mail delivery failed
On Fri, 16 Oct 1998, ing.Bubulac Angela Tatiana wrote: : Ok. It work but now I receive in that user a lot of messages like that: : Cron<[EMAIL PROTECTED]> /usr/sbin/exim -q && false with the next contnBet : 1998-10-16 12:09:01 queue run: process 23976 crashed with signal 11 while : delivering 0zUD7c-0004xc-00 : 1998-10-16 12:09:02 queue run: process 23981 crashed with signal 11 while : delivering 0zUDM9-00055V-00 : 1998-10-16 12:09:03 queue run: process 23986 crashed with signal 11 while : delivering 0zUDaf-0005Cy-00 : 1998-10-16 12:09:03 queue run: process 23991 crashed with signal 11 while : delivering 0zUE3h-0005TT-00 : 1998-10-16 12:09:04 queue run: process 23996 crashed with signal 11 while : delivering 0zUElF-0005qr-00 : : The paniclog and mainlog files increase rapidly. I installed exim when I : installed debian with dselect and I was root. : : this is a sample from mainlog file: : 6 12:23:10 0zTurN-98-00 => maric ([EMAIL PROTECTED]) : <[EMAIL PROTECTED]> D=localuser T=local_del : 6 12:23:10 0zTurN-98-00 Completed : 6 12:23:11 0zTucu-8t-00 => maric ([EMAIL PROTECTED]) : <[EMAIL PROTECTED]> D=localuser T=local_del : 6 12:23:11 0zTucu-8t-00 Completed : 6 12:23:11 0zTvKP-AT-00 => maric ([EMAIL PROTECTED]) : <[EMAIL PROTECTED]> D=localuser T=local_del : 6 12:23:11 0zTvKP-AT-00 Completed : ... : 1998-10-16 12:46:51 refused relay : (host reject) to <[EMAIL PROTECTED]> from <[EMAIL PROTECTED]> H= : 1998-10-16 12:53:01 Start queue run: pid=24401 : 1998-10-16 12:53:28 0zTnfQ-4E-00 ** root@: unrouteable mail domain "" : 1998-10-16 12:53:28 0zUFwG-0006Lb-00 Error while handling error message: : at least one malformed recipient : 1998-10-16 12:53:28 0zTnfQ-4E-00 Process failed (1) when writing error : message to root@ : 1998-10-16 12:53:28 0zTtRH-us-00 Message is frozen : 1998-10-16 12:53:28 0zTq92-pr-00 Message is frozen : : rejectlog file: : 1998-10-16 12:14:57 refused relay (host reject) to <[EMAIL PROTECTED]> : from <[EMAIL PROTECTED]> H=(maric) [193.231.157.5] : -- : 1998-10-16 12:46:51 refused relay (host reject) to <[EMAIL PROTECTED]> : from <[EMAIL PROTECTED]>H=(maric) [193.231.157.5] : -- : : Any suggestion? Last time I saw this I had not set up an alias for the root account. Exim seems to dislike selivering mail to the root account. Edit /etc/aliases and make sure that ONE alias exists for the user "root", and that it refers to a real mail account somewhere. -- Nathan Norman MidcoNet 410 South Phillips Avenue Sioux Falls, SD mailto:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Re: exim: never stop Mail delivery failed
Ok. It work but now I receive in that user a lot of messages like that: Cron<[EMAIL PROTECTED]> /usr/sbin/exim -q && false with the next contnBet 1998-10-16 12:09:01 queue run: process 23976 crashed with signal 11 while delivering 0zUD7c-0004xc-00 1998-10-16 12:09:02 queue run: process 23981 crashed with signal 11 while delivering 0zUDM9-00055V-00 1998-10-16 12:09:03 queue run: process 23986 crashed with signal 11 while delivering 0zUDaf-0005Cy-00 1998-10-16 12:09:03 queue run: process 23991 crashed with signal 11 while delivering 0zUE3h-0005TT-00 1998-10-16 12:09:04 queue run: process 23996 crashed with signal 11 while delivering 0zUElF-0005qr-00 The paniclog and mainlog files increase rapidly. I installed exim when I installed debian with dselect and I was root. this is a sample from mainlog file: 6 12:23:10 0zTurN-98-00 => maric ([EMAIL PROTECTED]) <[EMAIL PROTECTED]> D=localuser T=local_del 6 12:23:10 0zTurN-98-00 Completed 6 12:23:11 0zTucu-8t-00 => maric ([EMAIL PROTECTED]) <[EMAIL PROTECTED]> D=localuser T=local_del 6 12:23:11 0zTucu-8t-00 Completed 6 12:23:11 0zTvKP-AT-00 => maric ([EMAIL PROTECTED]) <[EMAIL PROTECTED]> D=localuser T=local_del 6 12:23:11 0zTvKP-AT-00 Completed ... 1998-10-16 12:46:51 refused relay (host reject) to <[EMAIL PROTECTED]> from <[EMAIL PROTECTED]> H= 1998-10-16 12:53:01 Start queue run: pid=24401 1998-10-16 12:53:28 0zTnfQ-4E-00 ** root@: unrouteable mail domain "" 1998-10-16 12:53:28 0zUFwG-0006Lb-00 Error while handling error message: at least one malformed recipient 1998-10-16 12:53:28 0zTnfQ-4E-00 Process failed (1) when writing error message to root@ 1998-10-16 12:53:28 0zTtRH-us-00 Message is frozen 1998-10-16 12:53:28 0zTq92-pr-00 Message is frozen rejectlog file: 1998-10-16 12:14:57 refused relay (host reject) to <[EMAIL PROTECTED]> from <[EMAIL PROTECTED]> H=(maric) [193.231.157.5] -- 1998-10-16 12:46:51 refused relay (host reject) to <[EMAIL PROTECTED]> from <[EMAIL PROTECTED]>H=(maric) [193.231.157.5] -- Any suggestion? TIA \\\___/// \\ - - // ( @ @ ) -oOOo-(_)-oOOo *Bubulac Angela Tatiana - National Institute for R&D of Materials Physics* * Bucuresti - Magurele P.O.B. MG-7 * * Romania* *e-mail: [EMAIL PROTECTED] | phone :401-7805385 int.1380 * *[EMAIL PROTECTED] | 401-7806925 * * | 401-7804573 * --Oooo oooO ( ) ( )) / \ ((_/ \_) On Fri, 16 Oct 1998, George Bonser wrote: > On Fri, 16 Oct 1998, Bubulac Angela Tatiana wrote: > > > hello, > > I think the problems never stops. This is one of the sense of life. > > Although the message I sent arrive to its destination (in my case a user > > in doamin citon.ro) continuouslyI receive messages like this > > (even from messages that was send yesterday): > > Please tell me what is wrong or what is happen. > > Create an alias in the /etc/alias file for root that points to your user > account, for example: > > root: tatia > > Root mail will then be delivered to a suer account and you will not have > problems will attempting to read anything in /root. I wonder what the real > problem is ... I think it is because exim does not run as root so when it > looks for a .forward or filter file for the root user, it fails to gain > access to that directory. > > > George Bonser > > The Linux "We're never going out of business" sale at an FTP site near you! > >
exim: never stop Mail delivery failed
hello, I think the problems never stops. This is one of the sense of life. Although the message I sent arrive to its destination (in my case a user in doamin citon.ro) continuouslyI receive messages like this (even from messages that was send yesterday): Please tell me what is wrong or what is happen. Date: Fri, 16 Oct 1998 10:23:02 -0700 From: Mail Delivery System <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Mail delivery failed: returning message to sender This message was created automatically by mail delivery software. A message that you sent could not be delivered to all of its recipients. The following address(es) failed: [EMAIL PROTECTED]: Permission denied: failed to chdir to /root: retry timeout exceeded -- This is a copy of the message, including all the headers. -- Return-path: <[EMAIL PROTECTED]> Received: from alpha1.infim.ro [193.231.44.2] by router.citon.ro with smtp (Exim 1.92 #1 (Debian)) id 0zUCC9-0004Yw-00; Fri, 16 Oct 1998 08:53:37 -0700 Received: from localhost by alpha1.infim.ro; (5.65v3.2/1.1.8.2/20May97-1214PM) id AA04147; Fri, 16 Oct 1998 07:54:00 +0200 Date: Fri, 16 Oct 1998 07:54:00 +0200 (EET) From: "ing.Bubulac Angela Tatiana" <[EMAIL PROTECTED]> To: maric <[EMAIL PROTECTED]> Subject: Re: your mail In-Reply-To: <[EMAIL PROTECTED]> Message-Id: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Au fost doua probleme. Fara ici nu puteam rezolva si a doua problema. On Fri, 16 Oct 1998, maric wrote: > Buna dimineata. Multumesc pt. rezolvare. Ai gasit ceva, sau ne-au conectat cei de la ici? > P.S. Before the exim starts to function normal I had a lot of frozen messages.
Re: MTA hostname masquerading, and local mail delivery
On Sun, 14 Dec 1997 22:17:17 EST, wrote: > > Well, you've certainly confused me. :) At least I can communicate clearly that I am confused. > Well, let me tell you what my machine is set up to do - it may help > you find a solution to your problem. More informationon how I > acheived my machine's setup can be found at > http://www.math.jhu.edu/~martind/mybox.html (a page which already > needs updating, despite only being about a month old...) I went through your and Steve Kosteke's (sp?) files last night. I was looking for two things before deciding to switch to smail: rules to rewrite the hostname (masquerade) on a user basis at the system level, and I want my local mail to be delivered without smtp server awareness. Towards the end of this I have a new criteria. > My machine is only connected to the internet intermittently (ppp > connection), and so it really has no fixed IP address or permanent > hostname visible from the outside. Internally, my machine always has > the hostname "cush". (why "cush"? Well, I'd already named the > terminal connected to it "nimrod", so...) Um.. cush:nimrod ?? Hmm.. I guess you had to be there. :-) > When I (as "[EMAIL PROTECTED]") send a piece of mail to "root" or to > "[EMAIL PROTECTED]", it gets sent to the root account on my machine. Same > goes for when I send a piece of mail to [EMAIL PROTECTED] or just > postmaster. (and when I send a message to "[EMAIL PROTECTED]", it goes to my > girlfriend's account on my machine). All these messages have > "[EMAIL PROTECTED]" as the From: address. Presumably it gets sent without your smtp server's awareness. OK, that's the second criteria I'm looking for, so I see smail can do that. > When I send a mail message to debian-user@lists.debian.org or > [EMAIL PROTECTED] or indeed to any non-cush address, the mail > is sent (as soon as my ppp connection goes up) to my department's smtp > server, which then sends it where it needs to go. On the way out, > smail on my machine re-writes the from address to > "[EMAIL PROTECTED]" (and puts some sort of appropriate value in > as the Sender field). That way, people can reply to me (or mail can > get bounced back to me) and it will get into a mailbox that I have > fetchmail (on my machine) check regularly. This is all completely > transparent to the MTA; as far as it's concerned, I might as well have > my own domain name. (that is, I don't have to set any variables in my > mail reader to tell it to use a different From: line) I think you mean outbound mail header rewriting is transparent to your MUA (or email client), not your MTA (smail). I understand that. Is your outgoing mail hostname rewriting done for all users (i.e.: including root) ? I've gotten this to work on a user basis with sendmail by masquerading globally and excluding root, but with some resulting conflicts; namely that all mail awaits the smtp server, which subsequently causes local mail to be undeliverable, but I read the headers in /var/spool/mailq, and it's right. :-) A new potential criteria for my MTA has arisen: One question I've skirted is if root or other users who do not have isp accounts should be allowed to send non-local mail. If they do, they'll have invalid "From:" lines in their headers, no matter if the hostname is rewritten or not--shouldn't non-local mail sent from users without an isp account be disallowed? How can I only allow specific users access to the smtp server (to send non-local mail)? > At the moment my machine doesn't deal nicely with mail that is > forwarded through it, (i.e. from the outside back to the outside) but > I should probably just be killing those mails anyway. > > Also, I've noticed with this setup that pine complains vociferously, > even though everything is just fine - I'm trying something out in a > couple days that ought to shut it up, though. I'm not sure what you mean by Pine complains but everything is fine. However, shutting up Pine (and thus my isp, the authors of Pine) is a good thing, as long as it is complete. While I await further clarification from you, I'm going to check into some crufty sendmail features I recently discovered. Thanks for the response, sendmail config is pretty difficult. -- David Stern [EMAIL PROTECTED] http://weber.u.washington.edu/~kotsya/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: MTA hostname masquerading, and local mail delivery (correction)
[EMAIL PROTECTED] (Daniel Martin at cush) writes: > > fetchmail (on my machine) check regularly. This is all completely > transparent to the MTA; as far as it's concerned, I might as well have > my own domain name. (that is, I don't have to set any variables in my > mail reader to tell it to use a different From: line) Ooops. I meant transparent to the MUA there; of course my MTA (which is smail, btw) has to know about the From: line translation - after all, it's the one doing it! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: MTA hostname masquerading, and local mail delivery
David Stern <[EMAIL PROTECTED]> writes: > There are a lot of things about mail delivery that I'm unsure of right > now. Having put more time into thinking about exactly what I want, I've > become less certain about my configuration needs. Well, you've certainly confused me. :) > What I mean is that I want mail from root to [EMAIL PROTECTED] > n to be delivered without the smtp server ever knowing about it, and > vice versa. > > Does anyone do this? Which MTA do you use? Where are the rules or > facilities to configure this? I'm willing to try just about anything > that will work. If I've lost my marbles, please suggest something > better. Well, let me tell you what my machine is set up to do - it may help you find a solution to your problem. More informationon how I acheived my machine's setup can be found at http://www.math.jhu.edu/~martind/mybox.html (a page which already needs updating, despite only being about a month old...) My machine is only connected to the internet intermittently (ppp connection), and so it really has no fixed IP address or permanent hostname visible from the outside. Internally, my machine always has the hostname "cush". (why "cush"? Well, I'd already named the terminal connected to it "nimrod", so...) When I (as "[EMAIL PROTECTED]") send a piece of mail to "root" or to "[EMAIL PROTECTED]", it gets sent to the root account on my machine. Same goes for when I send a piece of mail to [EMAIL PROTECTED] or just postmaster. (and when I send a message to "[EMAIL PROTECTED]", it goes to my girlfriend's account on my machine). All these messages have "[EMAIL PROTECTED]" as the From: address. When I send a mail message to debian-user@lists.debian.org or [EMAIL PROTECTED] or indeed to any non-cush address, the mail is sent (as soon as my ppp connection goes up) to my department's smtp server, which then sends it where it needs to go. On the way out, smail on my machine re-writes the from address to "[EMAIL PROTECTED]" (and puts some sort of appropriate value in as the Sender field). That way, people can reply to me (or mail can get bounced back to me) and it will get into a mailbox that I have fetchmail (on my machine) check regularly. This is all completely transparent to the MTA; as far as it's concerned, I might as well have my own domain name. (that is, I don't have to set any variables in my mail reader to tell it to use a different From: line) At the moment my machine doesn't deal nicely with mail that is forwarded through it, (i.e. from the outside back to the outside) but I should probably just be killing those mails anyway. Also, I've noticed with this setup that pine complains vociferously, even though everything is just fine - I'm trying something out in a couple days that ought to shut it up, though. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
MTA hostname masquerading, and local mail delivery
Hi, There are a lot of things about mail delivery that I'm unsure of right now. Having put more time into thinking about exactly what I want, I've become less certain about my configuration needs. Originally I thought it best to masquerade globally, as this is not email client specific, which is important in case I decide to try out another mail client, and exclude root. The problem is that all mail gets queued up for the smtp server, and mail to root is undeliverable (even when connected to my smtp server). Now I'm thinking I want to masquerade the hostname on a user by user basis (at the system level, for outgoing mail) and also for mail from and to local users to be delivered locally without the smtp server being in the loop, if that is consistent--it sounds complex and I don't know if it is or not. What I mean is that I want mail from root to [EMAIL PROTECTED] n to be delivered without the smtp server ever knowing about it, and vice versa. Does anyone do this? Which MTA do you use? Where are the rules or facilities to configure this? I'm willing to try just about anything that will work. If I've lost my marbles, please suggest something better. -- David Stern [EMAIL PROTECTED] http://weber.u.washington.edu/~kotsya/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mail delivery error message
It's Bill Leach <[EMAIL PROTECTED]>. He's been having problems with fetchmail/exim/procmail. He's aware of the problem and I think he's going to go to sendmail soon. Brandon - Brandon Mitchell <[EMAIL PROTECTED]> "We all know linux is great... it PGP: finger -l [EMAIL PROTECTED] does infinite loops in 5 seconds" Phone: (757) 221-4847 --Linus Torvalds -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
mail delivery error message
Hi, Two days ago I began getting the following error messages when I responded to [EMAIL PROTECTED] and [EMAIL PROTECTED], which I did twice. The standard mailing list footer is on the mail, it appears to come from the mailing-list, but the From: address reads Mail Delivery System <[EMAIL PROTECTED]> . It's pretty confusing to me. Who's mail delivery software is generating this error message? ([EMAIL PROTECTED] or [EMAIL PROTECTED](is this debian?)?) What is the cause of this error message? (some procmail recipe? specifically how was it triggered?) What corrective action can I take? (clueless, but I'd like this to stop) David Stern bin24sO2Bq1g0.bin Description: message David Stern StarOffice 4.0 for Linux Beta Install Guide http://weber.u.washington.edu/~kotsya/
Re: mail delivery notification
Hi, >>"Stephen" == Stephen Zander <[EMAIL PROTECTED]> writes: Stephen> Lukas Eppler wrote: >> When a mail server is set up properly, you can use the command >> 'finger [EMAIL PROTECTED]' to see when your recipient checked his mail for >> the last time. Stephen> Assuming the admin is supporting fingerd, the machine is not Stephen> behind a firewall, etc, etc. And assuming that the fingerd actually supports the mailbox retrieval time. (I assure you, I have read my mail since wednesday). I do not wish to give out this information, so no fingerd on my machine shall ever report when the recipient checked his mail. I'm glad my ISP agrees. manoj __> finger [EMAIL PROTECTED] [datasync.com] Username: srivasta Userlog Last seen Wed Oct 08 09:58 AM (CDT) Project: Debian GNU/Linux -- "Things could be worse. Suppose your errors were counted and published every day, like those of a baseball player." Anonymous Manoj Srivastava mailto:[EMAIL PROTECTED]> Mobile, Alabama USAhttp://www.datasync.com/%7Esrivasta/> -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mail delivery notification
Lukas Eppler wrote: > When a mail server is set up properly, you can use the command 'finger > [EMAIL PROTECTED]' to see when your recipient checked his mail for the last > time. Assuming the admin is supporting fingerd, the machine is not behind a firewall, etc, etc. Stephen --- "Normality is a statistical illusion." -- me -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mail delivery notification
On Thu, 9 Oct 1997, Richard S. Gray wrote: > How do I go about ensuring that an email message has been received? > In other words, is there a way for me to get a notification mailed back > to me that the message has been delevered and opened? When a mail server is set up properly, you can use the command 'finger [EMAIL PROTECTED]' to see when your recipient checked his mail for the last time. -- Lukas Eppler (godot) http://www.fear.ch telnet://soil.fear.ch: talk:[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mail delivery notification
On Thu, 9 Oct 1997, Richard S. Gray wrote: > How do I go about ensuring that an email message has been received? > In other words, is there a way for me to get a notification mailed back > to me that the message has been delevered and opened? Well, if it can't be delivered, generally you'll get an error message returned (by email) to you. It's pretty reliable that way. Will [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.cis.udel.edu/~lowe/ * Good Idea: Feeding Stray Cats in the Park. Bad Idea: Feeding Stray Cats in the park ... to a bear. * -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
mail delivery notification
Hi, How do I go about ensuring that an email message has been received? In other words, is there a way for me to get a notification mailed back to me that the message has been delevered and opened? Thanks, Scott Gray -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Force smail immediately retry mail delivery.
Which is the correct way to force smail immediately retry sending e-mail for which there was an error? Nicola Bernardelli <[EMAIL PROTECTED]> --- Please use <[EMAIL PROTECTED]> for messages from any kind of robot, such as mailing lists. From that address no autoresponse messages will return even when I'm not at home. --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mail-delivery-agents?
Hi Lamar I hope you don't mind that I put this back onto the list as other people might wonder about this too. Lamar> Hi, Dirk. I seem to be having some trouble getting posts to the Lamar> debian-user list, so I'm mailing you directly. Lamar> Lamar> You posted something about using procmail _and_ pop to sort your Lamar> mail. I was wondering how you invoke procmail? I, too, use Lamar> popclient to get my mail, and I'd _love_ to be able to have procmail Lamar> (or slocal or something) filter it for me. It is all in the procmail manpages --- but as those are quite detailed it hard to find as first sight. Note also that Debian procmail package has, as many other packages, a lot of documentation in /usr/doc/ and /usr/doc/example/. 1. I start popclient as (indented by a TAB for readability) popclient -s -3 -P ~/.file-with-password host.that.has.mail to get my mail to my local machine. 2. One needs a file ~/.forward of the following form "|IFS=' '&&exec /usr/bin/procmail -f-||exit 75 #edd" where the end must #" as a fallback strategy. This passes the mail to the procmail program. 3. A file ~/.procmailrc describes the sorting rules. There are lots of examples in the manpage, and the /usr/doc/examples/procmail directory. But as a concrete example, here are some pieces. If it looks all to strange, than it's probably time to review a Unix book with something on regular expressions. I just show some entries as it is mostly repetitive ~/.procmailrc -- # edd 26.10.95 installed from adapted version from /usr/doc/examples/procmail PATH=$HOME/bin:/usr/bin:/bin:/usr/local/bin:. MAILDIR=$HOME/mail # use `usual' default and not this one: DEFAULT=$MAILDIR/mail.in LOGABSTRACT=all LOGFILE=$MAILDIR/log/procmail :0: # mail To or CC ctan-ann * (^To|^CC|^Resent-).*ctan-ann@(shsu.edu|RELAY.URZ.UNI-HEIDELBERG.DE) in.ctan-announce :0: # mail To or CC debian-announce * (^To|^CC|^Resent-)[EMAIL PROTECTED](debian.org|pixar.com) in.debian-announce :0: # mail To or CC debian-bugs, debian-bugs-done * (^To|^CC|^Resent-).*debian-bugs(-done)[EMAIL PROTECTED](debian.org|pixar.com) in.debian-bugs :0: # Another one for new bugs system * (^To|^CC|^Resent-)[EMAIL PROTECTED] in.debian-bugs :0: # mail To or CC debian-changes * (^To|^CC|^Resent-)[EMAIL PROTECTED](debian.org|pixar.com) in.debian-changes :0: # mail To or CC debian-devel * (^To|^CC|^Resent-)[EMAIL PROTECTED](debian.org|pixar.com) in.debian-devel :0: # mirror logs * ^To: edd * ^Subject: mirror update$ in.mirror-update - :0: always starts a new rule section. Line with * describes rules, if there are several they are ANDed together. The last line shows the folder into which a message is put. Hope this helps, Dirk -- Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
Re: mail-delivery-agents?
Rob Browning <[EMAIL PROTECTED]> writes: Several people have asked me for my Gnus setup, so I'll post it here. Hope no one's offended, but it has a fairly high signal to noise ratio if you're interested in gnus for mail with debian. This is stuff I've sent to a couple of people before. Feel free to ask if you have any questions. Gnus supports a number of backends for mail. It can handle RMAIL, mh, etc, but I would recommend that you switch to using the nnml back end. It's much faster since it generates NOV overview databases (the same ones used by news servers) for all the mail folders. Other than that it stores mail just like mh, one message per file. Makes scripting over messages easy, but it can be hard on the inodes :> I think that nnml is compatible with mh, but only if you don't use both at the same time. I think that gnus won't notice changes made by mh with this method until restart and vice versa. I'f you're already using mh, you don't have to do anything special to use nnml other than tell gnus to use it. It will then run over your mh heirarchy and automatically generate the databases. That's what I did. All my code assumes you are using nnml, but that should only be an issue in a couple of places where I set up the mail group servers. I'm going to assume for now that you don't want to use the bleeding edge release, and that the one that came with your emacs is OK. Is it emacs-19.31.1? If not, you may need the newer version of Gnus (or emacs). I will have info below about how to use the bleeding edge if you're interested. I'm using 5.2.38 to write this and it works great. Gnus treats mail groups (as opposed to news groups) specially with respect to deleting articles. The normal rule is: "if it's a mail group, never delete anything unless specifically told to, and then only after the expiration period." You expire mail articles with "E" in the summary buffer. The default expire period is two weeks. If any article is two weeks old and has been expired, it is deleted. This is kind of nice if you later (within two weeks) decide you really did need some old message. Also, expired articles (until their deletion) still show up in threading histories, etc. You should also look in the info pages (gnus' are quite complete, Lars is insanely prolific) at the section on "Topics". This allows you to organize your groups in collapsible outline form. With respect to file system layout, I have my groups set up like this: ~/Mail/Incoming/inbox(incoming mail that doesn't go anywhere else) ~/Mail/Incoming/debian-bugs (debian bug list) ~/Mail/Incoming/... (other assorted mail groups) and for outgoing stuff: ~/Mail/Outgoing/misc-mail ~/Mail/Outgoing/misc-news this used to be the default in gnus, but in the latest version, it saves no mail by default, so I explicitly enable this in my .emacs. For news (don't forget to check out the info pages on persistent articles and asynchronous fetching -- too cool): ~/News/... (all Gnus related stuff for *incoming* news goes here) Note that it might make more semantic sense for misc-news to go under ~/News, but it turns out that would be pretty awkward to manage with the way Gnus wants to handle things right now. I don't think you could do it without more hassle than it's worth, and the way I have it now, all personal writings are in one subdir. A couple of other things of note. If you just want to read mail, without going through the time consuming (at 28.8) process of contacting the news server and getting the current news group status, you just use M-x gnus-no-server instead of M-x gnus to launch gnus. One caveat, you might notice that all of the mail groups vanish along with the news groups when you do this (i.e. when you run gnus-no-server). That's just because groups have levels of "activeness", and gnus-no-server only shows groups of level 2 or lower. Unfortunately all groups, including mail groups, are created at level 3 by default, so they vanish with gnus-no-server. To see them again, you just need to launch gnus the old fashioned way (M-x gnus) and then use the set level command to set the level of all your mail groups to 2. You can set the levels via "S l" with the cursor on the relevant group in the Group buffer. In order to actually get your mail, you might be able to use pop directly from gnus (I think that's supported now, but I'm not sure), but I just use popclient to grab my mail from all the relevant machines, and then let gnus suck up the mail from my normal system mailbox, which it does by default. Gnus automatically gets your new mail when you launch it, but if you want to incorporate all the new mail after launching gnus, you can use "g" from the group buffer which updates all the mail and news groups, or "2 g" which only does groups level 2 or higher, i.e. the mail groups (there are other commands too, see M-g, for example, which works from a mail summary buffer). Incoming mail is split in
Re: mail-delivery-agents?
And Dale - If you're thinking of going with emacs clients, there's an smtpmail.el package. Not to stunt your budding mail-admin-ship, but maybe it'd do the job. I don't use it but a decent number of people seem to. http://www.cs.washington.edu/homes/voelker/ntemacs/contrib/smtp> is the most recent locale I've seen (that was off the Gnus mailing list, I have no relations with NT, thank you please! :-) -- Ed Donovan [EMAIL PROTECTED] (reader should note unhealthy emacs-junkie gleam in poster's eye)
Re: mail-delivery-agents?
[EMAIL PROTECTED] writes: > I can really recommend emacs with the vm mode. Really. My personal favorite is Gnus. It does a *wonderful* job with mail. Threading, filtering, deleting duplicates, etc... Getting it set up just the way I wanted was a little tricky, but anyone who's interested can mail me, and I'll give you an intro. -- Rob
Re: mail-delivery-agents?
Dale Scheetz writes: Dale> The current way I manage my e-mail involves using popclient to get Dale> incoming e-mail from my ISP (mail.polaris.net) to dwarf's incoming Dale> mail folder on my machine (dwarf.polaris.net), Same here. I advocate [EMAIL PROTECTED], which forwards to [EMAIL PROTECTED], my wife's Debian box on campus, from where I popclient everything to the house ([EMAIL PROTECTED], dynamic IP). Dale> outgoing mail is handled by Pine using SMTP. I use smail, locally and for outgoing mail. _Very_ easy to setup and change all the time because Ian Jackson wrote a fantastic /usr/sbin/smailconfig. The only problem is that you have to "fake" another email address for outgoing mail. There are several ways to do it, directly with emacs, pine (as you compiled the switch in, on my hint :-) and elm, or via smail indepently of the MUA as was recently discussed on debian-user. I also use procmail to sort my mail into 21 (!!!) different mail folders for different mailing lists. Dale> I would like to try some other mail readers like elm and emacs but Dale> none of these seem to be able to do SMTP and so require the presence Dale> of a mail-delivery-agent. I can really recommend emacs with the vm mode. Really. Dale> I know I have heard pro and con discussions about smail vs sendmail Dale> but am still confused. Also I hear hints that qmail (?) will soon be Dale> a Debian package. I am a complete idiot when it comes to mail Dale> systems, so please be simple and clear in your answer ;-) Goes with smail. Use the "smarthost" feature of the smailconfig for outgoing mail. Dale> What do I need to understand to install and use any of the available Dale> packages? Nothing, basically :-) Dale> If I am going to go to the trouble o1f learning to install a Dale> mail-delivery-agent I will want to be able to filter mail to various Dale> mail-folders based on the source of that mail. You can already do that with your existing setup. Just install procmail, and email me for examples. Dale> If that is not available in the mail-delivery-agent, then point me Dale> to a package that will work with the target mail-delivery-agent. Dale> Dale> Thanks in advance for any help, Pleasure. -- Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd
mail-delivery-agents?
The current way I manage my e-mail involves using popclient to get incoming e-mail from my ISP (mail.polaris.net) to dwarf's incoming mail folder on my machine (dwarf.polaris.net), outgoing mail is handled by Pine using SMTP. I would like to try some other mail readers like elm and emacs but none of these seem to be able to do SMTP and so require the presence of a mail-delivery-agent. I know I have heard pro and con discussions about smail vs sendmail but am still confused. Also I hear hints that qmail (?) will soon be a Debian package. I am a complete idiot when it comes to mail systems, so please be simple and clear in your answer ;-) What do I need to understand to install and use any of the available packages? If I am going to go to the trouble of learning to install a mail-delivery-agent I will want to be able to filter mail to various mail-folders based on the source of that mail. If that is not available in the mail-delivery-agent, then point me to a package that will work with the target mail-delivery-agent. Thanks in advance for any help, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
