[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MediaGoblin Trac email notifications to issue requestors (was: Taili
Re: MediaGoblin Trac email notifications to issue requestors (was: Tailing MediaGoblin's Postfix logs - troubleshooting Trac emails to ticket requestor)
Mon, 06 Apr 2020 22:52:36 +1000
mu4e 1.2.0; emacs 26.3
I've pulled these Trac changes in on the mediagoblin server. Let's wait
and see whether we end up with a new collaboration tool before moving
the repo - for the time being I've created an account on 0xacab.org
Regarding postfix logs, I just tried looking at those while creating and
logging into a new account on Trac. The email comes through, but nothing
at all in the logs. Any ideas?
Looks like I forgot to attach the patch to my email about haproxy, so
I've made a merge request on 0xacab.org. Did that email notification
On Sat, 04 Apr 2020, Simon Fondrie-Teitler wrote:
> Hi Ben,
> Thanks for working on this! I reviewed the patch and (manually) applied
> and pushed it. We should probably move the git repo to somewhere that's
> easier for you to get access. Let me know if you have preferences for
> where that could be.
> I tried to pull on the mediagoblin server but it looks like there are
> local changes in there so I'll let you take care of that.
> In terms of the logs, I would think 'docker-compose logs postfix' would
> give you want you want. If not, you could try:
> docker-compose exec postfix tail -f /var/log/mail.log
> It doesn't look like there's anything in there right now, so testing it
> is hard.
> Ben Sturmfels <address@hidden> writes:
>> Hi Simon,
>> After some messing around with Trac I was able to configure it to email
>> ticket requestors by default. Could you please review and merge the
>> attached patch?
>> If you do know how to tail the mail logs, that would still be handy to
>> On Thu, 02 Apr 2020, Ben Sturmfels wrote:
>>> Hi Simon,
>>> When I create a test user on Trac, then add a new ticket as the test
>>> user and reply to the ticket from my admin user, I'd expect the test
>>> user to get an email, but that doesn't seem to come through.
>>> Before I fiddle too much with Trac settings, I'd like to see what's
>>> hitting Postfix, just to make sure it's not caused by my email spam
>>> filtering. When I run:
>>> /root/docker-compose-venv/bin/docker-compose up --build --force-recreate
>>> --no-deps postfix
>>> I don't seem to get the Postfix logs showing up like I was hoping. Can
>>> you tell me how I can tail mail.log file please?
>> From 759259e6affdd2b40c869746b545dc98accfc134 Mon Sep 17 00:00:00 2001
>> From: Ben Sturmfels <address@hidden>
>> Date: Thu, 2 Apr 2020 14:58:43 +1100
>> Subject: [PATCH] Send Trac email notifications to issue reporters by default.
>> trac/trac/conf/trac.ini | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>> diff --git a/trac/trac/conf/trac.ini b/trac/trac/conf/trac.ini
>> index e171b83..8bfa00c 100644
>> --- a/trac/trac/conf/trac.ini
>> +++ b/trac/trac/conf/trac.ini
>> @@ -3,7 +3,7 @@
>> file = /var/lib/trac/conf/db.ini
>> -account_changes_notify_addresses = address@hidden
>> +account_changes_notify_addresses = address@hidden,address@hidden
>> force_passwd_change = enabled
>> hash_method = HtDigestHashMethod
>> notify_actions = new,change,delete
>> @@ -158,6 +158,10 @@ use_tls = disabled
>> always_notify_cc = CarbonCopySubscriber
>> always_notify_previous_updater = TicketPreviousUpdatersSubscriber
>> always_notify_updater = TicketUpdaterSubscriber
>> +# Reporters should be notified of updates to a ticket. Otherwise they'd
>> need to
>> +# come back and check Trac explicitly, or know to manually configure
>> +# notifications in their preferences.
>> +always_notify_reporter = TicketReporterSubscriber
>> admin =