Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRM-21378 Ensure that email abuse reports are treated as bounce type … #11226

Merged
merged 1 commit into from
Nov 22, 2017

Conversation

seamuslee001
Copy link
Contributor

…of spam

Overview

At present when an email abuse report bounce is processed it is treated as if it is a syntax bounce when it should be treated as bounce type of spam

Before

The current status. Please provide screenshots or gifs (LICEcap, SilentCast) where appropriate.

After

Email abuse reports are treated as spam bounces

Technical Details

There were changes made to support Hotmail's "Complaint report" in CRM-12425 this adds on yahoo's Email Abuse report which is virtually the same thing

ping @monishdeb @mattwire Matt i think you might be interested in this

@eileenmcnaughton
Copy link
Contributor

@seamuslee001 I'm inclined to merge this as it seems to be adding more metadata to an already established pattern of classification of bounces. My one issue is that this has not been reviewed in a timely manner, and hence needs the upgrade script portion to be moved to 4.7.29

@seamuslee001
Copy link
Contributor Author

@eileenmcnaughton have moved it to .29 now

@eileenmcnaughton
Copy link
Contributor

Merging per my previous comment

@eileenmcnaughton eileenmcnaughton merged commit 3214aa7 into civicrm:master Nov 22, 2017
@eileenmcnaughton eileenmcnaughton deleted the CRM-21378 branch November 22, 2017 00:42
sluc23 pushed a commit to ixiam/civicrm-core that referenced this pull request Jan 10, 2018
CRM-21378 Ensure that email abuse reports are treated as bounce type …
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants