[Gloucs] Fetchmail and the list

[Dave Addison]

This is a PGP signed message sent according to RFC3156 [PGP/MIME]

--=_Turnpike_8Dyd64B72ZF+4L9G=
Content-Type: text/plain;charset=us-ascii;format=flowed
Content-Transfer-Encoding: quoted-printable

In message <sZWHozAaFKF+Ewsl@painswik.freeserve.co.uk>, Roland Hinkley=20
<roland@painswik.freeserve.co.uk> writes
>In message <20030102160450.GA4376@candy.10forbes.close>, Steve Searle=20
><steve@stevesearle.com> writes
>>Around 03:47pm on Thursday, January 02, 2003 (UK time), Roland Hinkley=20
>>scrawled:
>>
>>> A problem I have is relating to receiving mail via POP3. My main ISP is
>>> Freeserve and I am using Fetchmail and Exim on the Linux machine. I am
>>> trying to do multidrop but not having much success. I have tried reading
>>> the FAQ and man pages but still no luck. I wonder if anyone has any luck
>>> with this combination.
>>>
>>Don't despair - I did manage to get it set up after a bit of trial and
>>error and I pick up email from multiple pop3 accounts and distribute it
>>to different users' mailboxes.
>>
>>What is the exact problem - are you failing to pick it up at all, or is
>>the multidrop bit not working?
>>
>>It is probably worthwhile posting your .fetchmailrc file here - hide
>>any passwords before you do so.
>>
>>
>>Cheers
>>
>>Steve
>>
>
>Many thanks for the reply.
>
>I have tried again and with the fetchmailrc below multidrop seems to be=20
>working in general. Unfortunately mail from the list just goes to the=20
>user fetchmail with the warning
>X-Fetchmail-Warning: recipient address gloucs@mailman.lug.org.uk didn't=20
>match any local name
>added.
>
>Running in daemon mode /etc/fetchmailrc is:-
>
>set no bouncemail
>defaults:
>  antispam -1
>  batchlimit 100
>
>poll pop.freeserve.co.uk proto pop3 aka pop.pol.net.uk:
>  localdomains painswik.freeserve.co.uk Envelope 'Envelope-to'
>  user painswik.freeserve.co.uk with password ******* is * here keep;
>
>User names at the local domain get delivered fine, but cannot figure=20
>out how to get the list items deliverd to a user. Any ideas would help.
>Cheers
>
>Roland
>
I believe this is a known problem with multidrop. There are no headers=20
in the message which have a recipient on the local system (Being a=20
socially responsible list the message is addressed to the list and all=20
recipients are bcc'd.). This means that there is nothing that fetchmail=20
can use to determine the user that the message is intended for. I had a=20
similar problem and for a limited number of users (I have 17) you can=20
use the following syntax:

localdomains painswik.freeserve.co.uk
poll pop.freeserve.co.uk proto pop3 aka pop.pol.net.uk:
   user fred@painswik.freeserve.co.uk with password ******* is fred here=20
keep;
poll pop.freeserve.co.uk proto pop3 aka pop.pol.net.uk:
   user tom@painswik.freeserve.co.uk with password ******* is tom here=20
keep;
poll pop.freeserve.co.uk proto pop3 aka pop.pol.net.uk:
   user painswik.freeserve.co.uk with password ******* is * here keep;

The freeserve mailserver knows who the message was intended for and will=20
present it for download when the server is queried with the correct user=20
name. The multidrop at the end catches anything not addressed to a known=20
user. This is fairly ugly but prevents the problem you are seeing=20
(unless a message arrives between the user being downloaded and the=20
multidrop retrieval at the end of the file)
--=20
Dave Addison

--=_Turnpike_8Dyd64B72ZF+4L9G=
Content-Type: application/pgp-signature
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk 2.0.5

iQA/AwUAPhWdvr/4CdQVnTbiEQLjVACfXT8W1SQgHi32zXwxIwe5X0QMj5QAoJTb
mv0/d4nLGJC2paIHiIHTxeA3
=5h1j
-----END PGP SIGNATURE-----

--=_Turnpike_8Dyd64B72ZF+4L9G=--