Re: Problem with exim and fetchmail.
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 the moment. Hmm, I have no idea why it's putting your mail there. AFAIK it shouldn't be. All your mail should be going into /var/spool/mail/username. -- Rob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problem with exim and fetchmail.
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" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problem with exim and fetchmail.
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 this in /etc/hosts? (I don't know if it should be there though!): 127.0.0.1 localhost > > mda "exim -bm %s " > > This fixes the problem, but according to the FAQ this is just masking > some other problem with the SMTP listener. Any idea how to fix the > listener? Well here is a quote from the fetchmail FAQ (not that I understand it): --cut-here-- By default, the exim listener enforces the the RFC1123 requirement that MAIL FROM addresses you pass to it have to be canonical (e.g. with a fully qualified hostname part). This is a potential problem if the MTAs upstream from your fetchmail don't necessarily pass canonicalized From and Return-Path addresses, and fetchmail's "rewrite" option is off. The specific case where this has come up involves bounce messages generated by sendmail on your mailer host, which have the (un-canonicalized) origin address MAILER-DAEMON. The right way to fix this is to enable the "rewrite" option and have fetchmail canonicalize From and Return-Path addresses with the mailserver hostname before exim sees them. If you must run with "rewrite" off, there is a switch in exim's configuration files that allows it to accept domainless MAIL FROM addresses; you will have to flip it by putting the line sender_unqualified_hosts = localhost in the main section of the exim configuration file. Note that this will result in such messages having an incorrect domain name attached to their return address (your SMTP listener's hostname rather than that of the remote mail server). --cut-here-- Adrian -- .signature in post -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problem with exim and fetchmail (solved).
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 UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problem with exim and fetchmail.
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 according to the fetchmail FAQ, this approach is a bad idea: >From the fetchmail FAQ: using an MDA for delivery is discouraged. If you throw those options away, fetchmail will now forward your mail into your system's normal Internet-mail delivery path. Actually, using an MDA is now almost always the wrong thing; the MDA facility has been retained only for people who can't or won't run a sendmail-like SMTP listener on port 25. The default, SMTP forwarding to port 25, is better for at least two major reasons. One: it feeds retrieved POP and IMAP mail into your system's normal delivery path along with local mail and normal Internet mail, so all your normal filtering/aliasing/forwarding setup for local mail works. Two: because the port 25 listener returns a positive acknowledge, fetchmail can be sure you're not going to lose mail to a disk-full or some other resource-exhaustion problem. Using the SMTP delivery (no mda option) works fine with sendmail, so just wanted to make it work with exim. Thanks -- Rob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problem with exim and fetchmail.
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.27.36/255.255.255.255
>
> Thanks for the suggestion, but that didn't do it. It's not
> complaining about the source, but rather the destination when
> fetchmail contacts exim for the SMTP transfer. I even tried
> receiver_verify=false and qualify_recipient=localhost with no luck.
>
> Here's some relevant bits from my /etc/exim.conf:
>
> qualify_domain = raven.localhost
> local_domains = raven.localhost
> receiver_unqualified_nets = 192.168.0.0/255.255.255.0
>
> If it matters (and it might), this machine normally has a dynamic
> connection to the internet (and a Dynamic IP), so I have bind/resolv
> set up to think this machine is under the (bogus) "localhost" domain.
> That seems to satisfy all the apps (lprng, sendmail originally, etc.)
> that were having trouble before, but I suppose this "hack" could be
> causing exim trouble.
>
> I've read the mini/Dynamic-IP-Hacks HOWTO, and their suggestions
> caused the same exim SMTP failures. I've also tried "localhost" and
> "localhost:raven.localhost" for each of the above variables without
> success.
>
> Thanks
> --
> Rob
>
>
---End quote
Hi Rob,
I'm using the following debian packages out of /debian/hamm/hamm:
exmh, exim, fetchmail, mh, metamail and mime-support.
The following is what I did for a ppp connection to an ISP using dynamic
addressing and pop3. I also used hack 5? of the mini/Dynamic-IP-Hacks HOWTO
(the one where you make new hosts-up and hosts-down files). This
Dynamic-IP-Hackshack
worked perfectly for me.
Anyhow my ~/.fetchmailrc is:
poll milo.cfw.com <--- Your ISP Mail server goes here
protocol pop3
uidl
username vtorrico is [EMAIL PROTECTED] here
password xxx
smtphost milo.cfw.com <--- Your ISP Mail server goes here
# keep
fetchall
mda "exim -bm %s"
My pertinent part of /etc/exim.conf is:
# This is the main exim configuration file.
# It was originally generated by `eximconfig', part of the exim package
# distributed with Debian, but it may edited by the mail system
administrator.
# This file originally generated by eximconfig at Fri Aug 8 20:09:27 EDT
1997
# See exim info section for details of the things that can be configured
here.
# General configuration here, such as local domains
qualify_domain = cfw.com < Your ISP domain name
local_domains = localhost
local_domains_include_host = true
local_domains_include_host_literals = true
never_users = root
trusted_users = mail
smtp_verify = true
gecos_pattern = ^([^,:]*)
gecos_name = $1
received_header_text = "Received: \
${if def:sender_fullhost {from ${sender_fullhost} \
${if def:sender_ident {(${sender_ident})}}\n\t}\
{${if def:sender_ident {from ${sender_ident} \
by ${primary_hostname} \
${if def:received_protocol {with ${received_protocol}}} \
(Exim ${version_number} #${compile_number})\n\t\
id ${message_id} (Debian)"
end
Make sure the following line is in /etc/inetd.conf:
smtpstream tcpnowait mail/r/sbin/exim exim -bs
To make From: part of messages read correctly change or add the localname
statement to /etc/mh/mtstailor. The localname should be the domain name of
your ISP. Mine is cfw.com.
This is my /etc/mh/mtstailor:
mmdfldir: /var/spool/mail
mmdflfil:
uucpldir: /var/spool/mail
uucplfil:
mmdelim1: \001\001\001\001\n
mmdelim2: \001\001\001\001\n
mmailid:0
umincproc:
lockstyle: 1
lockldir:
hostable: /usr/lib/mh/hosts
sendmail: /usr/sbin/sendmail
localname: cfw.com
Cheers,
Victor
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble?
e-mail to [EMAIL PROTECTED] .
Re: Problem with exim and fetchmail.
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 to the FAQ this is just masking some other problem with the SMTP listener. Any idea how to fix the listener? Thanks for the help... -- Rob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problem with exim and fetchmail.
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 name: > > fetchmail: SMTP> RCPT TO: > fetchmail: SMTP< 501 : recipient address must contain a domain > > but it's fetchmail that's trying to send the mail locally to > with no domain. I feel sure I've overlooked something simple. Any > help/(RTFM pointer) would be appreciated. I believe that exim wants a fully qualified address. Try putting this in /etc/exim.conf: qualify_domain = localhost qualify_recipient = localhost The first line is for outgoing mail and the second one (which defaults to the first one if it is missing) is for incoming mail. In case it helps, here is what I currently have in my ~/.fetchmailrc: poll mail.myisp.com proto pop3 user adrian.bridgett is [EMAIL PROTECTED] here password xxx fetchall mda "exim -bm %s " Otherwise it might be something mentioned in the fetchmail FAQ around line 700. Adrian -- .signature in post -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
