View Issue Details

IDProjectCategoryView StatusLast Update
0002395Composrticketspublic2016-04-10 18:49
ReporterPatrick SchmalstigAssigned ToChris Graham 
SeverityMinor-bug 
Status resolvedResolutionfixed 
Product Version 
Fixed in Version 
Summary0002395: Infinite loop case detected in support ticket email integration
DescriptionI found an infinite loop case that should be checked out.

Let's assume that I have support ticket email integration enabled at support@lovinity.org . Let's also assume I do not have an email set in my profile as administrator. Here's what can happen:

*In certain situations, such as newsletter emailing, since I don't have a set email address in my profile, the site may email support@lovinity.org if site configuration causes it to (I think setting staff email to it does).

*Since I do not have an email address set on my account, and since support@lovinity.org is the support ticket email, what happens is an email gets sent to support@lovinity.org . Composr doesn't recognize the from address of support@lovinity.org associated with any account, and therefore emails support@lovinity.org to inform about that. However, this then causes a chain reaction of emailing support@lovinity.org every time cron executes to check for new emails for support tickets.
TagsNo tags attached.
Time estimation (hours)
Sponsorship open

Activities

Chris Graham

2016-04-10 18:32

administrator   ~0003555

The support email must be separate from the website address / staff address settings.

I'll document that.

Chris Graham

2016-04-10 18:35

administrator   ~0003556

Actually I'll do that, but I'll also put a block on it considering any email sent from it's own address.

Patrick Schmalstig

2016-04-10 18:49

administrator   ~0003558

Yeah was about to say I'd prefer if I could keep my support email the same and have the staff email the same as the support email. That way, if people try to reply to a notification, the reply-to would be the support email and thus a ticket is created.

Issue History

Date Modified Username Field Change
2016-04-10 06:53 Patrick Schmalstig New Issue
2016-04-10 18:32 Chris Graham Note Added: 0003555
2016-04-10 18:32 Chris Graham Status non-assigned => closed
2016-04-10 18:32 Chris Graham Assigned To => Chris Graham
2016-04-10 18:32 Chris Graham Resolution open => not fixable
2016-04-10 18:35 Chris Graham Note Added: 0003556
2016-04-10 18:35 Chris Graham Status closed => resolved
2016-04-10 18:35 Chris Graham Resolution not fixable => fixed
2016-04-10 18:49 Patrick Schmalstig Note Added: 0003558