Re: exim (probably broken thread)
On Sun, Dec 17, 2000 at 11:49:47AM -0600, Phil Brutsche wrote: exim can be configured to run from inetd - I have the commented-out line Ok, thanks for all the help. I'll try and muddle through this. But I have a direction now. Jonathan -- Hey, I think I finally got the hang of i-
Re: exim (probably broken thread)
On Sat, Dec 16, 2000 at 04:02:04PM +0100, Carel Fellinger wrote: okee, this probably means that your /etc/inetd.conf got hoosed, unless you are running exim in daemon mode. Somewhere you need to find lines like: Hi, I didn't know taht one could run exim in naything but daemon mode? How can I set it upotherwise and have it work with fetchmail? Thanks, Jonathan -- Hey, I think I finally got the hang of i-
Re: exim (probably broken thread)
On Sun, Dec 17, 2000 at 10:26:41AM +0100, Jonathan Gift wrote: ... Hi, I didn't know taht one could run exim in naything but daemon mode? How can I set it upotherwise and have it work with fetchmail? There are some long winding threads going on on setting up exim and fetchmail, but normally it's a snap:) Per default exim is started up from inet.d, but if you once set it up to run in daemon mode, all you have to do is add a line to /etc/inetd.conf: #:MAIL: Mail, news and uucp services. smtpstream tcp nowait mail/usr/sbin/exim exim -bs You'll have to check your exim crontab, it might have been changed to deal with daemon mode too. For fetchmail just use fetchmailconf. -- groetjes, carel
Re: exim (probably broken thread)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... On Sat, Dec 16, 2000 at 04:02:04PM +0100, Carel Fellinger wrote: okee, this probably means that your /etc/inetd.conf got hoosed, unless you are running exim in daemon mode. Somewhere you need to find lines like: Hi, I didn't know taht one could run exim in naything but daemon mode? How can I set it upotherwise and have it work with fetchmail? exim can be configured to run from inetd - I have the commented-out line smtpstream tcp nowait mail/usr/sbin/exim exim -bs in /etc/inetd.conf. fetchmail can be told to deliver mail by calling an external program (ie /usr/sbin/exim with the appropriate command-line parameters) rather than try to connect to an SMTP server. - -- - -- Phil Brutsche [EMAIL PROTECTED] GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC GPG key id: 50DE1CFC GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6PPy9/ZTSZFDeHPwRArMTAJ4nLZNoSbYsgBbrD3GP2hfIRsB89ACdHNx1 12laQUuJ+b5o4x/ta8XfPmA= =4lx3 -END PGP SIGNATURE-
Re: exim (probably broken thread)
On Sun, 17 Dec 2000, Phil Brutsche wrote: fetchmail can be told to deliver mail by calling an external program (ie /usr/sbin/exim with the appropriate command-line parameters) rather than try to connect to an SMTP server. It's even possible to remove exim from the picture completely in some cases. I have fetchmail, procmail, and ssmtp installed. I use the fetchmail config option 'mda /usr/bin/procmail -d %T' to have fetchmail deliver straight to procmail, which sorts the mail and dumps it into the appropriate mail folders. Then ssmtp is configured to send all mail using my ISP's SMTP server, so that anything that needs to use /usr/sbin/sendmail still works. Pros: * Noticeably faster than using a MTA to deliver large amounts of mail (like the linux-kernel mailing list), since it cuts down on the number of synchronous file writes * Nothing bound to port 25 Cons: * Can't be used to deliver local-local mail * No mail queueing * Nothing bound to port 25 :) * Less flexible than using an MTA Brad
Re: exim (probably broken thread)
On Sat, Dec 16, 2000 at 09:36:53AM -0500, A R wrote: ... [EMAIL PROTECTED]:~$ telnet localhost smtp Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused [EMAIL PROTECTED]:~$ okee, this probably means that your /etc/inetd.conf got hoosed, unless you are running exim in daemon mode. Somewhere you need to find lines like: #:MAIL: Mail, news and uucp services. smtpstream tcp nowait mail/usr/sbin/exim exim -bs if that smtp line is missing, add it, do as root /etc/init.d/inetd reload and try again. -- groetjes, carel
Re: exim (probably broken thread)
Carel Fellinger wrote: On Sat, Dec 16, 2000 at 09:36:53AM -0500, A R wrote: ... [EMAIL PROTECTED]:~$ telnet localhost smtp Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused [EMAIL PROTECTED]:~$ okee, this probably means that your /etc/inetd.conf got hoosed, unless you are running exim in daemon mode. Somewhere you need to find lines like: #:MAIL: Mail, news and uucp services. smtpstream tcp nowait mail/usr/sbin/exim exim -bs if that smtp line is missing, add it, do as root /etc/init.d/inetd reload and try again. -- groetjes, carel I did it, now look what's coming: Before trying fetchmail again, I am going to close netscape to avoid conflict. I have messenger set to retrieve every minute. So I will report back in a few minutes. [EMAIL PROTECTED]:~/pruebas$ telnet localhost smtp Trying 127.0.0.1... Connected to debian. Escape character is '^]'. 220 debian ESMTP Exim 3.12 #1 Sat, 16 Dec 2000 10:23:21 -0500 quit 221 debian closing connection Connection closed by foreign host. [EMAIL PROTECTED]:~/pruebas$
Re: exim (probably broken thread)
A R wrote: I did it, now look what's coming: Before trying fetchmail again, I am going to close netscape to avoid conflict. I have messenger set to retrieve every minute. So I will report back in a few minutes. [EMAIL PROTECTED]:~/pruebas$ telnet localhost smtp Trying 127.0.0.1... Connected to debian. Escape character is '^]'. 220 debian ESMTP Exim 3.12 #1 Sat, 16 Dec 2000 10:23:21 -0500 quit 221 debian closing connection Connection closed by foreign host. [EMAIL PROTECTED]:~/pruebas$ It is working god now, I was able to fetch it, and read it from the first time. I suppose that next comes tying it to mutt, emacs, or whatever there. Any ideas, pointers, suggestions? Thanks again, Carel. Tony.
Re: exim (probably broken thread)
On Sat, Dec 16, 2000 at 10:28:03AM -0500, A R wrote: ... I did it, now look what's coming: Before trying fetchmail again, I am going to close netscape to avoid conflict. I have messenger set to retrieve every minute. So I will report back in a few minutes. [EMAIL PROTECTED]:~/pruebas$ telnet localhost smtp Trying 127.0.0.1... Connected to debian. Escape character is '^]'. 220 debian ESMTP Exim 3.12 #1 Sat, 16 Dec 2000 10:23:21 -0500 quit 221 debian closing connection Connection closed by foreign host. [EMAIL PROTECTED]:~/pruebas$ great, exim is responding! Back to those fetchmail glitches. Can you try fetchmail -v -v again and send us part of the log? I want to check tose glitches in the fetchmail part are okee now. -- groetjes, carel
Re: exim (probably broken thread)
On Sat, Dec 16, 2000 at 10:38:11AM -0500, A R wrote: ... It is working god now, I was able to fetch it, and read it from the first time. I suppose that next comes tying it to mutt, emacs, or whatever there. Any ideas, pointers, suggestions? Thanks again, Carel. Tony. If fetchmail/exim is working properly your mails get stored locally in /var/mail/tony (or /var/spool/mail/tony which is really the same file as /var/spool/mail is linked to /var/mail). Traditional unix programs like mail and mutt and... look there to get at your mail per default, so no need to configure them:) Forgive me my curiousity, but are those glitches we saw before in the fetchmail log (fetchmail: rejected..., fetchmail: no local matches...) still there? And if not, did you change anything to your fetchmailrc? -- groetjes, carel
Re: exim (probably broken thread)
On Sat, Dec 16, 2000 at 10:38:11AM -0500, A R wrote: A R wrote: I did it, now look what's coming: Before trying fetchmail again, I am going to close netscape to avoid conflict. I have messenger set to retrieve every minute. So I will report back in a few minutes. [EMAIL PROTECTED]:~/pruebas$ telnet localhost smtp Trying 127.0.0.1... Connected to debian. Escape character is '^]'. 220 debian ESMTP Exim 3.12 #1 Sat, 16 Dec 2000 10:23:21 -0500 quit 221 debian closing connection Connection closed by foreign host. [EMAIL PROTECTED]:~/pruebas$ It is working god now, I was able to fetch it, and read it from the first time. I suppose that next comes tying it to mutt, emacs, or whatever there. Any ideas, pointers, suggestions? Thanks again, Carel. Tony. I really like mutt. There is tons of information at their web site about how to customize it to your liking. kent -- In order to make an apple pie from scratch, you must first create the universe. - Carl Sagan
Re: exim (probably broken thread)
Forgive me my curiousity, but are those glitches we saw before in the fetchmail log (fetchmail: rejected..., fetchmail: no local matches...) still there? And if not, did you change anything to your fetchmailrc? -- groetjes, carel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Sorry that didn't answer sooner, I took my mother Christmas shopping for a while. I will run fetchmail -v-v and send the log in a few.
Re: exim (probably broken thread)
If fetchmail/exim is working properly your mails get stored locally in /var/mail/tony (or /var/spool/mail/tony which is really the same file as /var/spool/mail is linked to /var/mail). Traditional unix programs like mail and mutt and... look there to get at your mail per default, so no need to configure them:) Forgive me my curiousity, but are those glitches we saw before in the fetchmail log (fetchmail: rejected..., fetchmail: no local matches...) still there? And if not, did you change anything to your fetchmailrc? Well, it seems that there are some glitches yet: [EMAIL PROTECTED]:~$ fetchmail -v -v fetchmail: 5.3.3 querying postoffice.worldnet.att.net (protocol POP3) at Sat, 16 Dec 2000 13:18:45 -0500 (EST) fetchmail: POP3 +OK InterMail POP3 server ready. fetchmail: POP3 USER arodriguez fetchmail: POP3 +OK please send PASS command fetchmail: POP3 PASS * fetchmail: POP3 +OK arodriguez is welcome here fetchmail: selecting or re-polling default folder fetchmail: POP3 STAT fetchmail: POP3 +OK 1 2675 fetchmail: POP3 LAST fetchmail: POP3 +OK 0 1 message for arodriguez at postoffice.worldnet.att.net (2675 octets). fetchmail: POP3 LIST fetchmail: POP3 +OK 1 messages fetchmail: POP3 1 2675 fetchmail: POP3 . fetchmail: POP3 RETR 1 fetchmail: POP3 +OK 2675 octets reading message 1 of 1 (2675 octets) About to rewrite Return-Path: [EMAIL PROTECTED] Rewritten version is Return-Path: [EMAIL PROTECTED] fetchmail: analyzing Received line: Received: from murphy.debian.org ([216.234.231.6]) by mtiwgwc21.worldnet.att.net (InterMail vM.4.01.03.10 201-229-121-110) with SMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Sat, 16 Dec 2000 18:05:52 + fetchmail: line rejected, mtiwgwc21.worldnet.att.net is not an alias of the mailserver About to rewrite Sender: tony Rewritten version is Sender: [EMAIL PROTECTED] About to rewrite From: A R [EMAIL PROTECTED] Rewritten version is From: A R [EMAIL PROTECTED] About to rewrite To: Carel Fellinger [EMAIL PROTECTED] Rewritten version is To: Carel Fellinger [EMAIL PROTECTED] About to rewrite CC: debian-user@lists.debian.org debian-user@lists.debian.org Rewritten version is CC: debian-user@lists.debian.org [EMAIL PROTECTED] n.org About to rewrite Resent-From: debian-user@lists.debian.org Rewritten version is Resent-From: debian-user@lists.debian.org About to rewrite Resent-Sender: [EMAIL PROTECTED] Rewritten version is Resent-Sender: [EMAIL PROTECTED] fetchmail: no local matches, forwarding to tony fetchmail: SMTP 220 debian ESMTP Exim 3.12 #1 Sat, 16 Dec 2000 13:18:53 -0500 fetchmail: SMTP EHLO localhost fetchmail: SMTP 250-debian Hello tony at debian [127.0.0.1] fetchmail: SMTP 250-SIZE fetchmail: SMTP 250-PIPELINING fetchmail: SMTP 250 HELP fetchmail: forwarding to localhost fetchmail: SMTP MAIL FROM:[EMAIL PROTECTED] SIZE=2675 fetchmail: SMTP 250 [EMAIL PROTECTED] is syntactically correct fetchmail: SMTP RCPT TO:[EMAIL PROTECTED] fetchmail: SMTP 250 [EMAIL PROTECTED] is syntactically correct fetchmail: SMTP DATA fetchmail: SMTP 354 Enter message, ending with . on a line by itself #***fetchmail: SMTP. (EOM) fetchmail: SMTP 250 OK id=147Lv3-9w-00 not flushed fetchmail: POP3 QUIT fetchmail: POP3 +OK arodriguez InterMail POP3 server signing off. fetchmail: not swapping UID lists, no UIDs seen this query fetchmail: SMTP QUIT fetchmail: SMTP 221 debian closing connection fetchmail: Deleting fetchids file. fetchmail: normal termination, status 0 fetchmail: Deleting fetchids file. You have new mail in /var/mail/tony [EMAIL PROTECTED]:~$ %% %%% %%% Now, notice that the changes that I made to .fetchmailrc shoud have taken care of that, here is my .fetchmailrc: [EMAIL PROTECTED]:~$ cat .fetchmailrc # Configuration created Tue Dec 5 14:18:33 2000 by fetchmailconf # and later edited by hand by me, tony, on the 8-dec-2000 set postmaster tony set no bouncemail set properties poll postoffice.worldnet.att.net aka worldnet.att.net, the-sphere.org with proto POP3 user arodriguez is user tony here password not-this-one-of-course options keep [EMAIL PROTECTED]:~$
Re: exim (probably broken thread)
On Sat, Dec 16, 2000 at 01:29:29PM -0500, A R wrote: ... Well, it seems that there are some glitches yet: I've looked again at my own fetchmailrc file, and low and behold I appear to use an extra option:) Just add no dns to your poll postoffice...line and those glitches should be gone. I think I don't fully grasp the docs on this though, so if anybody could explain, thanks. Just to still my curiousity could you first try once more without this no dns thingy,but with a longer aka list: aka mtiwgwc21.worldnet.att.net worldnet.att.net ... -- groetjes, carel
Re: exim (probably broken thread)
Just to still my curiousity could you first try once more without this no dns thingy,but with a longer aka list: aka mtiwgwc21.worldnet.att.net worldnet.att.net ... I did it, next my session: [EMAIL PROTECTED]:~$ fetchmail -v -v fetchmail: 5.3.3 querying postoffice.worldnet.att.net (protocol POP3) at Sat, 16 Dec 2000 16:23:03 -0500 (EST) fetchmail: POP3 +OK InterMail POP3 server ready. fetchmail: POP3 USER arodriguez fetchmail: POP3 +OK please send PASS command fetchmail: POP3 PASS * fetchmail: POP3 +OK arodriguez is welcome here fetchmail: selecting or re-polling default folder fetchmail: POP3 STAT fetchmail: POP3 +OK 1 3531 fetchmail: POP3 LAST fetchmail: POP3 +OK 0 1 message for arodriguez at postoffice.worldnet.att.net (3531 octets). fetchmail: POP3 LIST fetchmail: POP3 +OK 1 messages fetchmail: POP3 1 3531 fetchmail: POP3 . fetchmail: POP3 RETR 1 fetchmail: POP3 +OK 3531 octets reading message 1 of 1 (3531 octets) About to rewrite Return-Path: [EMAIL PROTECTED] Rewritten version is Return-Path: [EMAIL PROTECTED] fetchmail: analyzing Received line: Received: from murphy.debian.org ([216.234.231.6]) by mtiwgwc24.worldnet.att.net (InterMail vM.4.01.03.10 201-229-121-110) with SMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Sat, 16 Dec 2000 21:11:36 + fetchmail: line rejected, mtiwgwc24.worldnet.att.net is not an alias of the mailserver About to rewrite Sender: jtc Rewritten version is Sender: [EMAIL PROTECTED] About to rewrite From: John Carline [EMAIL PROTECTED] Rewritten version is From: John Carline [EMAIL PROTECTED] About to rewrite CC: debian-user@lists.debian.org Rewritten version is CC: debian-user@lists.debian.org About to rewrite To: debian-user@lists.debian.org Rewritten version is To: debian-user@lists.debian.org About to rewrite Resent-From: debian-user@lists.debian.org Rewritten version is Resent-From: debian-user@lists.debian.org About to rewrite Resent-Sender: [EMAIL PROTECTED] Rewritten version is Resent-Sender: [EMAIL PROTECTED] fetchmail: no local matches, forwarding to tony fetchmail: SMTP 220 debian ESMTP Exim 3.12 #1 Sat, 16 Dec 2000 16:23:10 -0500 fetchmail: SMTP EHLO localhost fetchmail: SMTP 250-debian Hello tony at debian [127.0.0.1] fetchmail: SMTP 250-SIZE fetchmail: SMTP 250-PIPELINING fetchmail: SMTP 250 HELP fetchmail: forwarding to localhost fetchmail: SMTP MAIL FROM:[EMAIL PROTECTED] SIZE=3531 fetchmail: SMTP 250 [EMAIL PROTECTED] is syntactically correct fetchmail: SMTP RCPT TO:[EMAIL PROTECTED] fetchmail: SMTP 250 [EMAIL PROTECTED] is syntactically correct fetchmail: SMTP DATA fetchmail: SMTP 354 Enter message, ending with . on a line by itself #***.fetchmail: SMTP. (EOM) fetchmail: SMTP 250 OK id=147OnO-CE-00 not flushed fetchmail: POP3 QUIT fetchmail: POP3 +OK arodriguez InterMail POP3 server signing off. fetchmail: not swapping UID lists, no UIDs seen this query fetchmail: SMTP QUIT fetchmail: SMTP 221 debian closing connection fetchmail: Deleting fetchids file. fetchmail: normal termination, status 0 fetchmail: Deleting fetchids file. You have new mail in /var/mail/tony [EMAIL PROTECTED]:~$ Notice how there is another rejection, now of mti*24.worldnet.att.net Perhaps using wild * can fix it? Something like aka mtiwgwc*.worldnet.att.net? It also bothers me that the mail comes to tony after bouncing, and I had defined arodriguez is tony here. Also, notice how in my previous posting there is the line this below About to rewrite Sender: tony Rewritten version is Sender: [EMAIL PROTECTED] up to here and there is no [EMAIL PROTECTED] !!! At least, if there is, is not me. ???
Re: exim (probably broken thread)
Hai Tony, Could you save this message and then sent it as attachment back to me? I want to have a closer look at the headers. (no need to send that copy to the list) On Sat, Dec 16, 2000 at 04:35:20PM -0500, A R wrote: ... fetchmail: analyzing Received line: Received: from murphy.debian.org ([216.234.231.6]) by mtiwgwc24.worldnet.att.net (InterMail vM.4.01.03.10 201-229-121-110) with SMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Sat, 16 Dec 2000 21:11:36 + fetchmail: line rejected, mtiwgwc24.worldnet.att.net is not an alias of the mailserver It has been some time since I set up my own fetchmail files, so it takes me some time remembering all:( What is bothering us now is that your pop host is not the same as the host on which the mail is received by your ips, moreover this receiving host changes over time (those mtiwgwc*.worldnet.att.net names). According to the docs this shouldn't bite us in 'single-drop' mode, and here on my machine that's right. But on your computer it fails, looks like you're run- ning in 'multi-drop' mode. To check this out could you mail the outcome of fetchmail -V run as tony? Somewhere to the end of its output you are likely to find a line that is similar to: Single-drop mode: 1 local name(s) recognized. If it says Single-drop, then your fetchmail isn't working like mine (you are running potato? no woody aka unstable intermingled I hope) If it says Multi-drop, then you'll have to look carefully at your ~/.fetchmailrc file; a single * could switch you into that mode. Back to the aka line in multi-drop mode. I've done a lot of testing this night and it looks like the aka hosts have to be spelled out, no domain wildcarding or whatever, just plain listing them all. This differs from the docs, so I wonder what I'm overlooking. In multi-drop mode Fetchmail parses the headers to see to whom the mail is addressed, per default it uses the Recieved:-lines. In those lines this changing mail-server-name pops-up and fetchmail bails out complaining that it doesn't match the mailhost. At home I've more luck specifying Delivered-to: as header-field to parse. My ips's MTA (postfix) adds those containing the To-envelop header. And that header has the expected host name. We have to have a look at your headers after receiving mail to figure out if this could work for you. Here it is working, nontheless I have added this no dns fetchmail: no local matches, forwarding to tony As the mailhost was not the same as the pophost fetchmail failed at first. Now he is using the fallback deliver address (postmaster) Notice how there is another rejection, now of mti*24.worldnet.att.net Perhaps using wild * can fix it? Something like aka mtiwgwc*.worldnet.att.net? I had no luck trying this tonight. It also bothers me that the mail comes to tony after bouncing, and I had defined arodriguez is tony here. Yes, but fetchmail chookes over those changing mailhosts and falls back to delivery to postmaster. This will change once we got that sorted out. Also, notice how in my previous posting there is the line this below About to rewrite Sender: tony Rewritten version is Sender: [EMAIL PROTECTED] Your mail agent (mutt?) or exim isn't configured properly, all mailheaders should have fully qualified email addresses. And a fully qualified domain name has at least 1 dot in it. -- groetjes, carel
