I've been talking also to the sendmail.org people: Basically sendmail had a 'broken postmaster' problem: It couldn't locate the postmaster address. This was because sendmail was sending all mail via 'msp' and the system is configured not to accept external connections to it from the external ethernet NIC, only from the internal (as much as I can gather). It was fixed by regenerating the mail configuration files whith a modification in the submit.mc file changing: Feature (`msp') to Feature (`msp',`[127.0.0.1]') I first ran the make manually but I also tried it with SuSE's system configuration tools and it worked fine. So: 1) fetchmail was working OK and, when it couldn't raise the listener on port 25 was delivering mail to /var/spool/clientmqueue and mail wasn't moving. 2) Added the loopback option to submit.mc and changed the name of the Qf files to qf. 3) Problem fixed! mail is being delivered correctly. Thanks! Ciro. > -----Mensaje original----- > De: Carlos E. R. [mailto:robin1.listas@tiscali.es] > Enviado el: Martes, 25 de Marzo de 2003 01:18 p.m. > Para: suse-linux-e@suse.com > Asunto: RE: [SLE] fetchmail: can't raise the listener > > > > The 03.03.24 at 14:22, Ciro Guerra Lara wrote: > > > The sendmail called by fetchmail when the daemon > sendmail is not listening > > delivers mail to /var/mail/clientmqueue but it's not > processed after that > > (it stays in the queue). > > > > 2) looping processes that might be raising my load and > making the daemon > > sendmail unavaiable. > > You could have a look at fetchmail options like: > > -S <hosts>, --smtphost <hosts> > -m <command>, --mda <command> > -b <count>, --batchlimit <count> > -B <number>, --fetchlimit <number> > > I think a combination of the above perhaps could slow > down a bit the > fetching. If the postmaster is wrong, there is an option > to set it > explicitly: > > --postmaster <name> > > -- > Cheers, > Carlos Robinson > > > > -- > Check the headers for your unsubscription address > For additional commands send e-mail to suse-linux-e-help@suse.com > Also check the archives at http://lists.suse.com > Please read the FAQs: suse-linux-e-faq@suse.com > >