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

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 28, 2020, at 4:56 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/28/20 4:39 PM, Mark Dadgar wrote: >> >> The patch does not apply cleanly against /usr/lib/python3/dist-packages/hyperkitty/models/email.py >> >> patching file email.py >> patch: **** malformed patch at line 4: import os > > > That probably isn't because of version mismatch. That would give applied > at offset or with fuzz or a reject. malformed patch means the patch file > is not formatted correctly. Here it is again as an attachment. That may > help. That gives a slightly different error: mark@mail:/usr/lib/python3/dist-packages/hyperkitty/models$ sudo patch < /tmp/patch.txt patching file email.py Hunk #1 FAILED at 24. patch: **** malformed patch at line 23: - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: sending messages in response to posts from non-members

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > On 2/26/22 04:26, David Bremner wrote: >> >> I'd like to turn off the "bounce messages" sent by mailman to >> non-members. My reasoning is that most such posts are spammers, and >> often use forged return-paths / From's, so I end of sending steady >> stream of backscatter to amazon.com etc... >> >> Is this configurable (without postorius) somehow? > > What exactly do you want? Do you want to discard without notice any > nonmember posts or do you want to hold them but not send a notice of the > hold to the poster? It was the latter, and your suggestion for existing lists seems to have worked. Thanks, David

3 years, 6 months

[MM3-users] Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Stephen J. Turnbull

Mark Sapiro writes: > You can't have two accounts in Postorius/Django with the same email > address. But why would you want to? There should be no problem with > a single Django user being subscribed to a list with more than one > role. I for one am uncomfortable having the superuser role being used by an ordinary user account, for several reasons. I'm pretty sure that is what Odhiambo was concerned about. I will have similar concerns about the domain user role when we implement it. The preference for a single email address across roles is harder for me to understand. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 4 days

[MM3-users] Re: What is result of planned MM3 integrated installation at Pycon?

by Tom Browder

On Sat, Jun 9, 2018 at 16:48 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/9/18 2:19 PM, Tom Browder wrote: > > I may have missed the announcement, but I thought it was hoped to get a > > major leap toward an integrated MM3 installation at the May Pycon. Did > > anything exciting happen toward that goal, or should I just press on with > > the latest release? > > We accomplished a lot. We are still tying up a few loose ends, but the > release should be soon. FWIW, this list is currently running on the > HEADs of the GitLab branches. Thanks, Mark. Will the release be pretty much a one-step affair for us older folks without much energy? -Tom

7 years, 2 months

[MM3-users] Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Mark Sapiro writes: > You don't need all of those. ^postorius/ and ^mailman3/ are two > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > two different ways to access HypereKitty. You only need one of each, That's true from "outside", but there are internal links as well. For example, in Postorius top page, the link to HyperKitty is .../archives. I guess it's a good idea to grep the templates to see which URLS are used. > > Now my question is about what could be adding the /mailman3. Is it possible > > that I installed something out of the ordinary? Besides mod_wsgi as Mark suggests and the uwsgi configuration, the only thing I can think of is an Apache rewrite rule. It's not in the Postorius and HyperKitty templates. Steve

2 years, 8 months

[MM3-users] Re: Mailman/Django-allauth integration with Yahoo

by Дилян Палаузов

Hello Mark, thanks for your answer. So I had in the past registered that yahoo address withing mailman. Then I added oauth/openid to yahoo, then gave it a try. I have receieved as resut two email in the yahoo mailbox. One is sent by yahoo, notifying about account activity. The other, which I have not overseen as it was evaluated as spam, contains: You are receiving this email because you or someone else tried to signup for an account using email address: zzz(a)yahoo.com However, an account using that email address already exists. In case you have forgotten about this, please use the password forgotten procedure to recover your account: https://…/accounts/password/reset/ So the text "we have sent you an email for verification” but the email stating ”there is already such an account within mailman” is misleading, especially after the first message is shown to an yahoo-authenticated user. Greetings // Дилян -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman/Django-allauth integration with Yahoo Date: 06/08/24 03:01:24 On 8/4/24 03:35, Дилян Палаузов wrote: > > Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: > > Messages: Confirmation of email address sent to ...(a)yahoo.com > Menu: Entrance \r\n New registration > > Confirm your email address: > > We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I'm not certain, but it looks like you are signing in to a new account and django-allauth is creating the account with the address from yahoo and is asking you to confirm. > I have indeed received an email, which states: > New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo > > So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. > > Any idea what can I improve? This appears to be a glitch in the new account verification process. In any case, it's a django-allauth issue, not a Mailman issue. Once you have gone through this dance, what happens the next time you sign in via Yahoo. > In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: > > SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} > > which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? I don't think it would matter. -- 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 dpa-mailman(a)aegee.org

1 year, 1 month

[MM3-users] Re: Postorius List members

by Alain D D Williams

On Wed, Nov 13, 2024 at 07:10:04PM -0800, Mark Sapiro wrote: > On 11/13/24 19:00, Alain D D Williams wrote: > > > > Is it possible to add delivery status to the summary where many users are > > shown ? I find this (on mailman 2) to be very useful, ie get a quick overview of > > what is happening to users. > > > There is a merge request in process for this. See > https://gitlab.com/mailman/postorius/-/merge_requests/953 Great I look forwards to that -- although since I have installed via Debian packages there will prolly be some delay :-( Thanks -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

9 months, 3 weeks

[MM3-users] Re: hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header

by Odhiambo Washington

On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/27/22 22:00, Odhiambo Washington wrote: > > I worke up to 959 such entries in my mailmanweb.log: > > > > ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The > > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ... > > > > What might have been the cause of this? > > > > Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= > 1.3.5 requires mailman-hyperkitty>=1.2.0. (venv) [mailman@gw ~/mm]$ pip list | grep itty HyperKitty 1.3.6 mailman-hyperkitty 1.2.0 Which I think is fine, no? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

[MM3-users] Re: Hiding the "subscribe without creating an account"

by Ben Sturmfels

> On 13/07/2024 07:17, Mark Sapiro wrote: > >> On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: >>> >>> Is there a configuration option that does this, or was it a custom change >>> made in the templates? Was the change made to reduce fake registrations? Did >>> it work? >> >> It was added in Postorius 1.3.9. See the UI section at >> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 >> >> Yes, the change was made in an attempt to reduce fake registrations. Thanks very much for the prompt advice Mark and Matthew! Really appreciate it. I'm currently running Postorius 1.3.8 (Debian Stable/Bookworm), so will look at upgrading and applying the settings you suggested. Regards, Ben

1 year, 1 month

[MM3-users] Re: troubleshooting hyperkitty

by Morris Jones

On 12/9/2020 9:11 PM, Mark Sapiro wrote: >> path: /opt/mailman/var/logs/archiver.log api_key <--- ?? Ugh ... I must have garbled my email. The files look fine. I don't know where that stray "api_key" came from. > The key in settings_local.py is MAILMAN_ARCHIVER_KEY, not > MAILMAN_ARCHIVER_FROM, a typo in your mail or ?? Yes, typo ... MAILMAN_ARCHIVER_KEY is 'properly_quoted' and unquoted in mailman-hyperkitty.cfg I'm guessing the next thing I need to do is find a way to crank up the logging in mailman and look for occasions where it calls the hyperkitty endpoint and delivers the message. I tried this but it may not be the right syntax: [logging.archiver] level: debug path: /opt/mailman/var/logs/archiver.log Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 8 months

Search results for query "sapiro"