[SOLVED] configure exim/fetchmail w/ dialup; daemon trouble.
AWESOME! AWESOME! AWESOME! Adding the indicated line to the exim.conf file appears to have fixed my problem! See bottom of message. Here is a story about perfection: Each time I have posted to this list there has been a response leading to a solution. As a Linux/Debian Newbie such help is indispensable! There have has also been significant learning by taking the time to read the list posts responses. Thanks! Barry Mathieu On Sat, Mar 30, 2002 at 02:19:10AM +0100, Steffen Evers ([EMAIL PROTECTED]) wrote: On Fri, Mar 29, 2002 at 09:23, Barry Mathieu wrote: My problem is unintended DoD. I checked the backup of my old Potato configuration and there was no /etc/ppp/ip-up.d/fetchmail. So, I renamed it to something else in my new Woody setup (fetchmail_daemon). I also issued a /etc/init.d/fetchmail stop. Now there is no way /etc/init.d/fetchmail should be able to run as a daemon when I start DoD by issuing pon. I have ppp configured for DoD; I don't use diald. Sure enough, when the following appeared in my log, the modem began a connection: Mar 29 08:38:02 debian /USR/SBIN/CRON[7292]: (mail) CMD ( if [ -x /usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi) Exim does this every 15 minutes. I definitely don't wan't my computer to obtain a connection every 15 minutes and stay connected for 5 minutes. As a newbie I really don't understand the full ramification of a DNS lookup. After reading the bug report, it appears that exim doesn't think it knows the name of the machine it is currently running on, and to search for, and assign, the name, it resorts to something that begins a modem connection. I simply can't have exim doing this every 15 minutes. I typically only collect mail twice per day, is there a way I could set exim to run using a timed cron job? That is, not run exim as a daemon. I'll start reading. My goal is to have DoD running so using a browser, or sending mail, can be a single step process. I can't believe such a terrible bug is not being more discussed in the mail group. DoD is simply unusable in Debian woody because of this exim bug. I think your are right: it is amazing how little attention this problem has taken so far. However, not so many people like DoD. Most want to have full control over their dail up connection when there are some reasons to be not online all the time. My suggestion for your to solve this problem for the short run is to give up DoD and work with full control instead. This means you use some of the tools like pon/poff to establish and disconnect your connection manually. An alternative would be to use sendmail instead of exim for a while. However, I do not know if this worth the effort to learn how to configure it properly. For me the bug was no real problem as I have a flatrate and ADSL. Anyway, I will post a more aggressive mail in order to underline this problem. As you convinced me that everything is as it should be I checked again the proper solution Philip Hazal and I worked out, but which did not work at that time for some strange reason we could not find. And this way I found out that the problem has disappeared in the current version of exim!!! So, anyone who is annoyed by this DNS lookup of exim can simply set the following option and it should work fine without looking up the name of the localhost all the time (it does here): # This specifies the name of the current host. This is used in the HELO # command for outgoing SMTP messages, and as the default for # qualify_domain. # If it is not set, Exim calls uname() to find it. If this fails, Exim # panics and dies. If the name returned by uname() contains only one # component, Exim passes it to gethostbyname() in order to obtain the # fully qualified version. primary_hostname = MyMachineName I suggest that Mark Baker considers to integrate this in the default exim.conf file. Then he could close the bug #96633 as well. Thanks for your help Ben. I am happy that this beast is finally done! :-) Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie, configure exim/fetchmail w/ dialup; daemon trouble.
On Thu, Mar 28, 2002 at 05:55:53PM +0100, Steffen Evers ([EMAIL PROTECTED]) wrote: On Wed, Mar 27, 2002 at 23:33, Barry Mathieu wrote: I removed the /etc/fetchmailrc file, and issued /etc/init.d/fetchmail stop and then I logged in as root and issued dpkg-reconfigure fetchmail-common and I made sure a non system wide fetchmail setup was completed. Then I issued a, pon and after a few minutes my system connects (initiates ppp to my ISP) without me issuing any command; like a daemon. So my problem is still not fixed. I'm beginning to wonder about exim. Before the system attempts to connect, the following occurs in /var/log/syslog: Mar 27 22:38:01 debian /USR/SBIN/CRON[4209]: (mail) CMD ( if [ -x /usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi) I thought exim simply interacts with /var/spool/mail and did not attempt to create a connection. Maybe I'm wrong? Is your problem about an unintended dial on demand (DoD) or about unintended retrievel of your emails? If it is about DoD than it is for sure this exim bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96633repeatmerged=yes The current Debian woody is simply unusable for DoD with exim. I have spend days to find out more about this bug. Thr problem is that EVERY time exim is started, it initiates a DNS lookup of your local machine name. No matter how you configure it. This is at least true when zou do not have a full qualified domain name for your machine. If someone likes to look after it, I can provide all information I have gatherd about this problem so far. The exim upstream developer gave me some hints as well where the problem could be ... By, Steffen Not very good news to hear. My problem is unintended DoD. I checked the backup of my old Potato configuration and there was no /etc/ppp/ip-up.d/fetchmail. So, I renamed it to something else in my new Woody setup (fetchmail_daemon). I also issued a /etc/init.d/fetchmail stop. Now there is no way /etc/init.d/fetchmail should be able to run as a daemon when I start DoD by issuing pon. I have ppp configured for DoD; I don't use diald. Sure enough, when the following appeared in my log, the modem began a connection: Mar 29 08:38:02 debian /USR/SBIN/CRON[7292]: (mail) CMD ( if [ -x /usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi) Exim does this every 15 minutes. I definitely don't wan't my computer to obtain a connection every 15 minutes and stay connected for 5 minutes. As a newbie I really don't understand the full ramification of a DNS lookup. After reading the bug report, it appears that exim doesn't think it knows the name of the machine it is currently running on, and to search for, and assign, the name, it resorts to something that begins a modem connection. I simply can't have exim doing this every 15 minutes. I typically only collect mail twice per day, is there a way I could set exim to run using a timed cron job? That is, not run exim as a daemon. I'll start reading. My goal is to have DoD running so using a browser, or sending mail, can be a single step process. I can't believe such a terrible bug is not being more discussed in the mail group. Thanks for your help, Barry Mathieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie, configure exim/fetchmail w/ dialup; daemon trouble.
On Fri, Mar 29, 2002 at 09:23, Barry Mathieu wrote: My problem is unintended DoD. I checked the backup of my old Potato configuration and there was no /etc/ppp/ip-up.d/fetchmail. So, I renamed it to something else in my new Woody setup (fetchmail_daemon). I also issued a /etc/init.d/fetchmail stop. Now there is no way /etc/init.d/fetchmail should be able to run as a daemon when I start DoD by issuing pon. I have ppp configured for DoD; I don't use diald. Sure enough, when the following appeared in my log, the modem began a connection: Mar 29 08:38:02 debian /USR/SBIN/CRON[7292]: (mail) CMD ( if [ -x /usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi) Exim does this every 15 minutes. I definitely don't wan't my computer to obtain a connection every 15 minutes and stay connected for 5 minutes. As a newbie I really don't understand the full ramification of a DNS lookup. After reading the bug report, it appears that exim doesn't think it knows the name of the machine it is currently running on, and to search for, and assign, the name, it resorts to something that begins a modem connection. I simply can't have exim doing this every 15 minutes. I typically only collect mail twice per day, is there a way I could set exim to run using a timed cron job? That is, not run exim as a daemon. I'll start reading. My goal is to have DoD running so using a browser, or sending mail, can be a single step process. I can't believe such a terrible bug is not being more discussed in the mail group. DoD is simply unusable in Debian woody because of this exim bug. I think your are right: it is amazing how little attention this problem has taken so far. However, not so many people like DoD. Most want to have full control over their dail up connection when there are some reasons to be not online all the time. My suggestion for your to solve this problem for the short run is to give up DoD and work with full control instead. This means you use some of the tools like pon/poff to establish and disconnect your connection manually. An alternative would be to use sendmail instead of exim for a while. However, I do not know if this worth the effort to learn how to configure it properly. For me the bug was no real problem as I have a flatrate and ADSL. Anyway, I will post a more aggressive mail in order to underline this problem. Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie, configure exim/fetchmail w/ dialup; daemon trouble.
On Wed, Mar 27, 2002 at 11:51:41PM +0100, Steffen Evers ([EMAIL PROTECTED]) wrote: On Tue, Mar 26, 2002 at 23:05, Barry Mathieu wrote: Fetchmail appears to running as a daemon and executes a query for mail every 300 seconds. To attempt to change this, I have a /etc/fetchmailrc with the line for the daemon commented out. I have altered the line for the daemon in /etc/default/fetchmail as follows: If you do not want fetchmail run as a daemon simply remove your /etc/fetchmailrc and the reular bootup scripts will notr start the daemon. Now, you can simply execute it from the command line. I removed the /etc/fetchmailrc file, and issued /etc/init.d/fetchmail stop and then I logged in as root and issued dpkg-reconfigure fetchmail-common and I made sure a non system wide fetchmail setup was completed. Then I issued a, pon and after a few minutes my system connects (initiates ppp to my ISP) without me issuing any command; like a daemon. So my problem is still not fixed. I'm beginning to wonder about exim. Before the system attempts to connect, the following occurs in /var/log/syslog: Mar 27 22:38:01 debian /USR/SBIN/CRON[4209]: (mail) CMD ( if [ -x /usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi) I thought exim simply interacts with /var/spool/mail and did not attempt to create a connection. Maybe I'm wrong? Any suggestion? Thanks for you help, Barry Mathieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie, configure exim/fetchmail w/ dialup; daemon trouble.
Barry Mathieu [EMAIL PROTECTED] writes: I removed the /etc/fetchmailrc file, and issued /etc/init.d/fetchmail stop Yes but that only stops it, not removes the script - and if something else fires up the script. and then I logged in as root and issued dpkg-reconfigure fetchmail-common and I made sure a non system wide fetchmail setup was completed. Then I issued a, pon and after a few minutes my system connects So it should! (initiates ppp to my ISP) You mean fetchmail starts? without me issuing any command; like a daemon. No, its not a daemon. Over in /etc/ppp there is a directory called ip-up.d . This contains scripts which launch certain services (mine has fetchmail, exim, leafnode snort and a few others) when you make a connection. Collection of mail and news and posting is thereby automated. It is standard stuff and nothing to worry about. If you want to stop it remove those scripts and keep them somewhere safe - you will probably get bored with typing fetchmail and fecthnews eventually! Mar 27 22:38:01 debian /USR/SBIN/CRON[4209]: (mail) CMD ( if [ -x /usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi) I thought exim simply interacts with /var/spool/mail and did not attempt to create a connection. Maybe I'm wrong? No, you are right! This is just the automated posting mentioned above exim -q flushes out the queue of post waiting to be sent. Exim doesn't create a connection, it responds to the ip-up script when a connection is made. hth Glyn -- Debian Home http://www.debian.org Debian Planet http://www.debianplanet.org/ For the children http://www.debian.org/devel/debian-jr/ In a hurry??? http://qref.sourceforge.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie, configure exim/fetchmail w/ dialup; daemon trouble.
On Wed, Mar 27, 2002 at 23:33, Barry Mathieu wrote: I removed the /etc/fetchmailrc file, and issued /etc/init.d/fetchmail stop and then I logged in as root and issued dpkg-reconfigure fetchmail-common and I made sure a non system wide fetchmail setup was completed. Then I issued a, pon and after a few minutes my system connects (initiates ppp to my ISP) without me issuing any command; like a daemon. So my problem is still not fixed. I'm beginning to wonder about exim. Before the system attempts to connect, the following occurs in /var/log/syslog: Mar 27 22:38:01 debian /USR/SBIN/CRON[4209]: (mail) CMD ( if [ -x /usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi) I thought exim simply interacts with /var/spool/mail and did not attempt to create a connection. Maybe I'm wrong? Is your problem about an unintended dial on demand (DoD) or about unintended retrievel of your emails? If it is about DoD than it is for sure this exim bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96633repeatmerged=yes The current Debian woody is simply unusable for DoD with exim. I have spend days to find out more about this bug. Thr problem is that EVERY time exim is started, it initiates a DNS lookup of your local machine name. No matter how you configure it. This is at least true when zou do not have a full qualified domain name for your machine. If someone likes to look after it, I can provide all information I have gatherd about this problem so far. The exim upstream developer gave me some hints as well where the problem could be ... By, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Newbie, configure exim/fetchmail w/ dialup; daemon trouble.
On Tue, Mar 26, 2002 at 23:05, Barry Mathieu wrote: Fetchmail appears to running as a daemon and executes a query for mail every 300 seconds. To attempt to change this, I have a /etc/fetchmailrc with the line for the daemon commented out. I have altered the line for the daemon in /etc/default/fetchmail as follows: If you do not want fetchmail run as a daemon simply remove your /etc/fetchmailrc and the reular bootup scripts will notr start the daemon. Now, you can simply execute it from the command line. Bye, Steffen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Newbie, configure exim/fetchmail w/ dialup; daemon trouble.
Hello, With the help of this list, I have successfully upgraded from Potato to Woody! 20 hours on a dialup. However, I am having some troubles with mail handling; exim fetchmail With Potato, ppp ran as a daemon, fetchmail was configured, and I could issue, fetchmail at the command prompt to download my mail (over a dialup) from my ISP. I have been unsuccessful at such a configuration with Woody. Fetchmail appears to running as a daemon and executes a query for mail every 300 seconds. To attempt to change this, I have a /etc/fetchmailrc with the line for the daemon commented out. I have altered the line for the daemon in /etc/default/fetchmail as follows: OPTIONS=--daemon 0 --syslog Within /etc/init.d/fetchmail there is a line, OPTIONS=--daemon 300 --syslog However, the header of /etc/default/fetchmail indicates it is sourced by /etc/init.d/fetchmail so the presence of the immediately above line is inconsequential. I have also issued a 'dpkg-reconfigure fetchmail-common' and responded with a non-systemwide fetchmail configuration. Curiously, within /var/log/syslog is the following: Mar 26 17:53:01 debian /USR/SBIN/CRON[1649]: (mail) CMD ( if [ -x /usr/sbin/exim -a -f /etc/exim/exim.conf ]; then /usr/sbin/exim -q ; fi) Mar 26 17:53:01 debian pppd[1460]: Starting link I'm assuming exim is starting ppp because of a query from fetchmail. As you can probably tell, I'm just a bit confused trying to configure fetchmail. This computer is only typically used by me, so I really don't need a systemwide configuration. There is a .fetchmailrc file in my home from the Potato configuration. Thanks in advance for your suggestions, Barry Mathieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim on a dialup
Mario Vukelic wrote: On Fri, 2001-12-14 at 18:32, Tony Crawford wrote: Mario Vukelic wrote (on 13 Dec 2001 at 8:25): The ugly thing with the rewriting is that the above rule in the eximconfig-generated conf file rewrites always, regardless of destination, i.e., also for local mail that stays on your machine or network (Which means that replys to local mail want to go over the ISP account, which is often not what's wanted). If your /etc/aliases contains the reverse table of your /etc/email-addresses, the local replies will stay local. If that doesn't turn out to be true for you, hit me up for config details: it works for me. Sounds cool! Excuse me if I just ask for the config details right away. (and please feel free to ignore me if you don't want to dig it up; I surely don't want to put my workload on you). I admit that I don't want to spend another day on email config right now. Maybe the folks at http://www.exim.org should be told too. This would made a great addition to their FAQ. Their solution for the problem is, well, daunting, at least for a little home net. I'm a newbie. I just noticed this thread. I've missed any stuff that wasn't included in the above quote of the last message, so please excuse. I would like to use pure free software for email. In particular, Netscape seems to freeze my x-windows just as I am about to send an email. Not good. I hope this gets through. I use ppp and diald to connect to my ISP. What do I need to do to a new installation of Debian stable to get email? What should I use for reading email? Do I need something besides exim to get the email? e.g. fetchmail? I don't want anything fancy, just something that works while I learn about Debain. I have read enough of the documentation that got loaded during the install to know that I need help ... badly. Thanks, Paul Condon
Re: exim on a dialup
On Sat, Dec 15, 2001 at 11:16:16AM -0800, Paul E Condon wrote: ... | I use ppp and diald to connect to my ISP. | What do I need to do to a new installation of Debian stable to get email? | What should I use for reading email? I like mutt. It is a curses-based mailer (text only). If you want a gui, balsa is decent and simple. | Do I need something besides exim to get the email? e.g. fetchmail? Yes. exim does not _get_ mail, it only transfers (to other machines) and delivers mail. fetchmail will fetch (get) your mail, and hand it off to the local MDA (Mail Delivery Agent, exim) for delivery. | I don't want anything fancy, just something that works while I learn about | Debain. If you want to get a bit more fancy, you can use something like procmail to filter your mail. It can be used, for example, to put debian-user mail into a separate folder or to aviod spam. Some people have recommended 'mailfilter' (I think) as a program that can connect to a POP server and test the headers for spam so that you can delete spam before downloading it over your dial-up line. HTH, -D -- Better a little with righteousness than much gain with injustice. Proverbs 16:8
Re: exim on a dialup
On Sat, 2001-12-15 at 20:16, Paul E Condon wrote: I use ppp and diald to connect to my ISP. What do I need to do to a new installation of Debian stable to get email? What should I use for reading email? Do I need something besides exim to get the email? e.g. fetchmail? I would suggest to try both KDE and Gnome as Desktop environments if your machine is reasonably recent. Both have an email client (KDE's is kmail, Gnome's is the newly released Evolution). KDE is the more polished environment for now, but Evolution is the better mailer, IMHO. Both can retrieve and send mail on their own, no need for other tools if your needs are not special. I don't know for kmail, but Evo can retrieve from multiple sources and send from different identities (i.e., you can configure several email adresses, and choose which one to send from - then the mail server that goes with it is used to send). In addition you should install exim and configure it to send local mail only. Also install logcheck. Then in Evo set up an additional mail retrieval from local spool. This way your system will send you the most important system logs every hour via the local mail spool. That said, if you're more interested in text clients, try mutt. I think mutt can retrieve by itself but needs exim to send, but I'm not sure. Exim configuration to forward non-local mail to your ISP is not that hard with eximconfig. You can also use fetchmail to retrieve mail (and fetchmailconf to configure it) but it's decidedly more complicated than Evo. You need special lines in /etc/apt/sources.list to get recent Gnome or KDE for potato. KDE is 2.2.1 or 2.2.2 now, Gnome 1.4.1. Search the list archive at http://lists.debian.org/ or look at http://www.debianhelp.org/ or http://www.debianplanet.org/ for the sources.list lines. You can also use Ximian's Gnome (http://www.ximian.com/) for potato. Many will advise against it for debian (because they package slightly different, maybe inferior to debian; in any case, don't mix Ximian and debian packages for Gnome, they don't work together well), but I found it a very nicely polished version of Gnome for potato. Have fun, M.
Re: exim on a dialup
Mario Vukelic wrote (on 13 Dec 2001 at 8:25): The ugly thing with the rewriting is that the above rule in the eximconfig-generated conf file rewrites always, regardless of destination, i.e., also for local mail that stays on your machine or network (Which means that replys to local mail want to go over the ISP account, which is often not what's wanted). If your /etc/aliases contains the reverse table of your /etc/email-addresses, the local replies will stay local. If that doesn't turn out to be true for you, hit me up for config details: it works for me. T. -- -- Tony Crawford -- [EMAIL PROTECTED] -- +49-3341-30 99 99 --
Re: exim on a dialup
On Fri, 2001-12-14 at 18:32, Tony Crawford wrote: Mario Vukelic wrote (on 13 Dec 2001 at 8:25): The ugly thing with the rewriting is that the above rule in the eximconfig-generated conf file rewrites always, regardless of destination, i.e., also for local mail that stays on your machine or network (Which means that replys to local mail want to go over the ISP account, which is often not what's wanted). If your /etc/aliases contains the reverse table of your /etc/email-addresses, the local replies will stay local. If that doesn't turn out to be true for you, hit me up for config details: it works for me. Sounds cool! Excuse me if I just ask for the config details right away. (and please feel free to ignore me if you don't want to dig it up; I surely don't want to put my workload on you). I admit that I don't want to spend another day on email config right now. Maybe the folks at http://www.exim.org should be told too. This would made a great addition to their FAQ. Their solution for the problem is, well, daunting, at least for a little home net. Thanks, M.
exim on a dialup
i've just managed to get exim set up on a dialup connection. localhost gets mentioned in the headers. does that matter a damn?
Re: exim on a dialup
On Thu, 2001-12-13 at 08:04, ben wrote:
i've just managed to get exim set up on a dialup connection. localhost gets
mentioned in the headers. does that matter a damn?
I once got angry mail from a guy from this list whose sendmail rewrote
the localhost part in my headers with the machine name of his sendmail
host. So I suggest to set qualify_domain = yourmachine.yourhomedomain in
/etc/exim/exim.conf, where yourhomedomain is a not-official domain name
like home or localnet. Also adapt the rewrite rule in the REWRITE
section:
[EMAIL PROTECTED] ${lookup{$1}lsearch{/etc/email-addresses}\
{$value}fail} frFs
This will then rewrite the mail headers of accounts set in
/etc/email-addresses to the headers of the accounts at the ISP.
The ugly thing with the rewriting is that the above rule in the
eximconfig-generated conf file rewrites always, regardless of
destination, i.e., also for local mail that stays on your machine or
network (Which means that replys to local mail want to go over the ISP
account, which is often not what's wanted). There is a exim FAQ at
http://www.exim.org/FAQ.html#SEC241 about this. I tried to figure it out
yesterday, with no success so far. Oh, the headaches.
--
I did not vote for the Austrian government
Re: exim on a dialup
On Wednesday 12 December 2001 11:25 pm, Mario Vukelic wrote:
On Thu, 2001-12-13 at 08:04, ben wrote:
i've just managed to get exim set up on a dialup connection. localhost
gets mentioned in the headers. does that matter a damn?
I once got angry mail from a guy from this list whose sendmail rewrote
the localhost part in my headers with the machine name of his sendmail
host. So I suggest to set qualify_domain = yourmachine.yourhomedomain in
/etc/exim/exim.conf, where yourhomedomain is a not-official domain name
like home or localnet. Also adapt the rewrite rule in the REWRITE
section:
[EMAIL PROTECTED] ${lookup{$1}lsearch{/etc/email-addresses}\
{$value}fail} frFs
This will then rewrite the mail headers of accounts set in
/etc/email-addresses to the headers of the accounts at the ISP.
The ugly thing with the rewriting is that the above rule in the
eximconfig-generated conf file rewrites always, regardless of
destination, i.e., also for local mail that stays on your machine or
network (Which means that replys to local mail want to go over the ISP
account, which is often not what's wanted). There is a exim FAQ at
http://www.exim.org/FAQ.html#SEC241 about this. I tried to figure it out
yesterday, with no success so far. Oh, the headaches.
thanks for the pointers. i'm assuming that i'll also need to configure
/etc/hosts to read an alias equivalent to yourmachine.yourhomedomain. is that
correct?
Re: exim on a dialup
On Thu, 2001-12-13 at 08:55, ben wrote: thanks for the pointers. i'm assuming that i'll also need to configure /etc/hosts to read an alias equivalent to yourmachine.yourhomedomain. is that correct? I don't think it's really related and needed, but it surely makes maintenance easier if your local network is known under the same name for all programs. Kind regards, M. -- I did not vote for the Austrian government
Re: exim on a dialup
On Wednesday 12 December 2001 11:25 pm, Mario Vukelic wrote:
On Thu, 2001-12-13 at 08:04, ben wrote:
i've just managed to get exim set up on a dialup connection. localhost
gets mentioned in the headers. does that matter a damn?
I once got angry mail from a guy from this list whose sendmail rewrote
the localhost part in my headers with the machine name of his sendmail
host. So I suggest to set qualify_domain = yourmachine.yourhomedomain in
/etc/exim/exim.conf, where yourhomedomain is a not-official domain name
like home or localnet. Also adapt the rewrite rule in the REWRITE
section:
[EMAIL PROTECTED] ${lookup{$1}lsearch{/etc/email-addresses}\
{$value}fail} frFs
This will then rewrite the mail headers of accounts set in
/etc/email-addresses to the headers of the accounts at the ISP.
i'm still getting this:
Received: from ben by localhost with local (Exim 3.33 #1 (Debian))
what's the syntax for /etc/email-addresses? i may have screwed that up.
Re: exim on a dialup
On Thu, 2001-12-13 at 09:30, ben wrote:
i'm still getting this:
Received: from ben by localhost with local (Exim 3.33 #1 (Debian))
Did you restart exim ('/etc/init.d/exim restart' as root)?
what's the syntax for /etc/email-addresses? i may have screwed that up.
Easy. I'm mario on my machine and [EMAIL PROTECTED] at my ISP. So
I put into my /etc/email-aliases:
mario: [EMAIL PROTECTED]
It should work. But to be sure that I don't lead you onto a wrong track:
do my headers actually look ok?. For otherwise I'm an idiot and you
shouldn't listen to me. (Try one of my previous messages. I'm at the
moment playing around with IMAP and this current mail is sent from my
IMAP account on my local machine. I'm not sure if I'm screwing something
up again :)
Cheers, M.
Re: exim on a dialup
On Thursday 13 December 2001 12:53 am, mario wrote:
On Thu, 2001-12-13 at 09:30, ben wrote:
i'm still getting this:
Received: from ben by localhost with local (Exim 3.33 #1 (Debian))
Did you restart exim ('/etc/init.d/exim restart' as root)?
what's the syntax for /etc/email-addresses? i may have screwed that up.
Easy. I'm mario on my machine and [EMAIL PROTECTED] at my ISP. So
I put into my /etc/email-aliases:
mario: [EMAIL PROTECTED]
It should work. But to be sure that I don't lead you onto a wrong track:
do my headers actually look ok?.
yeah, your headers look reasonable--speaking from a position of obvious
inexpertise. what i looked at were the references, which make a lot more
sense than mine, all of which refer to message id's from localhost, whereas
yours eventually refer back to chello.at. i guess that--message id's anchored
at localhost--was the cause of the angry gripe you got from the sendmail
user, although i would imagine that some manner of safeguard exists within
his responsibility to prevent that. otherwise, internet havoc would easily
prevail.
essentially, i've followed all the rules i've found, including those you've
passed on. nothing you said caused any negative effect, so i assume that they
are relevant. i've read that some of exim's syntax rules occasionally cancel
each other, so i'm thinking that something i've done previously is having
that effect. back to the FM, i guess. nothing like a good read before bedtime.
thanks for your help. if i get it sorted, i'll get back to you.
Re: exim on a dialup
On Thu, 2001-12-13 at 10:27, ben wrote: thanks for your help. if i get it sorted, i'll get back to you. Good luck. Essentially, I think you're set when you take eximconfigs option 2 and accept more or less the defaults plus proper email-aliases. Then you have to live with rewriting of internal addresses, however. OHMYGOD!!! No that I say this I see that I /am/ an idiot. Forget my headers, please. Some days ago I actually configured my mailer (evolution) to send using my ISP's smarthost when sending from my ISP-address and to use exim without rewriting when sending from my home address (because of the rewriting problem). Of course my headers look right. Kind regards, M. -- I did not vote for the Austrian government
Re: exim on a dialup
On Thursday 13 December 2001 01:57 am, Mario Vukelic wrote: Good luck. Essentially, I think you're set when you take eximconfigs option 2 and accept more or less the defaults plus proper email-aliases. Then you have to live with rewriting of internal addresses, however. OHMYGOD!!! No that I say this I see that I /am/ an idiot. Forget my headers, please. Some days ago I actually configured my mailer (evolution) to send using my ISP's smarthost when sending from my ISP-address and to use exim without rewriting when sending from my home address (because of the rewriting problem). Of course my headers look right. Kind regards, M. i got it. you've got to comment out the local_domains option in exim.conf. then exim reads /etc/hostname and bingo!
Re: exim on a dialup
On Thu, Dec 13, 2001 at 12:30:33AM -0800, ben wrote: | i'm still getting this: | | Received: from ben by localhost with local (Exim 3.33 #1 (Debian)) This is normal and expected. The Received: headers are there so that you can track down problems with mail transfer. Each MTA that sees the message adds itself to the top of the Received: list. What exim is saying is that it saw the message, and the envelope sender was ben on the localhost machine. That is, you (as a user) asked exim (on your machine) to transfer the message for you. -D -- ...the word HACK is used as a verb to indicate a massive amount of nerd-like effort. -Harley Hahn, A Student's Guide to Unix
Re: exim on a dialup
On Thursday 13 December 2001 07:03 am, dman wrote: On Thu, Dec 13, 2001 at 12:30:33AM -0800, ben wrote: | i'm still getting this: | | Received: from ben by localhost with local (Exim 3.33 #1 (Debian)) This is normal and expected. The Received: headers are there so that you can track down problems with mail transfer. Each MTA that sees the message adds itself to the top of the Received: list. What exim is saying is that it saw the message, and the envelope sender was ben on the localhost machine. That is, you (as a user) asked exim (on your machine) to transfer the message for you. -D thanks for the response, but that wasn't so much the issue as the fact that exim wasn't reading the hostname i had set in a rewrite rule. this was resolved by commenting out the local_domains option.
Exim on a dialup
I have just installed and configured exim on my box. Both incoming (via fetchmail) and outgoing mail work, but at the moment exim initiates a connection to my ISP as soon as it gets outgoing mail. I know there is a way to stop this but I couldn't see the details in the man page. Could someone point me in the right direction, please, maybe with a hint as to the keyword or phrase I should be looking for?
EXIM settings for dialup.
Not sure if I should post here (but I'm running exim on a debian :)
So, I have a Debian unstable running exim 3.03, connecting to the
Internet through PPP without fixed IP. I have configured exim to
use smarthost(*) to send mail, performing address rewrite like
this:
[EMAIL PROTECTED] [EMAIL PROTECTED] Ffr
And can send mail just fine (or else you can't see this)
However there is something stupid when I send mail to myself:
Address rewrite is performed even for local deliveries.
How can I disable this?
I guess I should disable address rewrite for everything
inside the directors. But... how?
Or am I plain wrong?
Should I disable address rewrites for everything, and
enable them only for the routers instead?
*) In fact I have more than one router. The smarthost router
runs only if the sender is me.
I does this through
condition = ${if eq [EMAIL PROTECTED] {yes}fail}
It works fine but is less then clean. Are there better configuration
options for this? From what I read in the spec this is the best?
( And that I am subscribed to the digest instead. Do I get
every single post, including this one and follow-ups for it? )
Re: EXIM settings for dialup.
Ronald Tin wrote:
Not sure if I should post here (but I'm running exim on a debian :)
So, I have a Debian unstable running exim 3.03, connecting to the
Internet through PPP without fixed IP. I have configured exim to
use smarthost(*) to send mail, performing address rewrite like
this:
[EMAIL PROTECTED] [EMAIL PROTECTED] Ffr
And can send mail just fine (or else you can't see this)
However there is something stupid when I send mail to myself:
Address rewrite is performed even for local deliveries.
How can I disable this?
I guess I should disable address rewrite for everything
inside the directors. But... how?
Or am I plain wrong?
Should I disable address rewrites for everything, and
enable them only for the routers instead?
*) In fact I have more than one router. The smarthost router
runs only if the sender is me.
I does this through
condition = ${if eq [EMAIL PROTECTED] {yes}fail}
It works fine but is less then clean. Are there better configuration
options for this? From what I read in the spec this is the best?
( And that I am subscribed to the digest instead. Do I get
every single post, including this one and follow-ups for it? )
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
I had to do this myself, I got this info. from Oskar Liljeblad ([EMAIL
PROTECTED])
(in /etc/exim.conf):
# Main Configuration Settings
qualify_domain = alumni.ust.hk
hem.passagen.se is my email ISP, and without this
they wouldn't let me relay mail through their server.
qualify_recipient = localhost
This is necessary so you can do mail vamp
and receive the mail directly without going through the ISP.
The new mail will have To: [EMAIL PROTECTED] but still
From: Ronald Tin alumni.ust.hk where the latter was
rewritten by the local MTA.
local_domains = localhost
If you use eximconfig to generate a smarthost setup, it is possible
that your smarthost will be included here. But it shouldn't.
Sorry for the plagiraism, Oskar, but you knew how to fix it
Jonathan
Re: EXIM settings for dialup.
Sorry that I didn't make it clear.. :(
I don't have much problems sending the mail through alumni.ust.hk.
And no problems for sending local mail too.
(There was quite a number of problems, but were solved before
I decided to post here :)
The problem is that local mails suffers from the address rewrite..
Just a bit ugly :(
And yes, I find that I can see my mail and replies to it from
the digest. Thanks for forwarding me a copy, Jonathan)
On Sat, Oct 23, 1999 at 03:11:59PM -, [EMAIL PROTECTED] wrote:
Date: Sat, 23 Oct 1999 10:43:21 +
From: Jonathan Heaney [EMAIL PROTECTED]
To: Ronald Tin [EMAIL PROTECTED]
CC: debian-user@lists.debian.org, [EMAIL PROTECTED]
Subject: Re: EXIM settings for dialup.
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Ronald Tin wrote:
Not sure if I should post here (but I'm running exim on a debian :)
So, I have a Debian unstable running exim 3.03, connecting to the
Internet through PPP without fixed IP. I have configured exim to
use smarthost(*) to send mail, performing address rewrite like
this:
[EMAIL PROTECTED] [EMAIL PROTECTED] Ffr
And can send mail just fine (or else you can't see this)
However there is something stupid when I send mail to myself:
Address rewrite is performed even for local deliveries.
How can I disable this?
I guess I should disable address rewrite for everything
inside the directors. But... how?
Or am I plain wrong?
Should I disable address rewrites for everything, and
enable them only for the routers instead?
*) In fact I have more than one router. The smarthost router
runs only if the sender is me.
I does this through
condition = ${if eq [EMAIL PROTECTED] {yes}fail}
It works fine but is less then clean. Are there better configuration
options for this? From what I read in the spec this is the best?
( And that I am subscribed to the digest instead. Do I get
every single post, including this one and follow-ups for it? )
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
I had to do this myself, I got this info. from Oskar Liljeblad ([EMAIL
PROTECTED])
(in /etc/exim.conf):
# Main Configuration Settings
qualify_domain = alumni.ust.hk
hem.passagen.se is my email ISP, and without this
they wouldn't let me relay mail through their server.
qualify_recipient = localhost
This is necessary so you can do mail vamp
and receive the mail directly without going through the ISP.
The new mail will have To: [EMAIL PROTECTED] but still
From: Ronald Tin alumni.ust.hk where the latter was
rewritten by the local MTA.
local_domains = localhost
If you use eximconfig to generate a smarthost setup, it is possible
that your smarthost will be included here. But it shouldn't.
Sorry for the plagiraism, Oskar, but you knew how to fix it
Jonathan
Exim configuration for dialup users (was Re: Exim as default mailer)
On Wed, Nov 11, 1998 at 11:38:16AM +0100, Paul Slootman wrote: In article [EMAIL PROTECTED] you write: 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? 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: 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!). Exim works fine for home users, but there are five areas that are tricky to configure: ** local_domans should have ALL the names your local network is known by; e.g., local_domains = townhouse:localhost. ** don't use the visible_name stuff or you'll find that messages to people at your ISP get delivered locally. ** I have all the queue options commended out (queue_smtp, queue_remote, queue_only, queue_run_in_order). Mail delivers immediately, but if it can't (e.g., network is down) it just gets queued, no problem. I run the queue manually when I want to, but you could also do it within ip-up or via cron. If you have dial-on-demand and don't want the link going up for email, edit the diald config file to ignore SMTP (and you'd also need to specify your smarthost via IP#, so it doesn't cause a DNS lookup, which would activate diald). ** You'll need to use your ISP's smarthost, because some sites will reject your mail if you try to deliver it directly, because your local domain name (that exim knows about) is different from the name associated with the (dynamic) IP you're currently connected on, so exim gets the HELO argument wrong and I don't know how to fix it. # In the ROUTERS section of /etc/exim.conf smarthost: driver = domainlist transport = remote_smtp route_list = * smtp.my_isp.com bydns_a end ** Rewriting the From: address takes forever to get right. I'm currently using: [EMAIL PROTECTED] [EMAIL PROTECTED] Ff If this is absent, you'll end up being From: [EMAIL PROTECTED], which is not accessible from Internet. Other misconfigrations cause [EMAIL PROTECTED] (somebody else, or a nonexistent user) or [EMAIL PROTECTED] (which your ISP will be real happy about). However, at least it's easier to get this right under Exim than any other MTA. ** It's difficult to funnel multiple local users through one ISP pop account. I've never gotten this to work. Some people use the comment part of the to-address to determine who it's going to. Others use the -suffix method, where mail to [EMAIL PROTECTED] goes through your .forward filter based on -suffix. But I think that requires Qmail and cooperation from your ISP. As another person stated, the problem is really SMTP's fault --- it's inadequate for dialup users with dynamic IPs. But UUCP is frequently not an option because most ISPs don't know what it is and those that do charge extra for it. I've sometimes thought, wouldn't it be better to use Qpopper's upload feature? That way, the authentication depends on knowing your username/ password, which is much more reliable than the domainname/ reverse domainname checks SMTP does. It would be easy enough to write an Exim transport which contacts the remote popserver. Unfortunately, it means the ISP would have to change to Qpopper, and they'd probably say, But our current system works fine for our Windows users. And we don't support Linux anyway. -- -Mike Orr, [EMAIL PROTECTED]
