Autor: Frank DeChellis DSL Fecha: A: exim-users Asunto: Re: [exim] Spool collecting but not sending
> > On 2010-01-01 at 21:12 -0500, Frank DeChellis DSL wrote:
>> On Fri, 1 Jan 2010, Frank DeChellis DSL wrote:
>>> I have one instance of it running on our native IP and port 25 and it runs
>>> great, and has for years.
>>>
>>> I just setup another instance of it on the same server with a different IP
>>> address and port number. The new install on port 999 has it's own log and
>>> spool directory.
>>>
>>> We just copied the config file form the orginal exim install, specified
>>> the different directories, IP and port number.
>>>
>>> When we use it to send mail the message is collected by Exim, placed into
>>> the new spool directory and just sits there.
>>>
>>> When I telnet to that IP and port exim answers fine.
>>>
>>> Before I setup the separate spool and log directory, it was sending email
>>> with the different port and IP using the same log and spool directories
>>> as the other exim, but I didn't feel comfortabel with that setup.
>>>
>>> Do I need to tell exim where the messages are being queued waiting to be
>>> sent?
>>>
>>> Thanks
>>> Frank
>>>
>>
>> I forgot to add one detail. After sending some messages through this
>> install and having the messages sit in the queue, the command
>>
>> /usr/pkgsbin/exim -qff -C /usr/pkg/etc/exim2/configure
>>
>> clears the queue and delivers the mail no problem.
>
> So *something* needs to start delivering from the spool.
>
> Typically you would either have the main listening Exim start
> queue-runners, or you'd invoke the queue-runners from cron (but that's
> more likely when you're in a client set-up with no listening daemon).
>
> { exim -bd } just runs a listening daemon. You need { exim -bd -q15m }
> or the like, to run a daemon which also starts queue-runners.
>
> How are you starting your second Exim?
>
> -Phil
>
