mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #15763
[Bug 1261231] A change has been merged
Reviewed: https://reviews.mahara.org/2802
Committed: http://gitorious.org/mahara/mahara/commit/db9c79bddf3f5bb8f4909bf09c18d41fd136f5d0
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch: master
commit db9c79bddf3f5bb8f4909bf09c18d41fd136f5d0
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date: Fri Dec 13 15:24:06 2013 +1300
Allow a $cfg->bounceprefix that's not exactly 4 characters
Bug 1261231
Change-Id: I82d8169e41dcca65c214fdfec954086eba8fc6c8
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1261231
Title:
Allow a VERP "bounceprefix" that's not exactly 4 characters
Status in Mahara ePortfolio:
In Progress
Bug description:
Mahara has a VERP system to identify users whose emails are bouncing,
and disable sending to their email address. It uses a
$cfg->bounceprefix setting to generated the VERP address; this is the
part of the email that comes before the VERP stuff.
Currently, it arbitrarily forces this prefix to be exactly 4
characters, but there doesn't appear to be a reason for this, except
that the process_email() function contains a lot of calls to substr()
with hard-coded offsets that assume the prefix is exactly 4
characters.
I want to change this so that the prefix can be any length. The reason
for this, is so I can use "verp+" as the prefix, which in our mail
system will forward them all to the "verp[at]mahara.org" mailbox. And
that will make it very easy for us to configure the IMAP-based bounce
handling system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1261231/+subscriptions
References