The following bug has been SUBMITTED. ====================================================================== http://dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000189 ====================================================================== Reported By: OutboundIndex Assigned To: ====================================================================== Project: DBMail Bug ID: 189 Category: Database layer Reproducibility: always Severity: crash Priority: normal Status: new ====================================================================== Date Submitted: 02-Apr-05 02:59 CEST Last Modified: 02-Apr-05 02:59 CEST ====================================================================== Summary: if alias == deliver_to, dbmail-smtp hogs mem until killed by oom or queue gives up Description: We had several thousand aliases correctly in the format:
alias: [EMAIL PROTECTED] deliver_to: 701 However, after these severe overloads kept occurring on each queue run if certain recips were in the run, I found 9 users who had aliases like this: alias: [EMAIL PROTECTED] deliver_to: [EMAIL PROTECTED] There is an actual user named [EMAIL PROTECTED] The machine would become unusuable during the queue run attempts. Could do nothing but wait for oom to kill something or the queue to give up. I watched "top" during this and could usually see 5 or 6 dbmail-smtp's at the top of the list for mem usage, each creeping up until it was taking 10% to 30% of mem. A paste from the log after turning trace level up to 5 is in the "additional information." I don't know if this type of alias is specifically disallowed. It was my understanding from the docs that either the user_idnr OR the user name was acceptable for a deliver_to. I suggest even if this is or becomes a forbidden format, that a slight change in the code could prevent this type of looping. ====================================================================== Bug History Date Modified Username Field Change ====================================================================== 02-Apr-05 02:59OutboundIndex New Bug ======================================================================
