I'm running OpenEMM on a cloud server. After a few mailings I'm coming to the conclusion that bounces don't always get filtered, and I think it's because I'm running the processor at 100% when the mailing is sent out. My guess is that there's a time limit on the code that runs the bounce filter, and because the processor is slammed, the time runs out too quickly on the filter. I'm wondering if that is in fact what's happening, and if so, can I change the time the filter code is allowed to run?

The next mailing I send out I will increase the cloud server space and see if that resolves the bounces that aren't properly filtered.

The filters in bav.rule seem to get skipped sometimes. With the Amazon SES set up, when a feedback loop is sent (so the user clicked "Spam" in say yahoo/hotmail/aol/whatever) Amazon sends an email from a complaint address back to the sending address of the email. You must remove that person from the mailing list because if you get too many of the complaints you get kicked off the Amazon SES system. I've got a bunch of filters set up in bav.rule that seem to catch the emails and then mark the email as bounced, but for some reason it seems the bav.rule doesn't always work even though the format of the email is the same. The only thing I can put together is it seems to happen when the server is loaded down.

I sent out another email yesterday to 80k. I bumped up the cloud server to use 96GB of RAM and 20 CPU's so I know there was enough horsepower to accomplish anything. I will check over the complaint emails that were sent to see if bav.rule caught them all.

I am still seeing the same problem even with much more power on the hosting machine. Some of the emails are getting properly filtered by bav.rule and set to bounce, others that have the exact same format are not. Very odd.

While bounce processing of OpenEMM works synchronously, timeout is a generous 2 minutes. If a timeout is reached this should be logged in files with string "is_no_systemmail", "scan_and_unsubscribe" or "filter_or_forward" as part of the file names in directory /home/openemm/var/log/. Please have a look.

Thanks for the info, there are no files with those names. It's very odd because the format of the emails is the same, just different email addresses. For example I'm seeing it with Yahoo feedback loop emails.

[hard]#Feedback-Type: abuse.*.*The e-mail address you entered couldn't be found.*.*Message expired: unable to deliver.*.*Unknown user.*.*recipient rejected.*.*mailbox unavailable.*.*non-member.*.*Requested action not taken: mailbox unavailable.*.*Recipient address rejected.*.*The email account that you tried to reach is disabled.*.*Suspended Inactive mailbox.*.*This user doesn't have a .* account.*.*The email account that you tried to reach is disabled.*.*Suspended Inactive mailbox.*.*does not exist here.*.*Requested action not taken: mailbox unavailable.*.*Addressee unknown.*.*recipient rejected.*.*No such domain at this location.*.*invalid recipient.*.*Invalid recipient.*.*Addressee unknown.*.*This user doesn't have a .* account.*.*Not our Customer.*.*Unable to relay recipient in non-accepted domain.*.*mailbox unavailable.*.*Amazon SES has suppressed sending to this address because it has a recent history of bouncing.*.*undeliverable address.*^(From|Sender):.*complaints.*X-Forefront-Antispam-Report.*X-Microsoft-Antispam.*Abuse-Type: complaint.*From: complaints.*From: complaints@us-west-2.email-abuse.amazonses.com.orgThis is an email abuse report for an email message.*This is a.*Abuse Report for an email message received.*.*email abuse report.*^Subject: .*complaint about message from.*Diagnostic-Code: Amazon SES has suppressed sending to this address.*.*No account by that name here.*The recipient does not existunknown user|user unknown|user not found^There is no such user\.^ Recipient.s Mailbox unavailable^Receiver not found:^Sorry, no mailbox here by that name\.^ The recipient name is not recognized^Invalid receiver address:^did not reach the following recipient\(s\):^Ihre Mail ist leider nicht zustellbar\.^Sorry. Your message could not be delivered to:^No such user\.^ user .* not known at this site\.^ unknown local-part .* in domain .*^.* sorry, no such mailbox here^User not listed in publicThe user.s email name is not found\.: unknown recipient:^User not knownUser not known^Diese Adresse ist nicht mehr verfuegbar\.$## tassilos hard world^The following destination addresses were unknownReceived <<< 550 Invalid recipient <.*>Unknown recipient addressaddress: <.*> ... failed<<< 550 <.*> ... failed550 Invalid recipient <.*>550 Unknown local part .* in <.*>553 Invalid recipient address550 No such recipientUser name is unknownno vaild recipients were found for this messageThis user doesn.t have a yahoo.de account# Sourceforge Bugreport #2620217^ Unrouteable address#

That didn't work. So I wrote a perl script that exports a file that I import back into openemm as bounces. I guess I could have the perl update the db directly, if I have some time I'll play with that.