Re: exim4: how to handle other addresses on my ISP?
* Chris Metzler [EMAIL PROTECTED] [061115 00:39]: Hi, I'm having trouble configuring exim4. My situation -- that is, what I want exim4 to do -- *can't* be that unusual; so I'm sure I'm missing something fairly obvious. But I've played around with exim4's configuration via dpkg-reconfigure exim4-config a zillion times and cannot get there. I've Googled and skimmed the exim4 FAQ without much success yet -- lots of stuff, but nothing that looks obviously like the solution here. Next up is digging into the exim4 specification in detail. I really don't want to that if I don't have to -- I mean, if that's what I have to do to solve this problem, I will; but I'm hoping that I'm just missing something with dpkg-reconfigure exim4-config and this can be solved more easily than skipping sleep, since right now I'm effectively working 15 hours a day and sleeptime is pretty much the only free time I have anymore. Here's my situation and what I want: 1. I have a machine with no domain of its own, in the sense that I haven't registered a domain or anything like that. My ISP is speakeasy.net. Outgoing email goes to a smarthost. Incoming email is pulled in by fetchmail and handed off to exim4. 2. Various users on this machine have email adresses registered with the ISP of the form [EMAIL PROTECTED] When one of my local users sends an outgoing email, exim4 appends @speakeasy.net to the local username. 3. Likewise, if you were to send email to [EMAIL PROTECTED], fetchmail on my machine should eventually grab it and pass it to exim4 here. This apparently means that when I've configured exim4 using dpkg- reconfigure, I need to tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination. If I don't do that, then when exim4 receives from fetchmail an email for [EMAIL PROTECTED], exim4 immediately passes that email back on to the ISP's smarthost (because we aren't a final destination for @speakeasy.net), and around and around we go. 4. But if I do that -- if I tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination, then that means I'm unable to send email to other users of this ISP that have nothing to do with my machine (since they all have addresses like [EMAIL PROTECTED]). Right now, if I send an email to [EMAIL PROTECTED], exim4 notes that it's been told that *I'm* the end destination for email to the domain speakeasy.net, and cheerily reminds me that there's no one on this machine by that username. Is there a simple solution to this? Or is it time for me to roll my sleeves up and learn exim4 in more detail? If someone can clarify what I'm doing wrong through dpkg-reconfigure, or point me at some helpful documentation, I'd be very grateful. I am no expert, but I had a similar problem. And I shall be grateful for correction from those who are experts. I discovered that I was making difficult a problem which is simple. The typical home or small business user needs only a small fraction of the capabilities provided by a mail transfer agent (MTA) such as Exim4. But little, if anything, is to be gained by switching to a less-capable alternative. You simply need to understand that, in the context of the LAN of a home, domitory, or small business, Exim4 need do nothing more than serve as a mechanism for handing off outgoing mail from the machines in the LAN to the smarthost of your choice. If the smarthost is, for example, the mail server of the outfit which hosts your commercial web site, it may be necessary to have Exim rewrite headers so that unqualified addresses are replaced with a valid address, and it may be necessary to configure Exim to authenticate with that server. But if you are using as smarthost the SMTP server of your ISP, rewriting and authentication may not be necessary. When filling in the blanks in the Exim4 configuration dialogue of the Debian installer, don't worry as to whether the headers accurately reflect the particular sender. All you need to do is get Exim configured so that the smarthost accepts your outgoing mail. The selection of the proper From: header for outgoing mail is the duty of your mail user agent (MUA); the MUA may be Mutt, Gnus, Balsa, Sylpheed, Thunderbird, etc. Read the documentation concerning multiple send 'personas' or 'personalities'. The sorting of incoming mail for multiple users or multiple personalities is the function of a mail delivery agent (MDA) such as maildrop. Exim has no role to play with respect to incoming mail which originates outside the LAN. RLH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim4: how to handle other addresses on my ISP?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Metzler wrote: Here's my situation and what I want: 1. I have a machine with no domain of its own, in the sense that I haven't registered a domain or anything like that. My ISP is speakeasy.net. Outgoing email goes to a smarthost. Incoming email is pulled in by fetchmail and handed off to exim4. 2. Various users on this machine have email adresses registered with the ISP of the form [EMAIL PROTECTED] When one of my local users sends an outgoing email, exim4 appends @speakeasy.net to the local username. 3. Likewise, if you were to send email to [EMAIL PROTECTED], fetchmail on my machine should eventually grab it and pass it to exim4 here. This apparently means that when I've configured exim4 using dpkg- reconfigure, I need to tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination. If I don't do that, then when exim4 receives from fetchmail an email for [EMAIL PROTECTED], exim4 immediately passes that email back on to the ISP's smarthost (because we aren't a final destination for @speakeasy.net), and around and around we go. 4. But if I do that -- if I tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination, then that means I'm unable to send email to other users of this ISP that have nothing to do with my machine (since they all have addresses like [EMAIL PROTECTED]). Right now, if I send an email to [EMAIL PROTECTED], exim4 notes that it's been told that *I'm* the end destination for email to the domain speakeasy.net, and cheerily reminds me that there's no one on this machine by that username. Is there a simple solution to this? Or is it time for me to roll my sleeves up and learn exim4 in more detail? If someone can clarify what I'm doing wrong through dpkg-reconfigure, or point me at some helpful documentation, I'd be very grateful. Just send your mail to [EMAIL PROTECTED] and it will be delivered locally instead of sent to the smarthost. If you specify localhost, nothing will be added to your address. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFFWtLSu4tRirKTPYwRAuVsAJ4qN2KJJoaARCqpmmxpy5493wytggCXemwf DmFENkyzLixfSMbH1vDPXA== =Dflq -END PGP SIGNATURE- begin:vcard fn:W Paul Mills n:Mills;W Paul org:The Mills Chaos In The USA adr:;;;Topeka;Kansas;;USA email;internet:[EMAIL PROTECTED] title:Electronics Technician note:Hint: remove -NOT x-mozilla-html:FALSE url:http://Mills-USA.com version:2.1 end:vcard
Re: exim4: how to handle other addresses on my ISP?
On (15/11/06 01:39), Chris Metzler wrote: snip 1. I have a machine with no domain of its own, in the sense that I haven't registered a domain or anything like that. My ISP is speakeasy.net. Outgoing email goes to a smarthost. Incoming email is pulled in by fetchmail and handed off to exim4. 2. Various users on this machine have email adresses registered with the ISP of the form [EMAIL PROTECTED] When one of my local users sends an outgoing email, exim4 appends @speakeasy.net to the local username. 3. Likewise, if you were to send email to [EMAIL PROTECTED], fetchmail on my machine should eventually grab it and pass it to exim4 here. This apparently means that when I've configured exim4 using dpkg- reconfigure, I need to tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination. If I don't do that, then when exim4 receives from fetchmail an email for [EMAIL PROTECTED], exim4 immediately passes that email back on to the ISP's smarthost (because we aren't a final destination for @speakeasy.net), and around and around we go. 4. But if I do that -- if I tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination, then that means I'm unable to send email to other users of this ISP that have nothing to do with my machine (since they all have addresses like [EMAIL PROTECTED]). Right now, if I send an email to [EMAIL PROTECTED], exim4 notes that it's been told that *I'm* the end destination for email to the domain speakeasy.net, and cheerily reminds me that there's no one on this machine by that username. I remember encountering this problem and puzzling over it for some time. I seem to recall it was something to do with the local part corresponding to users. If x is a local user [EMAIL PROTECTED] mails are delivered locally; if not they go out to the smarthost. I've set up a number of machines since then and they just seem to work. What is the output of: $cat /etc/exim4/update-exim4.conf.conf it may give a clue as to where the problem lies. FWIW I didn't have to rewite headers or the like. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim4: how to handle other addresses on my ISP?
On Wed, Nov 15, 2006 at 01:39:21AM -0500, Chris Metzler wrote: Hi, I'm having trouble configuring exim4. My situation -- that is, what I want exim4 to do -- *can't* be that unusual; so I'm sure I'm missing something fairly obvious. But I've played around with exim4's configuration via dpkg-reconfigure exim4-config a zillion times and cannot get there. I've Googled and skimmed the exim4 FAQ without much success yet -- lots of stuff, but nothing that looks obviously like the solution here. Next up is digging into the exim4 specification in detail. I really don't want to that if I don't have to -- I mean, if that's what I have to do to solve this problem, I will; but I'm hoping that I'm just missing something with dpkg-reconfigure exim4-config and this can be solved more easily than skipping sleep, since right now I'm effectively working 15 hours a day and sleeptime is pretty much the only free time I have anymore. Here's my situation and what I want: 1. I have a machine with no domain of its own, in the sense that I haven't registered a domain or anything like that. My ISP is speakeasy.net. Outgoing email goes to a smarthost. Incoming email is pulled in by fetchmail and handed off to exim4. 2. Various users on this machine have email adresses registered with the ISP of the form [EMAIL PROTECTED] When one of my local users sends an outgoing email, exim4 appends @speakeasy.net to the local username. 3. Likewise, if you were to send email to [EMAIL PROTECTED], fetchmail on my machine should eventually grab it and pass it to exim4 here. This apparently means that when I've configured exim4 using dpkg- reconfigure, I need to tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination. If I don't do that, then when exim4 receives from fetchmail an email for [EMAIL PROTECTED], exim4 immediately passes that email back on to the ISP's smarthost (because we aren't a final destination for @speakeasy.net), and around and around we go. I think the problem may lie in your fetchmail configuration. Have you got something like: user [EMAIL PROTECTED] password abcdef is jim here ^^^ in .fetchmailrc? 4. But if I do that -- if I tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination, then that means I'm unable to send email to other users of this ISP that have nothing to do with my machine (since they all have addresses like [EMAIL PROTECTED]). Right now, if I send an email to [EMAIL PROTECTED], exim4 notes that it's been told that *I'm* the end destination for email to the domain speakeasy.net, and cheerily reminds me that there's no one on this machine by that username. Is there a simple solution to this? Or is it time for me to roll my sleeves up and learn exim4 in more detail? If someone can clarify what I'm doing wrong through dpkg-reconfigure, or point me at some helpful documentation, I'd be very grateful. Thanks for , -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear -- David Jardine Running Debian GNU/Linux and loving every minute of it. -L. von Sacher-M.(1835-1895) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim4: how to handle other addresses on my ISP?
On Wed, Nov 15, 2006 at 01:21:20AM -0600, Russell L. Harris wrote: The selection of the proper From: header for outgoing mail is the duty of your mail user agent (MUA); the MUA may be Mutt, Gnus, Balsa, Sylpheed, Thunderbird, etc. Read the documentation concerning multiple send 'personas' or 'personalities'. I saw your post on the mutt users list where it was advised to set the envelope_from in the MUA so the ISP wouldn't reject the mail. I think it should be the MTA's job. Imagine, everytime a user changed their MUA they would have to configure this everytime whereas if it was set in the MTA then it would only have to be done *once* by the system administrator. I was running Exim and it worked out of the box once you had answered the debconf questions correctly *and* entered the users in the /etc/email-addresses (I'm not sure if that is the correct name because I am now trying postfix, which incidentally gained me about 1.1M of disk space, and wiped all traces of exim off my hard disk.) file. It is self documenting. When I installed postfix guess what? Yep, my mail was rejected from my ISP because it was still showing [EMAIL PROTECTED] instead of [EMAIL PROTECTED] After a bit of reading of the copious documentation, I found in ADDRESS_REWRITING_README.gz what I was looking for and so I cd into /etc/postfix, created a file called generic with the following line: [EMAIL PROTECTED] [EMAIL PROTECTED] and also added: smtp_generic_maps = hash:/etc/postfix/generic to /etc/postfix/main.cf as per instructions. Restarted postfix. Grumble grumble, postconf -n still showed smtp_generic_maps = i.e. nothing. Back to the documentation ... ahh ... in another completely separate document I found the postmap command. YES!!, so I issued a postmap /etc/postfix/generic and voila a generic.db file was created in the /etc/postfix directory. It was about this time I saw your post in mutt-users and the replys about setting envelope_from and thought 'strange, why would you set the same thing in two places, this aint Windows'. About this time I tested my email again, NO!!!, it was rejected! I thought lucky I saw your post to mutt-users and put: set use_envelope_from=yes set envelope_from_address=[EMAIL PROTECTED] into my .muttrc and tested again and sure enough it worked. BUT I still wasn't satisfied, it felt like a hack for reasons I explained above. So I had a closer look at the rejected mail and it wasn't [EMAIL PROTECTED] it was seeing but, [EMAIL PROTECTED] AHHH!!! why didn't I see that, duh. So to cut a long story short :-) I deleted the /etc/postfix/generic.db file, put [EMAIL PROTECTED] [EMAIL PROTECTED] into /etc/postfix/generic ran postmap /etc/postfix/generic then ran postfix reload (according to the documentation a postfix stop then postfix start does NOT reload the configuration. Commented out set use_envelope_from=yes and set envelope_from_address=[EMAIL PROTECTED] from my .muttrc and gave it another test. YES IT WORKED!!! P.S. I have alternates [EMAIL PROTECTED] in my .muttrc but Its been in there since exim3. Also to get all the postfix documentation you have to install postfix-doc which installs the documentation under /usr/share/doc/postfix/ NOT /usr/share/doc/postfix-doc/. The sorting of incoming mail for multiple users or multiple personalities is the function of a mail delivery agent (MDA) such as maildrop. Exim has no role to play with respect to incoming mail which originates outside the LAN. Agreed. -- Chris. == ... the official version cannot be abandoned because the implication of rejecting it is far too disturbing: that we are subject to a government conspiracy of `X-Files' proportions and insidiousness. Letter to the LA Times Magazine, September 18, 2005. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim4: how to handle other addresses on my ISP?
On Wed, Nov 15, 2006 at 01:39:21AM -0500, Chris Metzler wrote: Here's my situation and what I want: 1. I have a machine with no domain of its own, in the sense that I haven't registered a domain or anything like that. My ISP is speakeasy.net. Outgoing email goes to a smarthost. Incoming email is pulled in by fetchmail and handed off to exim4. 2. Various users on this machine have email adresses registered with the ISP of the form [EMAIL PROTECTED] When one of my local users sends an outgoing email, exim4 appends @speakeasy.net to the local username. 3. Likewise, if you were to send email to [EMAIL PROTECTED], fetchmail on my machine should eventually grab it and pass it to exim4 here. This apparently means that when I've configured exim4 using dpkg- reconfigure, I need to tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination. If I don't do that, then when exim4 receives from fetchmail an email for [EMAIL PROTECTED], exim4 immediately passes that email back on to the ISP's smarthost (because we aren't a final destination for @speakeasy.net), and around and around we go. Local delivery should be enabled. The only ISP entry should be the smtp server at speakeasy.net -- probably smtp.speakeasy.net That is [EMAIL PROTECTED] should be able to send to [EMAIL PROTECTED] without being connected to your ISP. 4. But if I do that -- if I tell exim4 that speakeasy.net should be added to the list of domains for which this machine should consider itself the final destination, then that means I'm unable to send email to other Is there a simple solution to this? Or is it time for me to roll my sleeves up and learn exim4 in more detail? If someone can clarify what I'm doing wrong through dpkg-reconfigure, or point me at some helpful documentation, I'd be very grateful. You *also* need to add any users that have accounts at your ISP to the /etc/email-addresses file. Could someone confirm that is the correct name as I no longer run exim. e.g. [EMAIL PROTECTED] [EMAIL PROTECTED] and it should just work. Please post back if that doesn't work. -- Chris. == ... the official version cannot be abandoned because the implication of rejecting it is far too disturbing: that we are subject to a government conspiracy of `X-Files' proportions and insidiousness. Letter to the LA Times Magazine, September 18, 2005. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
