hello all!
after a lot of troubles, i have - at last - a working exim and fetchmail
set-up.
i must thank all in the group who helped. in fact, that alone kept me going.
i will like to tweak it further to suit my needs. but i at least have a
working set-up now.
thanx again
- sandip
--
To
On Mon, 2001-10-22 at 17:36, Chris Concannon wrote:
> I'm running woody on my desktop machine and I'm running into problems
> trying to get email working. I want to get my email with fetchmail, read
> it with mutt, and send it with exim. I'm on a network link at my
> university and my IP address
I'm running woody on my desktop machine and I'm running into problems
trying to get email working. I want to get my email with fetchmail, read
it with mutt, and send it with exim. I'm on a network link at my
university and my IP address isn't going to change all year.
Fetchmail and exim do not
I'll try to point this out by assuming your username on the pop3 server and
on your local machine is "jason". The hostname of your local one seems to be
"magneto.whizzird.net".
If you tell fetchmail in .fetchmailrc "poll mail.whizzird.net user jason
password secret" it will fetch the mail from the
I just replaced sendmail with exim on a satellite box on my system. It's also
my main workstation. I run fetchmail on it to fetch from my mail server, but
as soon as fetchmail fetches, exim forwards it back to the smart host.
Is there someway for me to have exim not forward the fetched mail? Or doe
On Thu, 21 Oct 1999, Philip Lehman wrote:
>root, the command in /etc/ppp/ip-* should be preceded by a `sudo`
>command, e.g.
>
>sudo fetchmail -d 600
It's `sudo -u ...`, forgot the '-u', sorry.
--
Space for hire. Contact Philip Lehman <[EMAIL PROTECTED]>
On Thu, 21 Oct 1999, Richard Clarke wrote:
>Could someone point me to documentation for exim and fetchmail which is
>easier to understand than the "man" files.
There is more documentation in /usr/doc or /usr/share/doc. It's more
comprehensive, but it's probably not
Sorry, I put the quotes in the wrong place.
It should be mda "/usr/sbin/sendmail -oem $USER"
Sebastian Canagaratna
me"
When I start my machine in the morning I type fetchmail -d 600
to run it as a daemon, fetching mail every 10 min. It will ask for
your password at this time.
I hope this helps.
Sebastian Canagaratna
Department of Chemistry
Ohio NOrthern University
Ada, OH 45810
> Hi,
> Could some
Hi,
Could someone point me to documentation for exim and fetchmail which is
easier to understand than the "man" files. As I understand, exim is a local
mail agent which uses SMTP? to send mail around the localnetwork. Fetchmail
delivers remote mail, POP3 in my case, to this local n
On 25-Jun-99 Christian Dysthe wrote:
> Please post a solution to the list. I have spent a lot of time
> trying to make fetchmail/exim 3.02 work, but no go. I rely on my MUA's pop
> abilities right now.
The author of Exim says it is an ipv6 issue and he is looking into it now.
--
Andrew
I just downgraded to 2.11. Reinstated my old exim.conf, and everything is back
to normal working order.
So, guess it will not be 3.02 on my box until this is fixed.
On 25-Jun-99 Pollywog wrote:
>
> On 25-Jun-99 George Bonser wrote:
>>
>> Hmm, looks like you have enabled ipv6 support in some thi
Please post a solution to the list. I have spent a lot of time
trying to make fetchmail/exim 3.02 work, but no go. I rely on my MUA's pop
abilities right now.
Right now exim 3.02 and fetchmail is a no go combo.
TIA.
On 25-Jun-99 Pollywog wrote:
>
> On 25-Jun-99 George Bonser wrote:
>>
>> Hmm,
On 25-Jun-99 George Bonser wrote:
>
> Hmm, looks like you have enabled ipv6 support in some things but not
> others. ;)
It looks as though I will have to stick with version 2.11 of Exim, or else
build from source instead of a Debian package, so that I can keep the ipv6
stuff out.
--
Andrew
On 25-Jun-99 George Bonser wrote:
>
> Hmm, looks like you have enabled ipv6 support in some things but not
> others. ;)
YES :) It looks that way, but I did not do that. I will look at the docs to
see if perhaps I did so in error and how I might fix that.
I have returned to version 2.11 until
This is what Fetchmail says:
~$fetchmail
1 message for shadypond.com/pollywog at mercury.he.net (4589 octets).
reading message 1 of 1 (4589 octets) .fetchmail: SMTP connect to localhost
failed
fetchmail: SMTP transaction error while fetching from mercury.he.net
fetchmail: Query status=10
If this
On 24-Jun-99 Sebastian Canagaratna wrote:
> I had the same sort of problem
> Did you run eximconfig?
> The .fetchmailrc should also have a line
> mda "/usr/lib/sendmail -oem $USER" or something like that:
> do a man fetchmail
>
> My problem was that that it fetched the mail but would not deliver
I had the same sort of problem
Did you run eximconfig?
The .fetchmailrc should also have a line
mda "/usr/lib/sendmail -oem $USER" or something like that:
do a man fetchmail
My problem was that that it fetched the mail but would not deliver
it to me. Your problem may be a little more serious. In t
I cannot get Fetchmail to deliver mail now that I upgraded Exim to 3.02.
The problem is with Exim or my DNS but I cannot figure out how to fix this.
Any ideas?
1999-06-25 00:41:27 connection from [:::127.0.0.1] refused
(:::127.0.0.1 does not match any IP address for localhost)
1999-06-25 0
On Wed, 05 May 1999 17:45:09 -0400, you wrote:
>I regard this as a bug in the installation procedure. Either
>fetchmail should deliver to "user" (without the "@localhost")
>or exim should be configured by default to accept such mail.
See bug #36837. The installation script of exim tells you that
Jake Bishop <[EMAIL PROTECTED]> writes:
Fetchmail's documentation has a special section on working wiht
exim. It specifically mentions that you should add localhost to your
exim's accepted domain names. Did you do that?
Cheers!
> I am having a problem getting exim and fetch
Jake Bishop <[EMAIL PROTECTED]> writes:
> Hello,
> I am having a problem getting exim and fetchmail to work.I just
> installed Slink.I used option #2 in the
> eximconfig menu. when I try to send a message with mutt it only goes to
> /var/spool/mail/jak3b.
> when I try to
On Wed, 05 May 1999 10:45:44 -0700, you wrote:
>I am having a problem getting exim and fetchmail to work.I just
>installed Slink.I used option #2 in the
>eximconfig menu. when I try to send a message with mutt it only goes to
>/var/spool/mail/jak3b.
>when I try to use fetchmail I g
Hello,
I am having a problem getting exim and fetchmail to work.I just
installed Slink.I used option #2 in the
eximconfig menu. when I try to send a message with mutt it only goes to
/var/spool/mail/jak3b.
when I try to use fetchmail I get this message: 1 message for jak3b at
Michael Beattie[SMTP:[EMAIL PROTECTED]
> Sent: Saturday, October 17, 1998 9:19 AM
> To: Russ Cook
> Cc: debian user list
> Subject: Re: exim and fetchmail
>
>
> Change these lines in /etc/exim.conf:
>
> qualify_domain =
>
&g
ECTED] and is
denied. Any more hints? This is frustrating.
--
From: Michael Beattie[SMTP:[EMAIL PROTECTED]
Sent: Saturday, October 17, 1998 9:19 AM
To: Russ Cook
Cc: debian user list
Subject: Re: exim and fetchmail
Change these lines in /etc/exim.conf:
qualify_d
Change these lines in /etc/exim.conf:
qualify_domain =
local_domains = :localhost
local_domains_include_host = true
local_domains_include_host_literals = true
sender_host_reject_relay = *
sender_unqualified_hosts = localhost
I cant remember which ones are relevant, but that makes it work.
I am running exim as my MTA, and I'm using fetchmail to retrieve my mail
from
my ISP. My ISP account is [EMAIL PROTECTED] My local account is
[EMAIL PROTECTED]
My mail is not getting delivered. fetchmail knows that [EMAIL PROTECTED]
is
russ here, and negotiates the mail retrieval. A script of
Victor Torrico <[EMAIL PROTECTED]> writes:
> In the interim, using fetchmail and exim, I still can only get my
> incoming mail to go into the /var/spool/exim/input directory. How do I
> get the mail in this directory out to use it in exmh? What steps must I
> follow? I'm brain frazzled as of th
Thanks for the reply. It turns out that the problem lies with
fetchmail. It's been fixed in an upcoming release. You won't need
any hacks in your exim.conf file anymore, nor will you need
fetchmail's -mda option.
--
Rob
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe"
On Aug 10, Rob Browning wrote
> Adrian Bridgett <[EMAIL PROTECTED]> writes:
>
> > I believe that exim wants a fully qualified address. Try putting this in
> > /etc/exim.conf:
> > qualify_domain = localhost
> > qualify_recipient = localhost
>
> I tried this, and it didn't help.
Have you got t
After some further cogitation, I spoke to the fetchmail author, and it
turns out that it was a problem with fetchmail. He's fixed it in the
next version, soon to be released. Once that's done fetchmail users
on sytems running exim shouldn't need the -mda option to fetchmail or
any special workar
Actually it turns out that using
receiver_unqualified_hosts=myhost.mydomain
fixes the problem nicely. Assuming no one else sees a problem with
this solution, I'm going to suggest it to the fetchmail FAQ
maintainers to replace the current -mda "exim -bm %" solution.
Thanks
--
Rob
--
TO UNS
Victor Torrico <[EMAIL PROTECTED]> writes:
> mda "exim -bm %s"
Thanks for the help, but I had discovered (see one of my previous
messages) that I could get it to work with this option. However, I
wanted to know why it was necessary. So far everyone who has a
working setup is using it, but accor
Mail of Rob Browning:
> Christoph Lameter <[EMAIL PROTECTED]> writes:
>
>> Put the following into /etc/exim.conf
>> (customize for your setup! by default exim does not accept unqualified
>> e-mail!)
>>
>> qualify_domain = waterf.org
>> receiver_unqualified_nets =
> 192.168.0.0/255.255.255.0:206.1
Adrian Bridgett <[EMAIL PROTECTED]> writes:
> I believe that exim wants a fully qualified address. Try putting this in
> /etc/exim.conf:
> qualify_domain = localhost
> qualify_recipient = localhost
I tried this, and it didn't help.
> mda "exim -bm %s "
This fixes the problem, but according
On Aug 08, Rob Browning wrote
>
> I just switched over from sendmail to exim on one of my machines, and
> I was having a problem getting my mail from any other machine via
> fetchmail. If I put fetchmail in verbose mode I can see that exim is
> rejecting the SMTP command because there's no domain
I just switched over from sendmail to exim on one of my machines, and
I was having a problem getting my mail from any other machine via
fetchmail. If I put fetchmail in verbose mode I can see that exim is
rejecting the SMTP command because there's no domain name:
fetchmail: SMTP> RCPT TO:
fetchm
38 matches
Mail list logo
