Your message dated Fri, 22 Feb 2019 22:04:52 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-mailman-hackers] Bug#919970: mailman3: Creating
template causes mail to stop sending mail
has caused the Debian Bug report #919970,
regarding mailman3: Creating template causes mail to stop sending mail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
919970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919970
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mailman3
Version: 3.2.0-4
Severity: important
Hello.
When creating custom templates for mailing list from webapps. The
mailman3 stop distributing mails. Steps to reproduce.
After creating mailing lists.
1. Go to particular list profile by clicking from the landing page
(assuming /postorius/lists/) .
2. Find the templates section and create a new template. ( I created
footer for non-digest regular message )
3. After saving template start sending mail to the list and see the logs.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mailman3 depends on:
pn dbconfig-sqlite3 | dbconfig-pgsql | dbconfig-mysql | dbconfig-n <none>
ii debconf [debconf-2.0] 1.5.69
ii logrotate
3.14.0-4
ii lsb-base
9.20170808
ii python3 3.6.6-1
pn python3-aiosmtpd <none>
pn python3-alembic <none>
pn python3-click <none>
pn python3-dnspython <none>
pn python3-falcon <none>
pn python3-flufl.bounce <none>
pn python3-flufl.i18n <none>
pn python3-flufl.lock <none>
pn python3-lazr.config <none>
pn python3-passlib <none>
pn python3-psycopg2 | python3-pymysql <none>
pn python3-public <none>
ii python3-requests
2.18.4-2
pn python3-sqlalchemy <none>
pn python3-zope.component <none>
pn python3-zope.configuration <none>
pn python3-zope.event <none>
pn python3-zope.interface <none>
ii ucf 3.0038
Versions of packages mailman3 recommends:
ii exim4-daemon-light [mail-transport-agent] 4.91-7
Versions of packages mailman3 suggests:
ii chromium [www-browser] 69.0.3497.92-1
ii firefox-esr [www-browser] 60.3.0esr-1
pn mailman3-doc <none>
pn postgresql | default-mysql-server | virtual-mysql-server <none>
ii w3m [www-browser] 0.5.3-36+b1
--- End Message ---
--- Begin Message ---
Jonas Meurer:
> Hi Abhijith,
>
> Abhijith PA:
>> On Monday 28 January 2019 04:53 AM, Jonas Meurer wrote:
>>> a log would be very helpful.
>>>
>>> I tried to reproduce your bug recently, but failed to do so. For me, the
>>> template feature in postorius works as expected. Several lists on the
>>> list server in question have custom footer templates configured through
>>> postorius and they're included in the list mails as expected.
>>>
>>> Is this a new mailman3 setup or did you upgrade it from Mailman 3.1 to
>>> 3.2 recently? On one instance I discovered some leftover cruft in
>>> templates 'file_cache' and 'templates' of the mailman3web database after
>>> upgrading which indeed broke one particular list. After manually
>>> removing the cruft from the database, the list worked as expected again.
>>> Maybe that helps?
>>
>> Yes, I recently updated from mailman 3.1 to 3.2.
>
> Interesting. Did you use the template feature in postorius before?
>
>> In my mailman3 db.I found table 'file_cache' and postorius_emailtemplate
>> (mailman3web db) empty.
>>
>> Please confirm these were the db you meant.
>
> I meant tables `file_cache` and `template` in database `mailman3`.
> Please do the following:
>
> * remove all custom templates from your mailinglists
> * make sure that all these tables are empty
> * try again to add a template to a mailinglist and see whether it works
>
> Also, *please* provide the log output in case anything failed.
Closing this bugreport after we didn't get further information. Feel
free to reopen and provide the requested information if you still
encounter this problem.
Cheers
jonas
signature.asc
Description: OpenPGP digital signature
--- End Message ---
