FYI, I disabled the auto-update feature because it could be exploited. Sender
names are now fixed to the one in the last email sent to a list, the full fix
is more complex and requires a SQL schema change, so it's going to take some
more time.
Thanks for letting me know about this issue.
Auréli
Yeah, that's exactly what's happenning. The sender name is updated when an
email from the same address is sent to the list. It worked well for humans, but
I have to think about this use case.
Aurélien
___
devel mailing list -- devel@lists.fedoraproject
> for some reason in hyperkitty the emails from pagure show up as
> coming from Brian Exelbierd (bex). Anyone know why that is?
They now show up as coming from "Josh Berkus", that's weird indeed. The posting
address is indeed "pag...@pagure.io".
There are several places where the poster's fullnam
On Wed, Jan 18, 2017, at 04:00 PM, Dennis Gilmore wrote:
> El mar, 17-01-2017 a las 22:15 +0100, Brian Exelbierd escribió:
> > On Tue, Jan 17, 2017, at 09:55 PM, Dusty Mabe wrote:
> > >
> > > The atomic working group has configured pagure to send
> > > notifications to
> > > the
> > > cloud mailin
El mar, 17-01-2017 a las 22:15 +0100, Brian Exelbierd escribió:
> On Tue, Jan 17, 2017, at 09:55 PM, Dusty Mabe wrote:
> >
> > The atomic working group has configured pagure to send
> > notifications to
> > the
> > cloud mailing list. These notifications come through as normal
> > emails
> > but f
On Tue, Jan 17, 2017, at 09:55 PM, Dusty Mabe wrote:
>
> The atomic working group has configured pagure to send notifications to
> the
> cloud mailing list. These notifications come through as normal emails
> but for some reason in hyperkitty the emails from pagure show up as
> coming from Brian E
The atomic working group has configured pagure to send notifications to the
cloud mailing list. These notifications come through as normal emails
but for some reason in hyperkitty the emails from pagure show up as
coming from Brian Exelbierd (bex). Anyone know why that is?
You can see that he has
