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

[MM3-users] Re: Unusual behavior: Standard discussion lists with prefix are sometimes having prefix *dropped*

by Thomas Ward

On 10/19/23 13:41, Mark Sapiro wrote: > On 10/19/23 10:02, Thomas Ward via Mailman-users wrote: >> I noticed some unusual behavior in Mailman3 stable release on PyPI >> and such. Namely, there are instances where replies are being >> processed and the prefix tags are simply being **lost** and dropped >> by Mailman3, instead of being properly prepended where they're >> supposed to go. >> >> Is this a known bug or does it need its own bug in the gitlab tracker? > > > Are you sure you are looking at messages from the list and not > messages received by direct To:, CC: or BCC:? > > I have never seen an issue where list posts would sometimes have the > subject prefix prepended and sometimes not. If you are seeing this, we > would ideally like to see a thread in the hyperkitty archive where > some of the messages have the prefix in the message view and some > don't, or at least see some of the raw Subject: headers. This might be a MUA quirk because we (read: my employer, like my other messages) are using Outlook which we all know does Weirdness. Upon examination of the actual message's source it has the proper subject line with a prefix: > Subject: [Test] Emailing Test But the way this is displayed in Outlook is weird. It may be that Microsoft is seeing the message as CC'd (reply-all was used!) and then stripping prefix, etc. because it realized there was some stupidness or such at the message-id level or something. This is looking more like a MUA issue because my other address which is subscribed and uses Thunderbird to access the mailbox instead sees the headers right with the proper prefix, suggesting this is something specific to Outlook as a MUA. Thomas

1 year, 10 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Sun, Feb 5, 2023 at 8:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/5/23 01:13, Odhiambo Washington wrote: > > > > So in my case, I should at least increase the value of > > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? > > > It probably isn't even set in your case and defaults to 900 if it isn't > set. I have never seen this config option in any of the settings files and so believe that no one has it set - except the DEVs, maybe. > Yes, you can set it to a larger value. If your archive search > engine is woosh and your archive is even moderately large, 1800 probably > isn't nearly enough. Yes, my archive search engine is whoosh. And my archives size is 2.5GB+ For starters I will make it 3600 and observe next time. > There was no indication of timing in your OP, but you should determine > when that cron job started and when the error was > reported. The difference is the absolute minimum you should set > for HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin > to that. > Sadly I deleted the email. I will have to determine those aspects next time. I need to make a request for a small improvement on the documentation at: https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m… The problem I am facing (the subject of this thread is that of a race between the "monthly hyperkitty update_and_clean_index" job and the hourly "hyperkitty update_index job" Would it be possible to add such details to the section, so that it is clear what the corn jobs do and perhaps what can lead to such race conditions (if that's not too much to ask)? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: Mailman 3 stops delivering to a domain after too many bounces

by Tim Cutts

> On 12 Jul 2022, at 16:28, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/12/22 12:34 AM, Julian Kippels wrote: >> Hi, >> We have recently upgraded from Mailman 2 to Mailman 3. Since then I >> have observed many user reports that mails to mailing lists don't reach >> all members. My suspicion is that there are too many "dead" members on >> those lists. This was not a problem on Mailman 2, but has become a >> problem on Mailman 3. It seems to me that for example Mailman 3 sends >> mails to the first 5 existing member addresses from domain A, then >> encounters several (20 or so seems to be the threshold) "dead" member >> addresses from domain A that generate a bounce and then does not even >> attempt to reach the remaining 800 member adresses from domain A and >> only sends to members on domain B and domain C. >> Is there a way to globaly ignore bounces and send out mails to all >> members of a list, no matter what? > > > Mailman's outgoing runner should not be quitting because of bounces at SMTP time. It seems like there may by some issue causing Mailman's outgoing runner to die. What's in Mailman's var/queue/shunt/ and Mailman's var/logs/mailman.log. Good point. Mailman3 needs a great deal more RAM than Mailman2, especially if you’re running the web and core on the same machine. I used to comfortably run my small mailing list server on a 1GB VM, but on Mailman3 I found it often ran out of memory and bits of mailman3 would get shot by the kernel’s OOM killer, and had to move to a larger VM. So I’d check your kernel logs and see if you’ve got OOM messages in there. Tim

3 years, 2 months

[MM3-users] Re: External MTA incoming mail: configuration

by Odhiambo Washington

On Wed, Jul 31, 2024 at 2:35 PM Roland Giesler via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2024/07/30 22:39, Mark Sapiro wrote: > > It appears you have a situation where the MX for the Mailman domains > > is not the Mailman server. You need to configure the MTA on > > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > > You can to this by configuring that MTA to use transport_maps, etc as > > if it were the Mailman server. In order to get Mailman's generated > > files on the other server, you need to create a process to do that. > > When Mailman makes changes by adding or deleting lists or when it is > > started, it updates the postfix_lmtp and postfix_domains files and > > calls a command (normally postmap) to update the corresponding .db > > files. The command can be set by setting `postmap_command` in the > > `[postfix]` section in mailman.cfg. > > > I'm not able to find any documentation about `postmap_command`, not even > in the schema.cfg. If I have to provide method to update the > postfix_lmtp and postfix_domains on another server, then it would have > to something like sftp? mailman changes the files on the mailman server > (in a location I set) and then postmap_command copies those files to the > destination on the MTA server. Is that in principle what needs to be done? > > thanks again! > Read this thread and take a keen look at the solution provided by @Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> : https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- 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, 1 month

[MM3-users] Re: exim4 + mailman3 lmtp failure

by Thomas Drillich

Hello Mark, thank you four your fast response, yes I use the default port 8024 netstat -atp: tcp 0 0 localhost:8024 0.0.0.0:* LISTEN 26555/python >grep MM3_LMTP_PORT /var/lib/exim4/config.autogenerated MM3_LMTP_PORT=8024 lines from exim4/mainlog 2020-05-06 21:48:08.506 [5776] 1jWQ1Y-0001VA-2A <= th(a)drillich.com H=mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 P=esmtps L- X=TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256 CV=no S=7313 M8S=0 DKIM=drillich.com RT=0.146s id=bb5a020a-bcc3-81a2-b5ab-6d89eaf5b28d(a)drillich.com from <th(a)drillich.com> for seebruecke(a)listen.td3.eu 2020-05-06 21:48:08.517 [5776] SMTP connection from mo4-p00-ob.smtp.rzone.de [85.215.255.20]:20961 I=[85.25.8.21]:25 closed by QUIT 2020-05-06 21:48:08.787 [5777] 1jWQ1Y-0001VA-2A ** seebruecke(a)listen.td3.eu F=<th(a)drillich.com> P=<th(a)drillich.com> R=mailman3_router T=mailman3_transport: all hosts for 'listen.td3.eu' have been failing for a long time (and retry time not reached) Am 06.05.20 um 20:55 schrieb Mark Sapiro: > On 5/6/20 10:54 AM, Thomas Drillich wrote: >> Hello, >> >> I tried to setup exim4 + mailman3 but it seems to stuck at lmtp delivery of mailman3. >> Could you give me a hint, to detect the reason of failure ? > ... >> # /etc/exim4/conf.d/transport/55_mm3_transport >> mailman3_transport: >> driver = smtp >> protocol = lmtp >> allow_localhost >> hosts = localhost >> port = MM3_LMTP_PORT >> rcpt_include_affixes = true > Have you defined MM3_LMTP_PORT and is it the same value as the > lmtp_port: setting in the [mta] section of mailman.cfg - default 8024? > > And is Mailman core and particularly its lmtp runner running and is it > listening on the relevant port? > > Is there more information about "all hosts for 'listen.td3.eu' have been > failing for a long time" in exim's logs? > > > _______________________________________________ > 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/ -- mit freundlichem Gruss -- regards Thomas Drillich Heugasse 4 / D-55116 Mainz / Germany fon +49-6131-570-2621 mobil +49-162-469-5875

5 years, 4 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Abhilash Raj

On Mon, Mar 30, 2020, at 5:33 AM, Ralph Seichter wrote: > * Mark Sapiro: > > >> $ grep ^EMAIL settings.py > >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > >> EMAIL_HOST = 'localhost' > >> EMAIL_PORT = 25 > > > > but is this perhaps overridden in a settings_local.py file? > > I don't have a local settings file. I cloned the suite from GitLab[1] > master branch and modified the existing settings.py, based on Mailman's > documentation. > > [1] https://gitlab.com/mailman/mailman-suite.git > > I just verified that EMAIL_BACKEND is not redefined anywhere: > > $ grep -r 'mail\.backends' . > Binary file ./__pycache__/settings.cpython-38.pyc matches > ./settings.py:EMAIL_BACKEND = > 'django.core.mail.backends.smtp.EmailBackend' > ./settings.py:# EMAIL_BACKEND = > 'django.core.mail.backends.filebased.EmailBackend' > > I commented out the "if DEBUG == True" lines, which explains match > number three. As far as I can see, the mail backed definition for Django > is as it should be. > > I could provide the differences between my settings.py and the Git HEAD > version if you think that might help. It definitely would help if you paste the diff of the settings required. Also, can you jump into a django shell and see if you can get any exceptions trying to send emails: $ python manage.py shell >>> from django.core.mail import send_mail >>> send_mail( 'Subject here', 'Here is the message.', 'from(a)example.com', ['to(a)example.com'], fail_silently=False, ) I picked it up from the Django's docs and perhaps fail_silently=False would give some exceptions. Please make sure you tail the logs for any connections. Abhilash > > -Ralph > _______________________________________________ > 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)

5 years, 5 months

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/07/31 13:47, Odhiambo Washington via Mailman-users wrote: > On Wed, Jul 31, 2024 at 2:35 PM Roland Giesler via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> On 2024/07/30 22:39, Mark Sapiro wrote: >>> It appears you have a situation where the MX for the Mailman domains >>> is not the Mailman server. You need to configure the MTA on >>> box2.gtahardware.co.za to relay Mailman's mail to the mailman server. >>> You can to this by configuring that MTA to use transport_maps, etc as >>> if it were the Mailman server. In order to get Mailman's generated >>> files on the other server, you need to create a process to do that. >>> When Mailman makes changes by adding or deleting lists or when it is >>> started, it updates the postfix_lmtp and postfix_domains files and >>> calls a command (normally postmap) to update the corresponding .db >>> files. The command can be set by setting `postmap_command` in the >>> `[postfix]` section in mailman.cfg. >> >> I'm not able to find any documentation about `postmap_command`, not even >> in the schema.cfg. If I have to provide method to update the >> postfix_lmtp and postfix_domains on another server, then it would have >> to something like sftp? mailman changes the files on the mailman server >> (in a location I set) and then postmap_command copies those files to the >> destination on the MTA server. Is that in principle what needs to be done? >> > Read this thread and take a keen look at the solution provided by @Stephen > J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> : > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Excellent! I think I can get the sshfs route working, but the pending database solution is elegant! I love it! Thanks for the pointer.

1 year, 1 month

[MM3-users] Re: SPF check fails for lists subdomain

by Jan Eden

On 2023-01-05 08:55, Jan Eden via Mailman-users wrote: > On 2023-01-04 15:07, Mark Sapiro wrote: > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > Although I could specify the IP address in my SPF records directly (as > > > you suggested), I do hope that my understanding of DNS records laid out > > > above is not entirely misguided. My current setup does work as expected > > > for eden.one, after all. > > > > As I said at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > I was misreading your DNS and now I am as puzzled as you about the failure. > > It gets even more mysterious. I tried sending messages from both > lists.eden.one and janeden.net (my other domain) to a gmail account and > to another mail provider. Both messages passed the SPF checks on both > services (s. the relevant headers quoted below). Now because I send > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > check operates (and succeeds) on e.g. > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > (and not on somethingsomething(a)lists.eden.one or > somethingsomething(a)janeden.net) Could this be the reason for the failed > SPF checks in Yahoo's and Google's DMARC reports? There was never a mystery, just my complete ignorance wrt DMARC and alignment[1]. Changing the DMARC DNS entry for lists.eden.one (more specifically, the aspf tag) solved the issue: <policy_published> <domain>lists.eden.one</domain> <adkim>s</adkim> <aspf>r</aspf> <p>quarantine</p> <sp>quarantine</sp> <pct>75</pct> </policy_published> <record> <row> <source_ip>123.123.123.123</source_ip> <count>1</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>pass</spf> </policy_evaluated> </row> For other domains, I would need to turn off SRS, which is not possible for independent reasons. - Jan [1] https://en.wikipedia.org/wiki/DMARC#Alignment

2 years, 8 months

[Test] Re: What now -reply from web

by Simon Hanna

On 03/21/2016 03:36 AM, Mark Sapiro wrote: > On 03/20/2016 07:22 PM, mailman(a)mailman3.org wrote: >> The last post with SSL = True and latest core still hits the same >> underlying exception both in trying to get the archive URL and in >> trying to archive the message. The core now handles these exceptions >> and continues so the message goes to the list, but isn't archived and >> has no archive headers. >> >> This is a post from hyperkitty which will probably be handled the >> same, so we have to go back to SSL = False until we can fix the >> certificate issue. > > > Yes. > > Bottom line. With USE_SSL = True, core connects to hyperkitty via SSL to > 127.0.0.1 and the certificates I installed don't include 127.0.0.1 in > their domains, so urllib3 or requests (depending on where we're coming > from) throws SSLError: hostname '127.0.0.1' doesn't match either of > 'lists.mailman3.org', 'mirror.list.org', 'mirror.mailman3.org'. > > The core now handles the exceptions and the message is ultimately > delivered but not archived. regardless of where it originated. > > We're back to USE_SSL = False now so this post should be archived, > albeit the archive URLs will have 127.0.0.1 ast the host and not > lists.mailman3.org. IMHO you shouldn't use USE_SSL at all. It just redirects to ssl pages on certain urls in hyperkitty. What you should be doing is having your webserver (nginx, apache, ...) redirect all trafic from http to https. I'm doing this and have the following settings: # django settings USE_SSL = False # Put external IP in this tuple MAILMAN_ARCHIVER_FROM = ('x.x.x.x', '127.0.0.1', '::1') # hyperkitty archiver plugin # this is the url to the base page of hyperkitty # in your case this would be # base_url: https://lists.mailman3.org/archives/ base_url: https://example.com/hyperkitty/ It's working like a charm with no errors at all

9 years, 5 months

[MM3-users] Re: Help request, almost got it going, but ....

by Claus-Justus Heine

I have fixed the bug on forks of mailman-core, postorius and mailman-client. C Am 02.09.2017 um 14:36 schrieb Claus-Justus Heine via Mailman-users: > I think I found the bug; I have posted a comment to the issue mentioned > by Mark > > https://gitlab.com/mailman/postorius/issues/58 > > Regards > > Claus > > Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users: >> Oh well. >> >> Am 01.09.2017 um 23:44 schrieb Mark Sapiro: >>> On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >>>> >>>> Seemingly, at some point in the deep dungeons of the source code the >>>> "Acceptable aliases" Text-Box is not interpreted correctly. >>>> >>>> Specifically, at the start it contains the string >>>> >>>> [] >>> >>> >>> See <https://gitlab.com/mailman/postorius/issues/58>. >> >> there they talk about fancy "uni-code thinks" (email addresses?) where >> the task is to convert a new-line separated text-field into an array. Oops. >> >> Kind thanks anyway. >> >>> >>> In order to set things on this page, you need to clear the Acceptable >>> aliases box before submitting changes. You can't actually set Acceptable >>> aliases via Postorius until this is fixed. >> >> The issue seems not to be overly active. I thought -- coming from >> Mailman v2 -- that the configuration of acceptable submitters to an >> email list (e.g. keep everyone moderated?) would be a central and >> prominent and important configuration issue. Seems not to be a central >> point. Mmmh. >> >> Thanks >> >> Claus >> >> > -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

8 years

Search results for query "sapiro"