Hi Martin,
Thanks for the hint, I've checked the mailscanner wiki and I did even a
quick check on the exim processes running (below is the result) and it
looks like the exim and mailscanner configuration are set to work
successfully:
Here what I get from a process side of it (both exim instances are running
as per mailscanner-exim document):

----------------------------------------------------------
[root@smtp ~]# ps -aux | grep exim
Warning: bad syntax, perhaps a bogus '-'? See
/usr/share/doc/procps-3.2.8/FAQ
exim      2963  0.0  2.4 315456 95528 ?        S    12:01   0:04
MailScanner: waiting for messages
*exim      4331  0.0  0.0  96660  1744 ?        Ss   Jun28   0:00
/usr/sbin/exim -C /etc/exim/exim.conf -bd*
*exim      4333  0.0  0.0  96664  1636 ?        Ss   Jun28   0:00
/usr/sbin/exim -C /etc/exim/exim_out.conf -q15m*
exim      4355  0.0  0.8 203216 33020 ?        Ss   Jun28   0:01
MailScanner: starting child
exim      6642  0.0  2.4 314960 95104 ?        S    13:01   0:03
MailScanner: waiting for messages
exim     14077  0.2  2.4 315020 95104 ?        S    15:01   0:02
MailScanner: waiting for messages
exim     14079  0.0  0.9 241920 38976 ?        S    15:01   0:00 Baruwa SQL
root     15699  0.0  0.0 103224   860 pts/0    S+   15:24   0:00 grep exim
exim     24323  0.0  2.4 315072 95120 ?        S    09:01   0:04
MailScanner: waiting for messages
exim     27936  0.0  2.4 314960 95104 ?        S    10:01   0:04
MailScanner: waiting for messages
----------------------------------------------------------

Before I pushed the emails through my baruwa server, I have added the "*:
/etc/exim/accepted_relay_network.txt*" in the */etc/exim/exim.conf* file as
"*relay_from_hosts*" option to accept the network ranges included in the
manually created file "/etc/exim/accepted_relay_network.txt" (each network
range is on a separate line as per documentation), I didn't add any domain
in baruwa UI yet... could this be the cause of the issue then?
Thanks again for any hint.
Cheers,
Anis


On 2 July 2012 20:15, Martin Hepworth <[email protected]> wrote:

> Sounds like your not running the outbound exim mta as a daemon at startup
>
> Have a look in the mailscanner wiki for how to setup two exim instances so
> one accepts incoming email for mailscanner and the other takes the
> mailscanner output from the holding queue and relays it onward
>
> Martin
>
>
> On Monday, 2 July 2012, Anis Jendoubi wrote:
>
>> Hi,
>> I've installed Baruwa through puppet, I must admit from the beginning
>> that I'm a beginner in EXIM mta (my preferred is Postfix), however I'm
>> trying to learn it the hard way ;)
>> I have baruwa setup as an outbound relay server that filters emails, it
>> does accept emails from few specific network ranges and should relay them
>> clean to the outside recipients.
>> it's all well until the point to relay them outside where I have to
>> manually run the command given in an early post I have searched and found:
>> "exim -C /etc/exim/exim_out.conf -v -qff", without this command the mails
>> get stuck somewhere and it does not show them on the outbound queue of
>> Baruwa UI.
>> Anyone had this before? and how to fix this without creating a dedicated
>> cron job for this command?
>> Thanks for any helpful advice.
>> Cheers,
>> Anis
>>
>
>
> --
> --
> Martin Hepworth, CISSP
> Oxford, UK
>
> _______________________________________________
> Keep Baruwa FREE - http://pledgie.com/campaigns/12056
>
>
_______________________________________________
Keep Baruwa FREE - http://pledgie.com/campaigns/12056

Reply via email to