On Wed, 7 May 2003, Ollie Cook wrote:
> I have noticed while writing a local_scan function that messages that are
> frozen with LOCAL_SCAN_ACCEPT_FREEZE don't get a message log file written to
> the spool:
>
> root@mutare:[mutare] (44) # grep 19DSMF-000OSb-Mw /var/log/exim/main_4.log
> 2003-05-07 18:05:34 19DSMF-000OSb-Mw Content scan results: [filter: No .filter file] [vscan: EICAR]
> 2003-05-07 18:05:34 19DSMF-000OSb-Mw Content scan timings: [filter: 95] [vscan: 289079]
> 2003-05-07 18:05:34 19DSMF-000OSb-Mw <= ollie@??? H=mutare.noc.clara.net [195.8.70.95] P=smtp S=922
> 2003-05-07 18:05:34 19DSMF-000OSb-Mw frozen by local_scan()
> root@mutare:[mutare] (45) # mailq
> 5m 940 19DSMF-000OSb-Mw <ollie@???> *** frozen ***
> ollie@???
>
> root@mutare:[mutare] (46) # /usr/exim/bin/exim -Mvl 19DSMF-000OSb-Mw
> Failed to open msglog file for 19DSMF-000OSb-Mw: No such file or directory
>
> Is this the expected behaviour under 4.14?
My interpretation of this phenomenon has always been that the per-message
log files are created by a _delivery_ attempt, and that you haven't yet
reached that stage (you are still _receiving_ the message when in
local_scan). So, yes, it is expected (by me!)
(A quick glance at the code in deliver.c appears to corroborate my
interpretation. Mind you, a quick glance at the docs didn't throw up a
definitive answer)
BTW1 you will get similar effects if using exiscan to reject messages
BTW2 it may be expected; whether it is desirable I shall leave to others
to debate.
>
> Thanks,
>
> Ollie
HTH,
Richard
