*** This bug is a duplicate of bug 265179 ***
https://bugs.launchpad.net/bugs/265179
Hello all!
I don't know if this is the correct post for my problem, but while searching launchpad, the results sent me here. So, here it goes: I am one of the people "responsible", for the "birth and eventual official blessing" of www.ubuntu-pr.org, which is still in its infancy, as a wiki page, for the past 8 years, due to lack of time, experience and interest, to be honest.
I am trying to revive the project, or find someone to hand it to, but I have forgotten the mailing list admin password. I (sonhadorpr[at]gmail) keep getting notices of spam and users wanting to connect, but I can't do anything about it.
How can I reset the password?
There should be a link that allows you to do that, or as mentioned above, some sort of security questions, for these problems.
Thank you for your help!
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/266821
Title:
privacy hole in password reminder
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions
Public bug reported:
Hello,
I installed Mailman 3 and Postorius on CentOS 7, via the packages
available at this repo:
https://repos.fedorapeople.org/repos/abompard/hyperkitty/el-7/x86_64/
I am using the default Postorius configuration. I am running Postorius
using the provided development Django project from bzr. I have
configured a domain that isn't real and a test list. Mailman has access
to an outgoing MTA but the MTA can't send mail back via LMTP, at least
at the moment.
I encountered an error when I attempted to change the test list's
settings for Message Acceptance. When I try to save my change in
settings, for any setting on that page, I get an error.
I was able to successfully change settings on that page (setting
default_member_action to "accept", specifically) by using the Python
REST client. I directly changed the value and ran .save() and everything
looked correct and there were no errors.
This is the error in the Postorius log:
[20/May/2015 19:59:35] "POST
/postorius/lists/testlist.mail.local/settings/message_acceptance
HTTP/1.1" 500 78853
This is the output from mailman.log:
May 20 20:59:35 2015 (12584) 127.0.0.1 - - "PATCH
/3.0/lists/testlist(a)mail.local/config HTTP/1.1" 400 2
Here is the trace output from the error:
*******
Environment:
Request Method: POST
Request URL: http://127.0.0.1:8000/postorius/lists/testlist.mail.local/settings/message_…
Django Version: 1.6.11
Python Version: 2.7.5
Installed Applications:
('django.contrib.auth',
'django.contrib.messages',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.admin',
'django.contrib.staticfiles',
'postorius',
'django_browserid')
Installed Middleware:
('django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware')
Traceback:
File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
112. response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python2.7/site-packages/postorius/auth/decorators.py" in wrapper
58. return fn(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/postorius/views/list.py" in list_settings
787. except HTTPError as e:
Exception Type: UnboundLocalError at /postorius/lists/testlist.mail.local/settings/message_acceptance
Exception Value: local variable 'HTTPError' referenced before assignment
*********
Let me know what other information you need, or how I can help diagnose
this issue.
** Affects: postorius
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to Postorius.
https://bugs.launchpad.net/bugs/1457271
Title:
HTTP 500 error when saving changes to Message Acceptance settings
To manage notifications about this bug go to:
https://bugs.launchpad.net/postorius/+bug/1457271/+subscriptions
Public bug reported:
If VIRTUAL_MAILMAN_LOCAL_DOMAIN is non-empty it should also be appended
to the addresses in the SITE ADDRESSES stanza.
If the site list's host_name attribute is in
POSTFIX_STYLE_VIRTUAL_DOMAINS the site list posting address will be in
both the SITE ADDRESSES stanza an in the list's virtual mapping stanza.
This causes postmap to warn about the duplication.
** Affects: mailman
Importance: Medium
Assignee: Mark Sapiro (msapiro)
Status: In Progress
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1570630
Title:
Some entries in data/virtual-mailman can be duplicates or be missing
VIRTUAL_MAILMAN_LOCAL_DOMAIN
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1570630/+subscriptions
Public bug reported:
A message with a From: address with an '@' in a quoted local part has
been observed. While this is probably bogus, it confuses the DMARC
mitigation code that splits off the domain at the first '@'. The code
should probably split at the first '@' from the right.
** Affects: mailman
Importance: Low
Assignee: Mark Sapiro (msapiro)
Status: In Progress
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1568445
Title:
DMARC mitigation can check an invalid domain if the From: local part
contains a quoted '@'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1568445/+subscriptions
Public bug reported:
In determining if dmarc_moderation_action should be applied, if a sub-
domain of an 'organizational domain' has no _dmarc policy record and the
organizational domain does have a _dmarc record, the policy that should
apply to the sub-domain is the organizational domain's sp= policy if any
and the p= policy if not.
Through Mailman 2.1.21, only the organizational domain's p= policy is
applied even if there is an sp= policy.
** Affects: mailman
Importance: Low
Assignee: Mark Sapiro (msapiro)
Status: In Progress
--
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1568398
Title:
DMARC mitigation can be incorrectly (not) applied for a sub-domain.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1568398/+subscriptions