Ye gods, it was require_explicit_destination that sorted it. If only I'd not glossed over that part in the original reply/looked more thoroughly for that configuration directive :(.
Very many thanks to yourself and Patrick for sticking with me during this! I suspect less patient guys would have ignored me long ago :). Best regards and thanks once again, Biggs On 15/10/06, Mark Sapiro <[EMAIL PROTECTED]> wrote: > BigglesZX wrote: > > > >If I use a local mail account (using mutt) to send a message to > >[EMAIL PROTECTED], the message is passed through fine - goes out on > >to the list. > > > >If, however, I send the message to the remote account checked by > >fetchmail, then run fetchmail to retrieve the message, it does not > >make it to the list. Fetchmail is set up to pass on to > >[EMAIL PROTECTED] just as above, and a reading of the exim log gives > >the impression that it has passed through okay, but then once the > >administrative approval request mail is generated to the list admin, > >that message gets frozen with the following error: > > > >2006-10-14 19:26:57 1GYoDp-00066c-Ec ** [EMAIL PROTECTED]: > >Unrouteable address > > > >I thought I had configured exim to accept mail to this domain > >correctly, but perhaps not - my question is why mailman won't deliver > >the post to the list when it is sent in this manner. > > > I'm not really clear on what you are seeing here, but it seems that the > post via fetchmail is being held for moderator approval and the notice > to the moderator is not making it from Mailman to the moderator. Is > this correct so far? > > If so, there are two issues. Why is the post held, and what happens to > the moderator notice? > > If you go to the admindb web interface, do you see the post? If so, > what is the reason it is held? This info is also in the 'vette' log. I > suspect it is "implicit destination". As Patrick said very early in > this thread, you have to look at Privacy options...->Recipient filters > and either set require_explicit_destination to No or add > [EMAIL PROTECTED] to acceptable_aliases. > > > >The only difference between the two sendings is the sender's address - > >the post goes through when the sender is @localhost or my FQDN - or to > >put it another way, no admin message is generated when the mail > >originates from the local machine. Have I missed a configuration > >option relating to mail originating from the local machine? > > > How about the To: address? Is it the same in both cases, or is it > [EMAIL PROTECTED] in one case and [EMAIL PROTECTED] > in the other. If the latter, see above. > > As far as the notice to the admin getting stuck, I'm not sure. The > message > > >2006-10-14 19:26:57 1GYoDp-00066c-Ec ** [EMAIL PROTECTED]: > >Unrouteable address > > seems to be saying that something was sent and bounced to > listname-bounces and that address is unroutable. What does your Exim > config have for the mailman router? > > -- > Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > -- [EMAIL PROTECTED] http://www.biggleszx.com/ ICQ 104870111 [ Because I used to be... T H E B A S T A R D O P E R A T O R F R O M H E L L ! ! ! ...and sometimes, late at night I get these twitches. Like dead people get. (Or, as I prefer to call them, perfect computer users) In the mornings I get them too. Like when the phone rings. And when I get email. And when people talk to me. AND when people are hogging the expresso machine to make fluffy milk. But apart from that I'm cured. A new man. ] ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
