Aah, I was incorrectly assuming before that the smtp daemon would take care
of sending all outgoing emails. (As a sidenote, is there not some logic in
my way of thinking: why would a program so complex allow setuid as root?)
Anyways, this means I have to rethink my setup. The considerations are:
route outgoing smtp traffic from the containers correctly to the internet,
make some construction to allow containers to spawn sendmail on the host
node or use an smtp connection from container to host as Bill Hacker
suggested. Feel free to comment. Thanks for your help so far.
Regards,
Lennart Ackermans
On Sat, Mar 10, 2012 at 10:34 PM, Dave Lugo <dlugo@???> wrote:
> On Sat, 10 Mar 2012, Lennart Ackermans wrote:
>
> node. My question is, how does the Exim sendmail binary (which according
>> to
>> the man page seems to be called "receiving process") tell the smtp daemon
>> to process emails in the queue? E.g., is there a socket or pipe I don't
>> know of?
>>
>>
> /reads docs for 5 minutes
>
> I'm going to guess that the final thing the receiving process
> does, after it has accepted the message, but before it exits,
> is to fork a new exim instance with -Mc <message-id> as the
> arguments.
>
> This is in contrast to calling a queue runner to process items
> sitting in the queue that were not able to be delivered earlier.
>
> --
> ------------------------------**--------------------------
> Dave Lugo dlugo@??? No spam, thanks.
> Are you the police? . . . No ma'am, we're sysadmins.
> ------------------------------**--------------------------
>
>
> --
> ## List details at https://lists.exim.org/**mailman/listinfo/exim-users<https://lists.exim.org/mailman/listinfo/exim-users>
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
>
