Re: Exim config problems
apologies for further questions on the same topic. I am using Mutt with
exim and fetchmail with a dial-up account with an isp - panix.com. i
originally configured with the "interactive" exim configuration utility
and for a while, everything worked fine. when i installed gnome, it caused
a few problems...when i, unintentionally, invoked Tkmail, more config
problems developed. specifically, i can no longer sendmail. I have been
trying to modify the /etc/exim.conf file manually, following the advices
offered on the list, but i have not been able to remedy the problem, so
one more time, a very similar question. I have modified the settings per
previous advice:
qualify_domains = panix.com
qualify_recipient = localhost
local_domains = localhost
with these settings, i am still unable to send mail, this is via telnet to
isp.
my computer does not have a fully qualified domain name, my user name on
my computer is pe, the user name at the isp is mickle, and the e-mail
address is mickle@panix.com. my computer or "system" name is PIENO. if,
using mutt, i send e-mail to myself <mickle@panix.com>, i get a delivery
failed message addressed to my local address pe@PIENO indicating that the
address mickle@panix.com failed after a long failure period.
apologies again...any thoughts,
Peter
On Tue, 8 Jun 1999, Marc Mongeon wrote:
> These three settings are important in exim.conf:
>
> qualify_domain = ihug.co.nz
> qualify_recipient = localhost
> local_domains = localhost
>
> Assuming your computer does not have a fully-qualified domain name (most dial-up users don't).
> If you do have a FQDN, use that instead of localhost. So, people who want to send mail to you
> will send it to you@ihug.co.nz. You will use fetchmail to relay the mail from your POP account
> to the local machine (tell fetchmail that you want to send it to you@localhost). You will send
> mail to local users by addressing it to user@localhost or just user, and the mail will be routed
> locally. You will send mail to non-local users by addressing it to user@fully.qualified.name, and
> the recipient will see you@ihug.co.nz in the "From:" field. Does that sound like what you wanted?
>
> Marc
>
> ----------
> Marc Mongeon <mongeon@bankoe.com>
> Unix Specialist
> Ban-Koe Systems
> 9100 W Bloomington Fwy
> Bloomington, MN 55431-2200
> (612)888-0123, x417 | FAX: (612)888-3344
> ----------
> "It's such a fine line between clever and stupid."
> -- David St. Hubbins and Nigel Tufnel of "Spinal Tap"
>
>
> >>> Matthew Gregan <kinetik@ihug.co.nz> 06/08 10:21 AM >>>
> Greetings...
>
> I've tried searching the debian-user list archive already, and found some messages which probably contain the answer I'm after, but it seems that the actual messages aren't available, so I can't read them... (It was working a week ago when I last tried, but not yesterday or today...)
>
> Anyway, this should be an easy problem to solve for somebody. I've played around with eximconfig a bit, but I can't find how to solve the problem.
>
> I'm using exim and fetchmail for my mail delivery. Exim is setup using option 2 in eximconfig (recommended for dialup systems). Everything is working fine, I can receive email and send it fine, except if I try and send email to people on my ISP. The problem is that outgoing emails have their addresses rewritten as @ihug.co.nz, and my mail system classes these emails as local, so it tries to deliver them on my machine and fails.
>
> I thought I'd fixed this by stopping ihug.co.nz being considered local, but then email generated by cronjobs and such were finding their way to my provider (root@ihug.co.nz - since the outgoing mails were having their addresses rewritten).
>
> I think it should be a simple fix to solve this, but I don't know what it is... I've checked howtos but they only seem to cover other MTAs. :-/
>
> Thanks in advance.
> --
> Matthew Gregan kinetik@ihug.co.nz
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
>
Reply to: