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

[MM3-users] Re: Apache Conf

by Thomas G

Hi tried both. Same result. xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0" Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > Hi, > > Currently, I use a nginx configuration for mailman. It's work perfectly. > > > > I tried to do the same with Apache, but the statics files are not > > delivered (404). > ... > > <VirtualHost *:80> > > ServerName mailing.ddd.fr > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > <Location /static/> > > Alias "/opt/mailman/static/" > > </Location> > > > > <Location /> > > ProxyPass http://localhost:8000/ > > ProxyPassReverse http://localhost:8000/ > > ProxyPreserveHost On > > </Location> > > </VirtualHost>/ > > > In Apache, location > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > appropriate for resources in the file system. > > Try > > Alias /static/ /opt/mailman/static/ > > not within a location block. > > -- > 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

[MM3-users] Re: Problems with New MM3 Installation

by Mark Sapiro

On 5/11/21 7:46 PM, Jeff wrote: > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > 1) some emails that arrived before I got the archive working are still sitting in: > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a collection of messages in maildir format. This is how the prototype archiver stores messages. This has nothing to do with HyperKitty. It is a separate archiver. If you don't want messages to be stored there, you can disable the prototype archiver for the list by unchecking prototype in Postorius -> Settings -> Archiving -> Active archivers or disable it entirely for the installation by setting ``` [archiver.prototype] enable: no ``` in mailman.cfg > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > /usr/local/mailman3/mm/var/queue/shunt > > What should I do to get these messages processed? Assuming the issues that caused them to be shunted have been fixed, just run the command ``` mailman unshunt ``` > 3) Similar to above, some messages are in: > > /usr/local/mailman3/mm/var/queue/bad > > How can I get these messages processed? First examine the messages with ``` mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> ``` To be sure you want them. Also examine mailman.log for the times they were stored in the `bad` queue. You are looking for 'Skipping and preserving unparseable message: <file>' and/or 'SHUNTING FAILED, preserving original entry: <file> messages and you want to determine which runner preserved the message. There may be a 'whichq' entry in the message's metadata in which case, that's the answer. Once you have determined the queue, you can just move the .psv file from the bad queue to the appropriate queue, renaming it from .psv to .pck in the process. > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? I know little about uwsgi. setting it to `uwsgi://localhost:8000` might work. You could also set it to the base URL that a user would use to access the web UI, e.g. `https://example.com` and that would presumably be proxied to uwsgi. For example, on the server for this list we have ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' ``` which gets proxied to gunicorn, but the idea is the same. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 10:57 PM, Ken Alker wrote: > > I have studied the output, looked at the code lines referenced in the > Traceback, and I can't figure out the problem (I feel like the sad guy > on the side of the street with his hood up staring into the engine bay > with stream pouring out and not knowing what to do next). I did some > analyses on the log file and determined that there are 71 messages it is > having problems processing and there are 71 messages "stuck" in > /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to > process each message about 20 times). Each time there is a new post, it retries all the messages in the spool/ directory. > Since upgrading to V3.3.8 I've > not seen new messages get stuck like this (although it's only been > running smoothly for 24 hours now and there hasn't been much activity). > But I'm suspecting there was something awry between the conversion from > V2 to V3 in February and me installing V3.3.8 that caused this (based on > message time stamps). It is HIGHLY likely these messages are in the > archiving spool as a result of me unshunting the shunt queue and that > they are copies of the messages that got delivered to the subscribers > when I did that... but are now hung up in the archiving process. Are new messages being archived OK. If so, that is a real mystery. It says mailman-hyperkitty can talk to hyperkitty and archive new messages, but it can't talk to hyperkitty when attempting to process a queued message. > Following is an excerpt from mailman.log. Note that the "first section" > (from DOCTYPE at top to 404 at bottom) is repeated four times (maybe not > identical; but similar) (so I did not include it to save room) before > the Traceback appears. > > Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list > found > Jun 25 00:13:04 2023 (386086) ACCEPT: > <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > Jun 25 00:13:04 2023 (386090) HyperKitty failure on > https://lists.netlojix.com/hyperkitty/api/mailman/urls: I just went to that URL and got a 404. This is a serious problem. https://lists.netlojix.com/hyperkitty/api/ also returns a 404. It should return some documentation of the API. https://lists.netlojix.com/archives/api/ does work and returns the expected information. Your urls.py file probably contains in its urlpatterns list ``` re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), ``` The simplest fix is to add ``` re_path(r'^postorius/', include('postorius.urls')), re_path(r'^hyperkitty/', include('hyperkitty.urls')), ``` to that list. Another way to fix this is in your mailman-hyperkitty.cfg, you have ``` base_url: https://lists.netlojix.com/hyperkitty ``` Change that to ``` base_url: https://lists.netlojix.com/archives ``` but it wouldn't hurt to add the `^postorius/` and `^hyperkitty/` patterns to urls.py anyway. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Gelpi Andrea

Il 08/05/20 17:13, Mark Sapiro ha scritto: > On 5/8/20 8:06 AM, Seth Seeger wrote: >> On May 8, 2020, at 10:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> You have to edit the display name for the domain in the Django web admin >>> Sites section. >> >> Huh. I had it properly set for the domain that is active, but it wasn’t taking affect. I changed it for the (old) test site, and it changed it. So the name that is showing doesn’t match the domain name that I was changing it for. > > > It should show the display name corresponding to the domain name that > matches the domain in the URL that you go to. If this doesn't seem > correct, perhaps there is some issue with the way you are proxying in > your web server. > Also in debian there is the some problem. The domain name is that of the installation site (example.com) and does not change if you change the webserver and the domian. It seems to be static. You can change it changing the site name in django admin console, but it doesn't change if you change the webserver name. Which file does provide it? Thanks -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 5 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Tue, Dec 27, 2022 at 1:58 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/26/22 11:08, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > El 26/12/22 a las 19:19, Mark Sapiro escribió: > >> On 12/26/22 07:42, Odhiambo Washington wrote: > >> > >>> Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> > >>> > >>> Does your https://site.name/user-profile/ work? > >> > >> Again, Guillermo is using uWSGI, not Apache mod_wsgi > > > > Well... now I am not sure, you know I've been confused before about that. > > > I was looking at what you posted at > https://forums.freebsd.org/threads/mailman-3.61050/#post-488128. I > focused on the part beginning with > > - initiated the uwsgi with a > /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & > [snip] Based on the above you ARE using Apache mod_wsgi and if you are still > also running uwsgi as > > /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & > > that is unnecessary. > Aha. This is interesting. I have been running the same, although via supervisord, thinking that it is necessary. So, this was a confusion! And it looks pretty easy to confuse mod_wsgi with uwsgi when dealing with the ever-evolving monster that most of us have been facing in MM3 over the years :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: using SSH/TLS with external MTA

by Odhiambo Washington

On Sat, Jul 27, 2024 at 11:02 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/24 01:32, Roland Giesler via Mailman-users wrote: > > On 2024/07/25 20:50, Mark Sapiro wrote: > >> > >> It is the mail server at box2.gtahardware.co.za that is refusing to > >> relay this message. I think this issue needs to be resolved in that > >> MTA's configuration. > > > > Indeed that is so, but that box is in daily use by a few different users > > and they authenticate and send email without any problems. I'm checking > > out the link you shared in my other thread now. > > Since I think you said the MTA at box2.gtahardware.co.za is Postfix, you > probably need to add the IP of the Mailman server to mynetworks in > Postfix main.cf on box2.gtahardware.co.za. > ASMTP works on the premise of "we can relay mail for you if we can authenticate you with certain credentials" Adding the IP to "hosts we can relay mail for" negates the need to authenticate, IMHO. So I am still waiting for how MM3 does ASMTP. Does it? -- 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, 3 months

[MM3-users] Re: How to Unshunt Specific Message ?

by Shashikanth Komandoor

Hahahaha. Looks like a work around. I understood "moving out of the shunt queue" means "Moving the files from /var/lib/mailman/mailman/var/shunt directory to any other directory say /opt/...." in my environment. Because I installed mailman software inside /var/lib/mailman only. Please correct me if I am wrong. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Aug 11, 2020 at 8:49 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/11/20 1:46 AM, Shashikanth Komandoor wrote: > > > > I learnt how to unshunt the messages that got unshunted in > > mailman 3. But the command *mailman unshunt* would unshunt all the > messages > > in the shunt queue. > > > > I want only a specific message to be unshunted and resent. I > > don't find my requirement reached with the help of *mailman unshunt*. > > > You need to move all the unwanted messages out of the shunt queue before > running unshunt. > > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 2 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Stephen J. Turnbull

Hi, Mark, Dan I'm no database expert, but is it possible that there's some index that's missing? (Just a WAG, feel free to ignore if you know more about databases than "adding indicies solves all problems" ;-) Mark Sapiro writes: > On 11/16/22 15:52, Dan Caballero wrote: > > Thanks Mark! > > > > We're using GNU Mailman 3.3.5 (Tom Sawyer). The tests I did via the Docker container used a database dump from our production MySQL server. > > > > We have 2050 lists. The address table in the database has 95028 rows. > > > For what it's worth, mail.python.org has 188 Mailman 3 lists and 85852 > rows in the address table, and handling a message waiting moderation > takes only a second or two. Thus, whatever the scaling issue is, it's > likely related to the number of lists as opposed to the number of list > members. > > -- > 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 turnbull.stephen.fw(a)u.tsukuba.ac.jp > >

2 years, 11 months

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/4/23 11:45, Joel Lord wrote: > So I seem to have problems with both periodic AND size-triggered > digests. Size first, this is simpler. Just got one sent out, clearly > triggered by a new email getting added to the queued up messages, but > the setting for the list is the default 30KB and the digest came out at > 23.2 KB. Is it measuring the accumulated queue as size on disk > including metadata and filesystem block sizes or something, rather than > the size of what the emailed digest will be? The threshold is determined by the size in bytes of the MMDF format mailbox file in which the the messages for the digest are saved. This does not include metadata and is not affected by block sizes. It contains the raw messages with all headers and 8 bytes of message separators per message and a 'From ' line per message. Once the digest is triggered, the messages are configured into a digest message with boilerplate, a TOC and possibly a header and/or footer added. The messages themselves may be added as separate MIME message/rfc822 parts to a mime format digest or added as text to a plain format digest. Many headers are removed as the messages are added. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for what is kept. In addition any non text/plain parts in the message are not included in the plain format digest, but are replaced by notes that they have been removed. All this says that a MIME format may be larger or smaller than the threshold depending on the size of the removed headers vs. the added parts, and a plain text digest will probably be smaller if the messages have non text/plain parts, e.g. if content filtering doesn't collapse alternatives and leaves the text/html alternative part, this part will not be in a plain format digest. > Periodic is much more complicated, even to explain. I have the cron job > running nightly at 11:00 PM and it certainly seems to be working, except > for one really odd thing. The list also definitely has periodic digests > enabled in the web UI. This is a very bursty list, so it will go mad > with traffic for a few weeks and then will go mostly idle for a month or > so. The first digest of a burst is definitely size-triggered, but > pretty reliably it has the last few messages from the previous burst in > there. So the one I got today had three messages from today and one > message from May 4th. But that May 4th message should have gone out at > 11:00 PM on May 4th with the daily digest and then gotten flushed from > the pending digest queue, right? That's correct. Do you ever get periodic digests sent at 11:00 PM? If not, there is some issue either with configuration or something. If you get them sometimes, I don't know what could be wrong. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

I created a new list with this setting. This new created list can send to Gmail addresses, this is very strange, because I have changed the problem list (The list that cannot send to @gmail addresses) settings to match the new one, but still the issue is there. The only difference is that the problem list has been imported from mailman2. Question: is there a command line that displays all the settings of a list? I think it might be some hidden settings that are not visible in the UI? Thanks Mohsen ________________________________ From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Wednesday, September 6, 2023 1:32 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Re: Issues with @gmail.com addresses Thank you Mark for your response as always! I checked the lists having the issue of sending emails to @gmail.com subscribers. They had already these settings (so no changes): DMARC Mitigate unconditionally : yes DMARC mitigation action: Replace From: with list address DMARC rejection notice: empty DMARC wrapped message text: empty I wonder three points: * What would be the next action to fix the issue? * This issue started around the beginning of August. Could it be due to some changes google made recently? * Give the number of Gmail users, this should annoy a bigger community, are you seeing that many upset people? Thanks, Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, September 5, 2023 4:17 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- 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…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 1 month

Search results for query "sapiro"