[exim-dev] [Bug 1178] queue runner is using huge amounts of …

Inizio della pagina
Delete this message
Reply to this message
Autore: Graeme Fowler
Data:  
To: exim-dev
Oggetto: [exim-dev] [Bug 1178] queue runner is using huge amounts of memory
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1178




--- Comment #5 from Graeme Fowler <graeme@???> 2011-11-28 16:20:45 ---
(In reply to comment #4)
> Graeme, even if some feature is deprecated, it shouldn't be exploitable.


Quite right. It isn't, so far as I can tell.

However: two things strike me as odd...

1. It's flagged as spam, but still got through the ACL and into the queue.
2. It contains a virus, which clamd picks up, but it got through and made it
into the queue.

I don't doubt that there's a problem with the queue runner here, but the fact
that the message is detected as spam and a virus but still got through the
"deny" phases of your ACLs is a little puzzling.

The only way to get something handled by a queue runner is for all "deny"
clauses to fail, and an "accept" be hit after DATA.

However, that's not the real problem. The real problem is what the queue runner
does with the message; this in itself is interesting because queue runners only
ever read messages, they don't do anything else with them (until they've been
confirmed as delivered, at which point they are deleted).

I'd very much like to see you attach strace to the affected queue runner to see
where it's getting twisted.

In fact, if you can do the following:

killall exim
strace -o /tmp/strace.txt -fFv -tt /path/to/exim -q

Leave it to cook for a while. Post the output.

Graeme


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email