Search results for query "sapiro"
- 5650 messages
[MM3-users] Re: Edit archived email? Is it possible?
by Prasanth Nair
Hi Mark,
Many thanks for your help. I have managed to modify some of the messages
after following your instructions.
Kind regards,
Prasanth
On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org>
wrote:
> Hi Mark,
>
> Thank you for your help. Let me try this.
>
> Kind regards,
> Prasanth
>
> On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote:
>
>> On 9/28/21 6:02 AM, Prasanth Nair wrote:
>> > Hello,
>> >
>> > Does anyone know how to edit an archived email in Mailman3? It is
>> possible
>> > in Mailman2 (
>> >
>> https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M…
>> ).
>> > Is there any option similar to this in Mailman3?
>>
>>
>> In some sense the process is the same but possibly even simpler in
>> Mailman 3. You need to modify the underlying data which requires
>> appropriate access to the server.
>>
>> In Mailman 3, the data are in the hyperkitty_email table in Mailman's
>> database. You can get the Message-ID hash from the URL to the archived
>> message, e.g. for the message to which I'm replying, the URL is
>>
>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…
>> and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have
>> access, you can do database queries like
>> ```
>> SELECT subject, content FROM hyperkitty_email WHERE message_id_hash =
>> '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA';
>> ```
>> and
>> ```
>> UPDATE hyperkitty_email SET content = '<new content>' WHERE
>> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA';
>> UPDATE hyperkitty_email SET subject = '<new subject>' WHERE
>> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA';
>> ```
>> If the message has attachments, they are in the hyperkitty_attachment
>> table and can be referenced by `email_id` which is the corresponding
>> `id` from the hyperkitty_email entry.
>>
>> You can also do similar things via `django-admin shell`. E.g.
>> ```
>> $ django-admin shell
>> Python ...
>> (InteractiveConsole)
>> >>> from hyperkitty.models.email import Email
>> >>> x =
>> Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA')
>> >>> print(x[0].content)
>> ```
>> but this requires some knowledge of HyperKitty's models and Django's ORM.
>>
>> --
>> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
>> San Francisco Bay Area, California better use your sense - B. Dylan
>> _______________________________________________
>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>>
>
3 years, 8 months
[MM3-users] Re: Badsignature on uwsgi-error.log
by Helio Loureiro
Hi,
I was wrong. It keeps happening. So the base_url didn't fix the issue.
And the keys are the same in all configurations.
Best Regards,
Helio Loureiro
https://helio.loureiro.eng.br
https://github.com/helioloureiro
https://mastodon.social/@helioloureiro
On Fri, 22 Mar 2024 at 09:37, Helio Loureiro <helio(a)loureiro.eng.br> wrote:
> Hi Mark,
>
> Thanks for your response. I found what the issue was.
>
> I actually misspelled hyperkitty as hyPperkitty on the url.
>
> So the error on mailman-hyperkitty.cfg was:
>
> base_url: http://localhost:8000/hypperkitty/
>
> I moved to:
>
> base_url: http://localhost:8000/hyperkitty/
>
> and it was solved.
>
> Problem was the wrong link was getting a generic page from Django instead
> of error. And it was failing to do the parsing probably, which was taking
> wrongly as key mistake.
> Best Regards,
> Helio Loureiro
> https://helio.loureiro.eng.br
> https://github.com/helioloureiro
> https://mastodon.social/@helioloureiro
>
>
> On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote:
>
>> On 3/20/24 14:25, Helio Loureiro wrote:
>> > Hi,
>> >
>> > I keep receiving a lot of errors like this:
>> >
>> > --- Logging error ---
>> > Traceback (most recent call last):
>> ...
>> >
>> "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py",
>> > line 55, in unsign
>> > raise BadSignature('Signature "%s" does not match' % sig)
>> > django.core.signing.BadSignature: Signature
>> "F6V0Dr_SvBsx5-cY8vcvLXrX8tA"
>> > does not match
>> ...
>> >
>> > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and
>> MAILMAN_ARCHIVE_KEY
>> > on setting.py are the same.
>>
>>
>> Of those three, the api_key on mailman-hypperkitty.cfg and
>> MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django
>> thing and has nothing to do with the others. See
>> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key
>>
>> If you changed it, that's the issue. If you know what it was previously,
>> you could set the previous value in SECRET_KEY_FALLBACKS, see
>> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks
>>
>> --
>> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
>> San Francisco Bay Area, California better use your sense - B. Dylan
>>
>> _______________________________________________
>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>> Archived at:
>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…
>>
>> This message sent to helio(a)loureiro.eng.br
>>
>
1 year, 2 months
[MM3-users] Re: mailman3-web and the django middleware problem
by Thomas Stein
Am 2024-04-26 00:52, schrieb Mark Sapiro:
> On 4/25/24 14:01, Thomas Stein wrote:
>> Am 2024-04-25 22:03, schrieb Mark Sapiro:
>>>
>>> I don't know how things are arranged in the Debian/Ubuntu package,
>>> but you may have a settings.py which at the end does something like
>>> ```
>>> try:
>>> from settings_local import *
>>> except ImportError:
>>> pass
>>> ```
>>> If that is the case, adding the above snippet to the end of
>>> settings_local.py should work.
>>
>> Yes, that's the case. I added the snippet in question to
>> settings_local.py but this leads to another error:
>>
>> File "/usr/share/mailman3-web/settings.py", line 503, in <module>
>> from settings_local import *
>> File "/usr/share/mailman3-web/settings_local.py", line 194, in
>> <module>
>> x = list(MIDDLEWARE)
>> ^^^^^^^^^^
>> NameError: name 'MIDDLEWARE' is not defined
>> dpkg: error processing package mailman3-web (--configure):
>
> Yes. I understand. In your case, MIDDLEWARE is only defined in
> settings.py and not in settings_local.py. As I understand it originally
> you added
> ```
> x = list(MIDDLEWARE)
> x.insert(0, 'allauth.account.middleware.AccountMiddleware')
> MIDDLEWARE = x
> ```
> to settings.py and you say it didn't help. I don't know why that
> wouldn't work as long as there is no setting for MIDDLEWARE in
> settings_local.py and you added that after the MIDDLEWARE setting in
> settings.py.
> When you say it didn't help, do you mean you still get the
>
> django.core.exceptions.ImproperlyConfigured:
> allauth.account.middleware.AccountMiddleware must be added to
> settings.MIDDLEWARE
>
> message or something else? I note that the original post in this thread
> refers to /etc/mailman3/mailman-web.py which is presumably where the
> package ultimately puts the Django settings, and I don't know what
> `dpkg --configure` is doing.
>
> One thing you could try is in settings_local.py, put
> ```
> from settings import MIDDLEWARE
> x = list(MIDDLEWARE)
> x.insert(0, 'allauth.account.middleware.AccountMiddleware')
> MIDDLEWARE = x
> ```
> to work around the NameError.
After that I get:
File "/usr/share/mailman3-web/urls.py", line 20, in <module>
from django.conf.urls import include, url
ImportError: cannot import name 'url' from 'django.conf.urls'
(/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
dpkg: error processing package mailman3-web (--configure):
installed mailman3-web package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
I guess I'll wait for the new package for now.
thanks again! t.
1 year, 1 month
[MM3-users] Re: users, users and users (was Re: Re: Cannot request password reset: "The e-mail address is not assigned to any user account")
by Mark Sapiro
On 1/28/22 00:41, IOhannes m zmölnig wrote:
>
> i'm afraid i still do not fully understand which types of "users" there
> are.
>
>
> afaics, there are three different types:
> - django users
> this is what get's listed under
> <https://lists.mailman3.org/admin/auth/user/>
Correct.
> - mailman accounts
> this is what is created when you visit
> <https://lists.mailman3.org/accounts/signup/>
No. That creates a Django user, not a Mailman user. What you think of as
a Mailman account is actually a Django account.
> - email addresses
> this is what is created when i subscribe to a list *without* having
> an account.
> e.g. via the "Subscribe" button on
> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Mailman core has users and addresses. A user has one or more associated
addresses. When you subscribe to a list without having an account in
that way, or via email to list-join or list-subscribe or by being mass
subscribed by the list admin or by being imported by `mailman import21`,
assuming you are previously unknown, this creates a Mailman user with an
associated address and subscribes the user or address.
Each user has a primary address and zero or more additional linked
addresses. The user can be subscribed to a list as a user in which case,
delivery if any is to the user's primary address, or can be subscribed
as an address.
> afaiu, (multiple) "email addresses" can be associated with a single
> "mailman account" (but this is strictly optional).
Yes, see above.
> if an "email address" is first used to subscribe to a list without a
> mailman account, and later a mailman account is created with that very
> email address, they get automatically associated.
> a single "email address" cannot be associated with more than one
> "mailman accounts".
Based on the above, your "mailman accounts" are actually Django
accounts. With that in mind, the above is correct, but there is no real
link between Mailman users and Django users. When you are logged in to
the web UI you are logged in as a Django user, and Postorius and
HyperKitty know that user's email address and can therefore know if it
is a list member and know what address to subscribe or unsubscribe as
requested.
> i think i got this one right (as it seems pretty straightforward).
>
> what i don't fully grasp yet is the relation between "django users" and
> "mailman accounts".
As I have said, what you are calling a mailman account is a Django user
and not a Mailman user.
> intuitively, i would have thought that they are identical.
They are, but they are not Mailman core users.
> now mark wrote:
> > a Django user, which is distinct from a Mailman user. The users you
> > added via the web API are Mailman users, but in order to access their
> > lists via the web UI they have to `sign up` to create a Django
> > account.
>
> that seems to indicate, that a "django user" is a (strict) superset of a
> "mailman account".
No. A Django user is the same thing as what you call a mailman account.
A Mailman core user is a separate thing entirely.
> you (as admin) can create "mailman accounts" via the web API¹, but they
> are only expanded to "mailman accounts" if you (as user) go through the
> "Sign Up" process.
No. An admin can create Mailman users via the Postorius UI. A Django
superuser can also create Django users through the Django admin UI.
> otoh, if you create an initial "django user" by signing up, you
> automatically create a "mailman account".
Because they are the same thing. When you go to the Sign-up link on a
Postorius or Hyperkitty page you go to
https://example.com/accounts/signup/, and that's Django, not Mailman.
> so are the two distinct concepts that are just associated via some
> common property (e.g. the email address), or is there some intrinsic
> relationship between the two (e.g. parent-child inheritance relationship)?
They are distinct. Django users have email addresses and Mailman users
have email addresses and they can be associated in that way. There is no
other link.
> so my recent experiment (comparing the output of
> <https://lists.example.com/admin/auth/user/> with that of `[u for u in
> getUtility(IUserManager).users]`) indicates that they are indeed
> distinct objects that *can* be associated with each other.
>
> could you please clarify this?
I hope I have.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
3 years, 4 months
[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold
by Gerald Vogt
Hi,
are you sure you are both talking about the same setting?
You wrote initially:
"The list settings have automatically (and appropriately) been set to
hold mails when I go to Settings -> Message Acceptance -> "Default
action to take when a *non-member* posts to the list" -- it says Hold
for moderation"
That's for non-members, not for members. That does not apply to users
which you have mass subscribed. For those there is the "Default action
to take when a member posts to the list". That's the one Mark Sapiro
mentioned.
Regards,
Gerald
On 18.11.24 10:59, mark(a)suburbia.org.au wrote:
> Hi Mark,
>
> Thanks for taking the time to reply.
>
> Mark Sapiro wrote:
>> On 11/16/24 21:41, mark(a)suburbia.org.au wrote:
>
>>> However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is None, but when I posted to the list from the address, it was not held for moderation, and went through.
>>> Am I missing something with the expected functionality?
>>> A member's moderation action of None means use the Default action to take when a member posts to the list. Is that set to Hold for moderation?
>> Actually, it is good practice to set that to Hold for moderation for
>> all lists or at least all those that don't require moderator approval
>> for subscription to prevent a spammer from subscribing and spamming the
>> list. Then, upon approving a member's post you can also set the member's
>> moderation action to default processing and upon discarding a spammers
>> post, you can also set the spammer's moderation action to Discard.
>
> I agree. My point was that the list is set as default to hold for moderation. But, a new user who sends an email to the list, whose Moderation Action is set to "none", was able to email the list without the email being held for moderation. I would have expected based on the threads I quoted, that a user who is added to the list via Mass subscribe, would not be able to send to the list without it being held.
>
> I'm happy to do more testing, provide other information/logs as desired if that would help?
>
> cheers,
> Mark
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…
>
> This message sent to vogt(a)spamcop.net
6 months, 3 weeks
[MM3-users] Re: config.pck from mailman2 has characters that won't import with import21
by Mark Sapiro
On 7/20/24 10:19 PM, Greg Newby wrote:
> Hi. I've set up MM3 in a venv successfully and am importing my legacy lists.
>
> I no longer have a running instance of mailman2, so don't know how I can
> change the offending list settings (i.e., in config.pck).
>
> The problem seems to be a digest footer from the previous incarnation of
> the list (list name is edited below, to protect the innocent):
That's not the issue.
> (venv) mailman@mail:~$ mailman import21 abc(a)lists.abcabcabc.org
> /var/lib/mailman/lists/abc/config.pck
> Unable to convert mailing list attribute: msg_footer with value
> "_______________________________________________
> ${display_name} mailing list -- ${listname}
> To unsubscribe send an email to ${short_listname}-leave@${domain}
> %(web_page_url)slistinfo/%(_internal_name)s"
> Unable to convert mailing list attribute: digest_footer with value
> "_______________________________________________
> ${display_name} mailing list -- ${listname}
> To unsubscribe send an email to ${short_listname}-leave@${domain}
> %(web_page_url)slistinfo/%(_internal_name)s"
The above are non-fatal. The importer just won't make list specific
templates for those. If you need the footers to be different from the
defaults, you will need to create them manually.
> Importing members [------------------------------------] 0%
> Traceback (most recent call last):
> File "/opt/mailman/venv/bin/mailman", line 8, in <module>
> sys.exit(main())
> ^^^^^^
> File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line
> 1157, in __call__
> return self.main(*args, **kwargs)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line
> 1078, in main
> rv = self.invoke(ctx)
> ^^^^^^^^^^^^^^^^
> File
> "/opt/mailman/venv/lib/python3.12/site-packages/mailman/bin/mailman.py",
> line 69, in invoke
> return super().invoke(ctx)
> ^^^^^^^^^^^^^^^^^^^
> File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line
> 1688, in invoke
> return _process_result(sub_ctx.command.invoke(sub_ctx))
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line
> 1434, in invoke
> return ctx.invoke(self.callback, **ctx.params)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line
> 783, in invoke
> return __callback(*args, **kwargs)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File
> "/opt/mailman/venv/lib/python3.12/site-packages/click/decorators.py", line
> 33, in new_func
> return f(get_current_context(), *args, **kwargs)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File
> "/opt/mailman/venv/lib/python3.12/site-packages/mailman/commands/cli_import.py",
> line 89, in import21
> import_config_pck(mlist, config_dict)
> File
> "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py",
> line 578, in import_config_pck
> import_roster(mlist, config_dict, members, MemberRole.member)
> File
> "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py",
> line 625, in import_roster
> _import_roster(mlist, config_dict, iterator, role, action=action)
> File
> "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py",
> line 645, in _import_roster
> if IBanManager(mlist).is_banned(email):
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File
> "/opt/mailman/venv/lib/python3.12/site-packages/mailman/database/transaction.py",
> line 106, in wrapper
> return function(args[0], config.db.store, *args[1:], **kws)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File
> "/opt/mailman/venv/lib/python3.12/site-packages/mailman/model/bans.py",
> line 103, in is_banned
> re.match(ban.email, email, re.IGNORECASE) is not None):
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.12/re/__init__.py", line 167, in match
> return _compile(pattern, flags).match(string)
> ^^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.12/re/__init__.py", line 307, in _compile
> p = _compiler.compile(pattern, flags)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.12/re/_compiler.py", line 745, in compile
> p = _parser.parse(p, flags)
> ^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.12/re/_parser.py", line 979, in parse
> p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.12/re/_parser.py", line 460, in _parse_sub
> itemsappend(_parse(source, state, verbose, nested + 1,
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> File "/usr/lib/python3.12/re/_parser.py", line 690, in _parse
> raise source.error("multiple repeat",
> re.error: multiple repeat at position 11
The list's ban_list has an invalid regexp.
Do the following in Mailman 3's `mailman shell`
```
bin/mailman shell
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
>>> import pickle
>>> from contextlib import ExitStack
>>> from mailman.commands.cli_import import _Mailman, _Bouncer
>>> from mailman.utilities.modules import hacked_sys_modules
>>> with ExitStack() as resources:
... resources.enter_context(hacked_sys_modules('Mailman', _Mailman))
... resources.enter_context(
... hacked_sys_modules('Mailman.Bouncer', _Bouncer))
... with open('/path/to/config.pck', 'rb+') as fp:
... data = pickle.load(fp)
... print(data['ban_list'])
... data['ban_list'] = []
... fp.seek(0)
... pickle.dump(data, fp)
...
>>>
```
This will print the ban_list so you can see it and then save the
config.pck with an empty ban_list. That config.pck will no longer be
usable in Mailman 2.1 because the pickle protocol is too high and the
bounce_info items if any will be corrupted, but it should work with
import21.
Note that all the ExitStack and hacked_sys_modules stuff is only needed
if there is bounce_info in the config.pck, but it doesn't hurt in any case.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
10 months, 2 weeks
[MM3-users] Re: config incoming email in my domain cpanel
by tlhackque
You've said you're working with labbrands.com.
labbrands.com has address 192.185.51.89
mail.labbrands.com has address 192.185.51.89
www.labbrands.com is an alias for labbrands.com.
telnet proves that Exim is running on that IP address. Either you're
running it, or hostgator is redirecting the SMTP ports.
You added:
lists.labbrands.com has address 190.145.27.66
Presumably that's a different machine.
So that now needs an MX record, and a firewall routing. And the SPF
records ... and spam and virus filters, and all the other stuff you need
to setup an independent, public-facing smtp server.
But at least you won't have to relay.
Good luck.
On 03-Aug-17 16:55, Rafael Mora wrote:
> El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (<
> mailman-users(a)mailman3.org>) escribió:
>
>> I think you're confused.
>>
>> You already have mail.labbrands.com set up as the MX record for
>> labbrands.com. And it has an A record with the same address as your
>> webserver.
>>
> I'm working with the hostgator mailserver, we are not running a local
> mailserver.
>
> As suggested I added an A record like this:
> [image: image.png]
>
> Is it correct? is it redirecting to my Ip so I can redirect it to my
> postfix/mm3 server?
>
>
>> So if you're getting e-mail on that domain, there's another e-mail
>> server running on that IP address. You can't have 2 servers on port
>> 25. In that case, as has been noted before, you'll need to setup a
>> relay in that server, not a firewall redirect. Depending on your MTA,
>> you would need to relay to your internal server. And make sure your
>> firewall setup allows your MTA to do this.
>>
>> We can see it's EXIM:
>>
>> telnet mail.labbrands.com 25
>> Trying 192.185.51.89...
>> Connected to mail.labbrands.com (192.185.51.89).
>> Escape character is '^]'.
>> help
>> 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48
>> -0500
>> 220-We do not authorize the use of this system to transport unsolicited,
>> 220 and/or bulk e-mail.
>> 214-Commands supported:
>> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP
>> quit
>> 221 gator4137.hostgator.com closing connection
>> Connection closed by foreign host.
>>
>> Or, consolidate all your e-mail to one server - which is a lot easier to
>> manage unless you have a really big operation. Postfix is probably the
>> right choice, but requires more setup.
>>
>> Although Mailman3 configuration is not well documented (as you've
>> discovered), you may want to get help from someone with more general
>> network and mail experience. You're now into territory that is, as
>> Simon indicated, not Mailman-specific.
>>
>> On 03-Aug-17 16:28, Rafael Mora wrote:
>>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>)
>> escribió:
>>>> On 08/03/2017 01:22 PM, Rafael Mora wrote:
>>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>)
>>>> escribió:
>>>>>> You need to forward port 25 for SMTP mail delivery and if you want the
>>>>>> web UI (Postorius and HyperKitty) accessible from the outside, port 80
>>>>>> for http and/or port 443 for https
>>>>>> <
>>>>>>
>> https://www.iana.org/assignments/service-names-port-numbers/service-names-p…
>>>>>>> .
>>>>> I mean for incoming mail redirected from my hostgator hosting, because
>>>> when
>>>>> I suscribe an email address MM3 sends a confirmation email, so I have
>> to
>>>>> reply to be suscribed to the list.
>>>> As I said, for mail delivery you need to forward port 25 to the Mailman
>>>> server.
>>>>
>>> Ok so I'll redirect in my zentyal firewall the port 25 to my local
>> centos7
>>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark.
>>>
>>>
>>>> --
>>>> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
>>>> San Francisco Bay Area, California better use your sense - B. Dylan
>>>> _______________________________________________
>>>> Mailman-users mailing list
>>>> mailman-users(a)mailman3.org
>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>>>>
>> --
>> This communication may not represent my employer's views,
>> if any, on the matters discussed.
>>
>> _______________________________________________
>> Mailman-users mailing list
>> mailman-users(a)mailman3.org
>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>>
--
This communication may not represent my employer's views,
if any, on the matters discussed.
7 years, 10 months
[MM3-users] django-allauth 0.59.0 (was: django-allauth failures, but only for some users)
by Jered Floyd
FYI, django-allauth 0.59.0 was released on December 12 and incorporates the patches to work properly with Mailman again.
The only other issue is formatting of the login page. As I noted previously, this can be fixed by copying
site-packages/allauth/templates/socialaccount/login.html
to
site-packages/django_mailman3/templates/socialaccount/login.html
and changing the first line from:
{% extends "socialaccount/base_entrance.html" %}
to
{% extends "django_mailman3/profile/base.html" %}
--Jered
----- On Dec 7, 2023, at 9:57 PM, Jered Floyd jered(a)convivian.com wrote:
> You're welcome. Thank you for all your hard work making Mailman 3 happen at all!
>
> I think django_allauth integration is again stable, but for now I'm pinning
> 0.58.2 + this patch. I'll test again once there is another release
> notification, but since I rebuild by container image every 2-3 weeks I am
> getting exhausted by surprises...
>
> --Jered
>
> ----- On Dec 7, 2023, at 7:44 PM, Mark Sapiro mark(a)msapiro.net wrote:
>
>> On 12/7/23 14:33, Jered Floyd wrote:
>>>
>>> FYI, The django-allauth author has proposed fixing both of these with an even
>>> simpler change, which is now upstream and queued for a future release.
>>>
>>> --Jered
>>
>>
>> Thank you again for your work on this. I can confirm that the patch
>> below fixes my issue with
>> https://msapiro.net/accounts/social/connections/ and SITE_ID = 0.
>>
>>
>>> --- a/allauth/socialaccount/adapter.py
>>> +++ b/allauth/socialaccount/adapter.py
>>> @@ -228,7 +228,10 @@ class DefaultSocialAccountAdapter(object):
>>> provider_to_apps = {}
>>>
>>> # First, populate it with the DB backed apps.
>>> - db_apps = SocialApp.objects.on_site(request)
>>> + if request:
>>> + db_apps = SocialApp.objects.on_site(request)
>>> + else:
>>> + db_apps = SocialApp.objects.all()
>>> if provider:
>>> db_apps = db_apps.filter(Q(provider=provider) | Q(provider_id=provider))
>>> if client_id:
>>
>> --
>> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
>> San Francisco Bay Area, California better use your sense - B. Dylan
>>
>> _______________________________________________
>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>> Archived at:
>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…
>>
>> This message sent to jered(a)convivian.com
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
> Archived at:
> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…
>
> This message sent to jered(a)convivian.com
1 year, 5 months
[MM3-users] Re: The message is larger than the 40 KB maximum size
by Mohsen Masoudfar
It seems something is fundamentally wrong with Hyperkitty:
From /var/log/mailman3/mailman.log
---
49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body>
50 <h1>Authorization Required</h1></body></html> (401)
51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body>
52 <h1>Authorization Required</h1></body></html> (401)
53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body>
54 <h1>Authorization Required</h1></body></html> (401)
55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN">
56 <html><head>
57 <title>503 Service Unavailable</title>
58 </head><body>
59 <h1>Service Unavailable</h1>
60 <p>The server is temporarily unable to service your
61 request due to maintenance downtime or capacity
62 problems. Please try again later.</p>
63 <hr>
64 <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address>
65 </body></html>
66 (503)
67 Sep 21 21:49:26 2020 (24918) Exception in the HyperKitty archiver: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
68 <html><head>
69 <title>503 Service Unavailable</title>
70 </head><body>
71 <h1>Service Unavailable</h1>
72 <p>The server is temporarily unable to service your
73 request due to maintenance downtime or capacity
74 problems. Please try again later.</p>
75 <hr>
76 <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address>
77 </body></html>
78 Sep 21 21:49:26 2020 (24918) Traceback (most recent call last):
79 File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message
80 url = self._send_message(mlist, msg)
81 File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message
82 raise ValueError(result.text)
83 ValueError: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
84 <html><head>
85 <title>503 Service Unavailable</title>
86 </head><body>
87 <h1>Service Unavailable</h1>
88 <p>The server is temporarily unable to service your
89 request due to maintenance downtime or capacity
90 problems. Please try again later.</p>
---
Thanks
Mohsen
-----Original Message-----
From: Mohsen Masoudfar <mmasoudf(a)aaas.org>
Sent: Monday, September 21, 2020 12:24 PM
To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org
Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size
[EXTERNAL EMAIL]
Hi Mark,
Thank you Mark and Phil for your help.
It seems I got stuck!
1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0.
After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size"
2- I checked the python files and found this file, where, it seems, the default value is defined:
/usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40
I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email:
The message is being held because: The message is larger than the 40 KB maximum size
3- I totally agree that the most important issue is the fact that the message vanished with the production list.
I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works.
4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/
Thanks
Mohsen
-----Original Message-----
From: Mark Sapiro <mark(a)msapiro.net>
Sent: Friday, September 18, 2020 4:00 PM
To: mailman-users(a)mailman3.org
Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size
[EXTERNAL EMAIL]
On 9/18/20 12:48 PM, Phil Stracchino wrote:
> On 2020-09-18 15:32, Mohsen Masoudfar wrote:
>> Hi,
>>
>> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped.
>
>
> Assuming that this works roughly the same in mm3 as it does in mm2,
> you can set max_message_size in your list configuration. It defaults
> to 40; units are KB.
Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear".
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…
4 years, 8 months
[MM3-users] Re: Scheduled tasks
by Darren Smith
I will take up any problems with the installation with the creator.
However, I was able to find and run some of the scripts this afternoon, and
I'm running some of the longer-running ones tonight while the usage is
lower.
As for bogging down - I mean attempting to click on an email can take a
LONG time to render, and we frequently get 504 gateway timeouts (the calls
to hyperkitty are timing out). I am trying hard to figure out why this is
happening and to try to tune the system. I still suspect that there are
some inefficiencies with how the database is being used, or how the
database is doing things.
I will take a look at qcluster, that was interesting info and hopefully it
can help me out.
Thanks for your response,
-Darren
On Thu, Jun 7, 2018 at 4:16 PM, Mark Sapiro <mark(a)msapiro.net> wrote:
> On 6/7/18 9:59 AM, Darren Smith wrote:
> > All,
> >
> > I am looking more through the documentation of the Mailman Suite here:
> >
> > https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf
> >
> > In section 3.2.5 it talks about the scheduled tasks that need to be run
> to
> > do "specific routine functions" in hyperkitty.
> >
> > I installed through the easy install script found here:
> >
> > https://github.com/iomarmochtar/mailman3_ei/
> >
> > However, I can't find anything in THAT documentation that talks about
> these
> > cron jobs, and in fact the Mailman Suite isn't installed through that
> > script.
>
>
> That is a third party project. If you have issues with it, you should
> take them up with @iomarmochtar.
>
>
> > Can someone point me to any other documentation about the tasks that need
> > to be run on a continual basis?
>
>
> The section 3.2.5 you refer to tells you what needs to be set up in
> cron. For a list of the jobs tat are run, use
>
> django-admin runjobs --list
>
>
> . Our hyperkitty installation seems to be
> > bogging down more and more, and I am hoping that it will be as simple as
> > just running some jobs that haven't been on our radar.
>
>
> what do you mean by 'bogging down'? If you aren't doing so, setting up
> qcluster as in section 3.2.3 may help.
>
> --
> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>
7 years