Page 1 of 1

Time Limit on bounce scans?

PostPosted: Tue Jun 05, 2018 4:59 pm
by jim_frey
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.

Re: Time Limit on bounce scans?

PostPosted: Sat Jun 09, 2018 6:31 pm
by maschoff
Jim, what exactly do you mean by "bounces not getting filtered"? Could you give us more details or an example?

Re: Time Limit on bounce scans?

PostPosted: Tue Jun 12, 2018 6:56 pm
by jim_frey
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.

Re: Time Limit on bounce scans?

PostPosted: Tue Jun 12, 2018 7:09 pm
by jim_frey
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.

Re: Time Limit on bounce scans?

PostPosted: Wed Jun 13, 2018 9:14 am
by maschoff
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.

BTW, next version of OpenEMM will process bounces asynchronously. :-)

Re: Time Limit on bounce scans?

PostPosted: Wed Jun 13, 2018 7:12 pm
by jim_frey
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.

All the feedback loop emails from Amazon SES are from:
Is there a way to set a bav.rule so that emails coming from should be scanned for user emails that should be set to bounced?

I ended up putting in a bunch of rules instead
Code: Select all
Feedback-Type: abuse.*
.*The e-mail address you entered couldn't be found.*
.*Message expired: unable to deliver.*
.*Unknown user.*
.*recipient rejected.*
.*mailbox unavailable.*
.*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.*
Abuse-Type: complaint.*
From: complaints.*
This 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 exist
unknown 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 public
The user.s email name is not found\.
: unknown recipient:
^User not known
User not known
^Diese Adresse ist nicht mehr verfuegbar\.$
# tassilos hard world
^The following destination addresses were unknown
Received <<< 550 Invalid recipient <.*>
Unknown recipient address
address: <.*> ... failed
<<< 550 <.*> ... failed
550 Invalid recipient <.*>
550 Unknown local part .* in <.*>
553 Invalid recipient address
550 No such recipient
User name is unknown
no vaild recipients were found for this message
This user doesn.t have a account
# Sourceforge Bugreport #2620217
^    Unrouteable address

Re: Time Limit on bounce scans?

PostPosted: Thu Jun 14, 2018 8:34 am
by maschoff
Hint from our backend development: To ensure that these mails are recognized to be scanned for bounces, you could add a rule to the section [systemmail]:
Code: Select all

Re: Time Limit on bounce scans?

PostPosted: Thu Jun 14, 2018 5:20 pm
by jim_frey
Thanks, I had:

From: complaints.*

but I'll add that line too and see what happens.