Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Random characters in "The results of your email commands" e-mail

by Jeffrey D

Mark Sapiro wrote: > To understand what's going on, We would like to see the complete, raw > response message. Also, the headers of the message sent to the -request > address, in particular the Content-Type: header of the first text/plain > part and its charset param. I didn't check the source headers... Mailman isn't the issue, my mail client (Evolution) is the problem. Messages sent to the -request@ with Subject: help and message body with my mail signature are working fine. I received the expected response from Mailman. Messages sent to the -request@ with Subject: help and empty message body, gives the random characters response. Instead of leaving the body empty, Evolution paste "Cgo=" into the message body. Mailman reply with the expected "No such command: cg0k" and Evolution couldn't decode the message. Long story short, don't use Evolution ;-) Thanks for pointing me in the right direction! Mail headers: Sent message -request@ (with empty body) ===================================== Message-ID: <eaa8bc6bec172bf3e19700959d6f86f637a3d59c.camel(a)domain.tld> Subject: help From: Jeffrey <jeffrey(a)domain.tld> To: test-jeffrey-request(a)domain.tld Date: Mon, 17 Feb 2020 10:54:13 +0100 Content-Type: text/plain User-Agent: Evolution 3.34.1-3 MIME-Version: 1.0 Content-Transfer-Encoding: base64 X-Evolution-Identity: 1f54715bb67ff0bd5b87ec47786956d762aec607 X-Evolution-Fcc: folder://f23e08ef4c9736554f0b631ce301539d32916444/Sent X-Evolution-Transport: 6fd443d2352de0b9c1126fe4334605581b1903c2 X-Evolution-Source: Cgo= Response message ===================================== Subject: The results of your email commands From: test-jeffrey-bounces(a)domain.tld To: jeffrey(a)domain.tld Content-Transfer-Encoding: base64 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <158193325438.30764.17876047045035004661(a)domain.tld> Date: Mon, 17 Feb 2020 10:54:14 +0100 Precedence: bulk X-Mailman-Version: 3.2.1 X-Evolution-Source: f23e08ef4c9736554f0b631ce301539d32916444 The results of your email command are provided below. - Original message details: From: Jeffrey <jeffrey(a)domain.tld> Subject: help Date: Mon, 17 Feb 2020 10:54:13 +0100 Message-ID: <eaa8bc6bec172bf3e19700959d6f86f637a3d59c.camel(a)domain.tld> - Results: confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end'. subscribe - An alias for 'join'. unsubscribe - An alias for 'leave'. No such command: cg0k - Done.

6 years, 1 month

[MM3-users] Re: add custom styles to postorius list creation menu

by mhazan＠mandint.org

Le 2022-05-02 17:32, Mark Sapiro a écrit : > On 5/2/22 06:39, Michael Hazan wrote: >> Hello, >> >> When creating a list via postorius, i can see 3 style appear >> (announce, discussion, private). Is it possible to either create a new >> style and add it to that list or modify one of those style ? > > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Thanks i will look into setting up that plugin, hopefully an easier way to do that can make it's way to the default install. >> Also, coming from mailman2, you could directly set the members post >> moderation action when subscribing, now you can only do it via the >> user menu, is there a way to automate this in mm3 ? > > > I don't understand what you mean here. In MM 2.1 a member had only one > setting - moderated yes or no and if moderated there was a list > setting for the moderation action. There was also a list setting for > whether new members were moderated by default. How were you setting > the new member's moderation when subscribing? > > You are correct that when subscribing a new member, the member gets > the default action for members and different action has to be set in a > separate operation. I don't think this is significantly different from > MM 2.1. Also, can you describe what you mean by "automate this". in MM2.1, if you set the list to moderated and default action to hold posting, you can set a some member to be un-moderated (mod bit off) to automatically allow their posting. In the web interface of MM2.1 there is a checkbox with moderated bit on/off on the member list itself, in the postorius interface for MM3 you have to open each members settings page to access that. For automation, as list owner, upon registering a member (via mass subscription) the possibility to change that ? also the me too/dupe setting for example. Thanks

3 years, 10 months

[MM3-users] Re: hyperkitty failed to create a thread

by Abhilash Raj

On Mon, Feb 11, 2019, at 2:08 PM, Marvin Gülker wrote: > Hi, > > Am 11. Februar 2019 um 13:20 Uhr -0800 schrieb Mark Sapiro: > > I downloaded the February mbox from > > <https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/export/wlug@l…> > > and imported it to a test list with 'django-admin hyperkitty_import and > > see the same issue. > > Here's the Hyperkitty Mbox for my affected mailinglist: > <https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch…> > > Maildir from my local machine as received from Mailman via e-mail: > <https://files.guelker.eu/misc/tsc-devel.tar.gz> > > > Examination of the mbox shows for the first message [...] > > Note the folding of the header and the double angle brackets. > > I can confirm that I see this behaviour for my affected mailinglist as > well. The Message-ID header is broken over two lines with double angle > brackets in the Hyperkitty MBox linked above: > > Message-ID: < > <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org>> > > However, the original message as it was delivered by Mailman to me does > not have such a weird message-id header: > > Message-ID: > <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org> > > In this message, the header is broken exactly as shown above after the > colon of "Message-ID:". Maybe some problem with parsing long Message-ID > headers, or ones folded over multiple lines? > > With regard to bug reporting on gitlab.com: I already have accounts on a > ton of sites, and at some point I'd actually like to stop creating new > ones all the time... I created an issue on Gitlab for this with this thread: https://gitlab.com/mailman/hyperkitty/issues/216 > > Marvin > > -- > Blog: https://mg.guelker.eu > PGP/GPG ID: F1D8799FBCC8BC4F > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 1 month

[MM3-users] Re: Importing Mailman 2 Lists apart from Django

by Brian Carpenter

On 4/30/20 11:59 AM, Mark Sapiro wrote: > On 4/30/20 7:59 AM, Brian Carpenter wrote: >> Hello Mailman Users, >> >> Are there instructions on importing a Mailman 2 list into a Mailman 3 >> core installation only? Does the import21 script not need >> Django/Postorius/Hyperkitty? > > import21 requires only Mailman core. > > >> It seems Django is required to import archives I guess because of the >> use of Hyperkitty. How about importing archives without having a Django >> installation? Is that what the prototype archiver for? > > The only current archive import we support is `django-admin > hyperkitty_import` which imports archive .mbox files into HyperKitty. > > The prototype archiver is just a maildir format collection of messages. > > Converting an mbox file to a maildir is trivial. > > from mailbox import Maildir, mbox > mb = mbox('/path/to/mbox', create=False) > md = Maildir('/path/to/maildir', create=True) > for msg in mb: > md.add(msg) > > >> We are getting ready to start working on a custom forum application for >> Mailman 3 (called Empathy) and I am would like to import some mailman 2 >> archives into the development server to work with. > > First you have to decide how Empathy will store messages. Look at > <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/management/c…>. > This is how HyperKitty gets messages from a mbox and adds them to its > database. It's actually fairly simple - a lot of the code is handling > exceptions due to defective messages. > > Presumably Empathy will have a method for adding a message to the > archive, so importing is just getting messages from the mbox and using > Empathy's method to add it. > Thank you Mark. Your response was very helpful. This should help my developer make some decisions. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 11 months

[MM3-users] Re: Archive download - unexpected end of file

by Mark

>> On 3/1/25 13:58, Mark wrote: >> >> I have a MM3 list to whose archive I recently added an mbox file of >> older emails. >> >> Viewing/searching the archive (Hyperkitty) is working fine. >> >> Downloading archives "for the month" or "last 30 days" delivers the >> expected ".mbox.gz" file and those are fine. >> >> However, when I download the "Entire archive" and attempt to gunzip >> that ".mbox.gz" file I get the error: " ... unexpected end of file". ?On 2025-03-01 23:04, Mark Sapiro wrote: > > The process creating the zip for download times out. You can increase > the timeout. If your wsgi server is Gunicorn, see > https://docs.gunicorn.org/en/stable/settings.html#timeout - for uwsgi > see > https://uwsgi-docs-additions.readthedocs.io/en/latest/Options.html#harakiri > > However, it's probably easier to get it in pieces. You can prpbably > get chunks bigger than a month. Look at the URL for a month, e.g. for > Jun, 2005 it will be something like > > https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2025-02.mbox.gz?start=2025-01-01&end=2025-02-01 > > The <fqdn-listname>-2025-02.mbox.gz can be any arbitrary file name. > The start and end parameters determine what's included. E.g. for all > of 2024 > > https://www.example.com/archives/list/<fqdn-listname>/export/<fqdn-listname>-2024.mbox.gz?start=2024-01-01&end=2025-01-01 > > Note that the end date is the first date not included, i.e. the day > after the last date included. Thank you very much Mark, for your detailed advice. Increasing the timeout from the default of 30 seconds to 360 now sees the entire archive downloading successfully. # /etc/mailman3/gunicorn.conf # bind = ['127.0.0.1:8000'] proc_name = "mailman-web" chdir = "/opt/mailman/mm" pidfile = "/opt/mailman/mm/var/gunicorn.pid" accesslog = "/opt/mailman/mm/var/logs/access.log" errorlog = "/opt/mailman/mm/var/logs/error.log" #Added 2025-03-02 to resolve timeout on download full archive. timeout = 360 $ systemctl daemon-reload $ systemctl restart mailman3 $ systemctl restart mailmanweb $ pstree ├─gunicorn───gunicorn ├─mailman-web───mailman-web─┬─mailman-web │ └─3*[mailman-web───{mailman-web}]

1 year

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Odhiambo Washington

On Sun, May 7, 2023 at 8:52 PM Volkmar Grote <volkmar(a)grote-family.com> wrote: > Hi Mark, > > On 07.05.23 01:31, Mark Sapiro wrote: > > On 5/6/23 16:02, volkmar(a)grote-family.com wrote: > >> > >> My urls.py: > >>> (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py > >>> from django.contrib import admin > >>> from django.urls import include, reverse_lazy, re_path > >>> from django.views.generic import RedirectView > >>> > >>> urlpatterns = [ > >>> re_path(r'^$', RedirectView.as_view( > >>> url=reverse_lazy('list_index'), > >>> permanent=True)), > >>> re_path(r'^postorius/', include('postorius.urls')), > >>> re_path(r'^hyperkitty/', include('hyperkitty.urls')), > >>> re_path(r'', include('django_mailman3.urls')), > >>> re_path(r'^accounts/', include('allauth.urls')), > >>> # Django admin > >>> re_path(r'^admin/', admin.site.urls), > >>> ] > > > > > > We and the various docs are inconsistent about 'postorius' vs > > 'mailman3' and 'hyperkitty' vs 'archives' in urls. Add these > > > > re_path(r'^mailman3/', include('postorius.urls')), > > re_path(r'^archives/', include('hyperkitty.urls')), > > > > to your urlpatterns list in urls.py to cover both variants. > > > thanks for the quick reply. > I am one step closer to a solution, > "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. > I get the functionality, but it looks ugly w/o any graphics, for which I > get yet another, slightly similar, error message: > > > > > > Page not found (404) > You can run: '/opt/mailman/mm/bin/django-admin clear_cache' as the mailman user. After that you can also restart Nginx, then test again and see if everything works. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 10 months

[MM3-users] Re: Installation Questions [Installation}

by Odhiambo Washington

On Mon, Nov 4, 2024 at 10:34 AM Gerald Vogt <vogt(a)spamcop.net> wrote: > Hi, > > On 04.11.24 02:06, Mark Sapiro wrote: > > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > > We should probably cover this in the docs, but for /etc/mailman3, you > > should do > > ``` > > sudo mkdir /etc/mailman3 > > sudo chown mailman:mailman /etc/mailman3 > > sudo chmod 755 /etc/mailman3 > > ``` > > Then you can create all the subordinate files as the mailman user. For > > other things like the systemd service and the postfix and web server > > configs, you need to do them as root (via sudo). > > is it really necessary that the mailman user can write that directory? > For most services, directories and files in /etc/ may be readable for > the service but usually not writable as you don't want the service > itself change it's core configuration. > > On your server it looks like this: > > # ls -la /etc/mailman3 > total 28 > drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . > drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. > -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf > -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg > -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg > -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py > > and it works just fine. > True, but making the mailman user own the files makes life easier when you operate from the virtualenv - you do not have to exit the virtualenv to edit the files in /etc/mailman3, and then re-enter the virtualenv. You do not have to give the mailman user sudoer rights. That's the whole point about the below: ``` sudo mkdir /etc/mailman3 sudo chown mailman:mailman /etc/mailman3 sudo chmod 755 /etc/mailman3 ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

[MM3-users] Bounce of HCL Notes invitations - CloseBoundaryNotFoundDefect() - 501 Message has defects (in reply to end of DATA command)

by Stephen J. Turnbull

Ulf R. writes: > >>> msg.defects > [CloseBoundaryNotFoundDefect()] This means that the message declares a MIME multipart Content-Type, and some part had a "start" boundary line but no "end" boundary line. > Is there a quick fix for this available? No. If the sending software isn't quite broken, this defect means that a chunk of the message was lost somewhere. Ignoring this kind of defect is obviously a bad idea, and any other fix (on the Mailman side) requires knowing precisely what's causing the defect to be detected. > Is it a problem of the python code or the format of the HCL Notes > Server? Nothing's impossible, but I would bet that the problem is in the HCL Notes format. The MIME multipart spec goes back to the early 1980s, and I'm sure the Python Email package implements it exactly by default. I can't say more without the exact MIME structure of a message that causes this error, preferably the whole message (header and body). That said, it might be something that (a) can be worked around with a slightly more lenient existing email policy, or (b) that we could create a new policy that ignores the problem. > In the .eml file I see 25 header fields calles "X-Notes-Item". May > be it is an overflow? Extremely unlikely. All header fields have been successfully processed by the time a CloseBoundaryNotFoundDefect can be detected, and the copy of the field you provide in your followup email is well-formed and contains no interesting content (such as non-ASCII characters, even after decoding the MIME-words). I cannot say why removing the first instance of the field would resolve the error without seeing the whole message. > Any ideas? Not without the full message. If you're not comfortable sending the message to the list, but do trust us enough, you can send a message that causes the error to me and/or Mark Sapiro <mark(a)msapiro.net>. Regards, Steve

1 year

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote: > > > > > On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > > > On Sat, 13 Mar 2021 14:46:55 -0500, > > Mark Sapiro wrote: > >> > >> On 3/13/21 11:14 AM, John Covici wrote: > >>> > >>> Now one thing came up while trying to create the database, I got a > >>> traceback complaining about a revision error because gentoo had a > >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I > >>> upgrade mailman, am I going to have to do something to the database as > >>> well and why should the database have some kind of reference to the > >>> mailman version? > >> > >> > >> I don't know why this is an issue. You shouldn't need to do anything > >> with the database when you upgrade. Please post the full traceback and > >> error message. > > > > Sorry I can't reproduce it, after dropping and recreating the database > > the error went away, but it was in alembic and it was talking about an > > invalid revision and gave a long hex string. > > > > > My guess is that you updated the database (perhaps, by invoking the mailman > command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes > up and sees a new revision for the database migration added from 3.3.3 but > can’t find the same migration in its source (because it is 3.3.2). That is sort of what happened, except in the opposite direction, it was from 3.3.3 to 3.3.2. My question is therefore, do I have to update this alembic_version when I upgrade mailman to a newer version? That is what I was getting at. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Mark Dadgar

On Nov 4, 2021, at 3:05 PM, Andreas Barth <aba(a)ayous.org> wrote: > * Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: >> >> >> --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro >> <mark(a)msapiro.net> wrote: >> >>> On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: >>>> >>>> My conclusion: >>>> I ask you to consider these experiences in an update for the mailman3 >>>> packages in debian bullseye. It would save time, questions and nerves. >>> >>> >>> Issues with Debian packaging should be directed to Debian. >> >> Or as previously discussed, the debian packages should be avoided entirely. > > I strongly disagree with that statement. > > Distribution packages have their own up- and downsides. Of course, how > they are done is to be discussed with the distribution, so: if > something is wrong with a debian package, please follow the > instructions on bugs.debian.org on reporting bugs. > > However, they have the advantage that they're integrated with the > distribution. They have the disadvantage that they're stable for some > time - that is why it's called a stable release. If they have all the > features someone wants, they usually work fine (and my first > mm3-installation was the default debian package). If one looks for > bleeding edge, of course that's not what one can expect from a > distribution package - but that's also a feature. You left out the fact that the distro edition of mailman3 has very poor support because Debian doesn’t know how to do it and the setup is different enough from vanilla that this community has a hard time supporting it as well. You can certainly try to run it, but I’m willing to bet that you’ll regret it. Having tried it myself, I can’t in good conscience recommend it to anyone. The bottom line is that, IMHO, distro works great for fairly mature projects. MM3 isn’t that yet. YMMV, my $0.02, you get what you pay for, etc. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 4 months

Search results for query "sapiro"