Search results for "Postorius" - Mailman-users

Mailman/Django-allauth integration with Yahoo

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

Hello, Has anybody managed to use the Django-Allauth Yahoo provider to authenticate towards Mailman3? I have integrated mailman3/django-allauth/gmail — it works. I want in the same way to integrate mailman3 with yahoo mail. As advised at https://docs.allauth.org/en/latest/socialaccount/providers/yahoo.html , in yahoo I register an application with redirect URL https://l.bapha.be/mm3/accounts/yahoo/login/callback/ , then I add credentials under mm3/admin/socialaccount/socialapp/: client ID and Private Key. I append in settings.py:INSTALLED_APPS = [… 'allauth.socialaccount.providers.yahoo' ]. After I do all of this, I eventually visit /mm3/accounts/login/?next=/mm3/postorius/lists/at.l.bapha.be/, click on Yahoo: “Sign In Via Yahoo . You are about to sign in using a third-party account from Yahoo.” → [Continue]. Now at https://login.yahoo.com I enter user name and password. 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 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? 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? Greetings Дилян

1 year, 1 month

Re: migration from 2.1 - owners and moderators

by Brian Carpenter

On 10/23/20 8:31 PM, Alex Schuilenburg via Mailman-users wrote: > We're migrating from 2.1 to 3.2.1 and an odd issue has popped up. It > may be something different in the way mailman3 works, or a > misconfiguration on my part. > > Most of the lists migrated so far don't have moderators, just owners. > However, when these lists have messages requiring moderation, the > owners dont get notified of held messages - unlike 2.1 where they > did. Is this a change or is there something I am missing in the > configuration? > > I have the minute/quarterly/hourly etc cron jobs running, although I > have had to tune down the frequency of minute to hourly as it takes > 6.5 minutes to run* - but I doubt this is the cause. > > While for the moment I have found the held messages in files in > /var/lib/mailman3/messages and figured out which lists are in need of > attention (and notified the owners), it seems I may have to do a bit > of coding myself to walk through the lists and notify owners when > their list is in need of attention. There must surely be something > that does this already - or is this moderators only in mailman3? > > Guidance appreciated. > > Thanks > > -- Alex > > * From the list I realise this is because I am still using the default > whoosh backend to haystack and need urgently to switch to xapian or > solr, but the info on how to get this working for a noob like me is > unfortunately lacking Hi Alex, List owners should be receiving moderation notifications and are able to moderate messages when they log into Postorius. Have you checked your MTA logs to see if they are or are not being sent out? If you don't mind having some paid assistance, I may be able to assist you with getting Xapian up and running. We use Xapian on our vanilla MM3 servers and Elasticsearch on our MM3 Affinity/Empathy servers. You can contact me off list if you are interested. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 10 months

Report problems NOW if you're not *sure* it's *not* a bug

by Stephen J. Turnbull

Nathan Dixon writes: > Am I missing something in my install? Or is this a bug? One of us will get to it specifically "soon" (we're all at PyCon YEAH! so not paying much attention BOO!) Right now I HAVE SOMETHING I WANT TO SAY TO YOU ALL: Sprints are coming up! This is your chance to report bugs and maybe get something done quickly. (Not all bugs get fixed quickly, sorree. But this is the best chance ) RFEs are welcome, too. What's a bug? Well, if you're sure it's NOT a bug, don't report it, post to this mailing list and get help on what you can do to make your life better. That's the best way, because some of the users are smarter and more experienced and more available than the developers. If you're pretty sure it is a bug, report it at https://gitlab.com/mailman/mailman/issues https://gitlab.com/mailman/postorius/issues https://gitlab.com/mailman/hyperkitty/issues Do your best but don't get too frantic about picking the right one. We can move (close and re-report on the correct component) issues. If it's somewhere in the middle, do both! First, report on the issue tracker so you can cite it in the mailing list post. Then post to the mailing list because it might not be a bug, and the logic above applies. If you've got the time, Google for "howto report bugs". It is time well-invested, because the more useful information you provide up front, the faster we can diagnose the harder bugs, and thus the faster we can fix them or provide a workaround. Again, don't get frantic about it, we'll ask for more information if we need it. And yes, I should ensure there's a HOWTO-BUG on the sites with both generic advice and common Mailman requirements for diagnosing bugs. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 4 months

Re: Digests not working correctly

by Joel Lord

On 6/4/2023 9:25 PM, Mark Sapiro wrote: > On 6/4/23 11:45, Joel Lord wrote: Thanks for the explanation on size-triggered digests. >> 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. The periodic digests do seem to be coming out. I also now have confirmation that the one message in this morning's digest that was from May 4th was also included in the last digest back on May 4th, so it seems that the one message was left behind in the digest queue when the periodic digest was sent. There was one earlier message to the list back on May 4th, before the one that got duplicated, but I can't tell if that triggered a size-based digest to be sent: the logs aren't clear enough on that detail for me to tell. Just to inform things: (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman django-mailman3==1.3.9 mailman==3.3.8 mailman-hyperkitty==1.2.1 mailman-web==0.0.6 mailmanclient==3.3.5 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper mailman-hyperkitty==1.2.1 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post postorius==1.3.8 -- Joel Lord

2 years, 3 months

Re: Filter who can send on mailman3 list?

by Ruth Ivimey-Cook

Marcus, I'm with you in not understanding Mark's instructions -- I think there is a typo somewhere :-) To create a non-member user in Mailman, Go to the List Settings page in Postorius, select Non-members from the User menu, and add a user there. Of course, that does nothing for your email system, which must also be configured. I would very strongly encourage you to have the no-reply address be 'real' in the sense that the email system will agree it is valid and deliverable, or some recipient email servers will refuse to accept email from that address, either. The right thing is for email to that address accepted as normal and then immediately discarded. You could send back a message "this address is not monitored" but there is an issue with spam backscattering which makes that less good than it first seems. Regards, Ruth On 06/04/2021 10:00, marcus.granath(a)gmail.com wrote: > Thank you @Mark Sapiro for you quick reply. > > So by doing the following settings, then ALL the messages sent to the list will be hold for moderation: > > Settings -> Message Acceptance > > "Default action to take when a member posts to the list": "Hold for moderation" > "Default action to take when a non-member posts to thelist": "Hold for moderation" > > Members -> Administration options -> Moderation: "List default" > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? > > Also, how do I create a "non-member" user "no-reply(a)abc.com"? > Do you mean that I do that under the "Mass operations -> Mass subscriptions" ? Can I add a "fake address" there? > _______________________________________________ > 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/ -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 5 months

Re: Unsubscribe Notifications to List Owners and Members

by Brian Carpenter

What list are you trying to unsubscribe from and how are you doing it? On 10/22/20 4:58 PM, Jerry Koutavas wrote: > > No offense but been trying to unsubscribe for months, nothing happens > > *From:*Brian Carpenter [mailto:brian_carpenter@emwd.com] > *Sent:* Thursday, October 22, 2020 4:56 PM > *To:* Mailman users <mailman-users(a)mailman3.org> > *Subject:* [MM3-users] Unsubscribe Notifications to List Owners and > Members > > It seems that the only time an unsubscribe notification is sent to a > list owner and/or list member is when a list member sends an email to > lisname-unsubscribe@listdomain <mailto:lisname-unsubscribe@listdomain> > and that list member is not registered > with Affinity/Postorius. Can anyone confirm this and if confirmed, is > this considered a bug? > > > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > ------------------------------------------------------------------------ > > *Total Control Panel* > > > > Login <https://asp.reflexion.net/login?domain=ascii.com> > > To: jk(a)ascii.com > <https://asp.reflexion.net/address-properties?aID=10188568&domain=ascii.com> > > From: mailman-users-bounces+jk=ascii.com(a)mailman3.org > <mailto:mailman-users-bounces+jk=ascii.com@mailman3.org> > > > > Message Score: 70 > > > > High (60): Fail > > My Spam Blocking Level: Medium > > > > Medium (75): Pass > > > > > Low (90): Pass > > Block > <https://asp.reflexion.net/FooterAction?ver=3&bl-sender-address=1&hID=458079…> > this sender / Block > <https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-address=1&hID=…> > this sender enterprise-wide > > > > Block > <https://asp.reflexion.net/FooterAction?ver=3&bl-sender-domain=1&hID=4580794…> > mailman3.org / Block > <https://asp.reflexion.net/FooterAction?ver=3&ent=1&bl-sender-domain=1&hID=4…> > mailman3.org enterprise-wide > > > > /This message was delivered because the content filter score did not > exceed your filter level./ > -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 10 months

Re: Newbie hyperkitty question

by Mark Sapiro

On 1/11/22 8:27 AM, Stephen Daniel wrote: > Mailman users -- > > I am setting up a new mailman3 installation, and this is my first > experience with the suite. All of the software is up and running, but I > cannot tell if hyperkitty is actually running. In Postorius, in the list's `info` view can you click the Archives button and see archived messages? That's HyperKitty. If the messages aren't there with the hyperkitty archiving option enabled, check `mailman.log` for why. Also do messages from the list have an Archived-At: header? > When I look at my test mailing list, two archive options are available, > hyperkitty and "prototype", and both are enabled. I can see that my email > is being archived, but I think "prototype" is what is doing the archiving. > I see that a test message will end up in > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > and nowhere else. This suggests that "prototype" is archiving, but > hyperkitty is not. No this says the prototype archiver is working. It says nothing about Hyperkitty. > So, this opens up a raft of questions on hyperkitty: David Newman has answered some of this, but ... > - How do I tell if hyperkitty is actually running? It doesn't actually run. it is a Django web UI and a web API that serves things on request. > - Does hyperkitty have a web-UI for admins or users? How would I access > it? See above. > - I can not find any documentation on hyperkitty, other than > installation instructions and change logs. Does documentation exist? No, not really. > - How do I set policies on how long archives are kept? > - Assuming I want to back up my archives, what do I need to back up? Messages are kept forever unless you do something to delete them. HyperKitty's messages are stored in the database configured in the DATABASES setting in your Django settings. How you backup the database depends on the database manager. You already found the prototype archiver's messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: How to store additional information about lists?

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210523 02:41]: > Andreas Barth writes: > > > Currently it is "list public" vs "subscribers only". I need something > > inbetween, so that some (i.e. most) people have access to the > > restricted audience lists but not just everybody. > > That much is clear. The problem is that "access to list" can mean a > lot of things: can subscribe, can post, can admin, can view archives, > can view list in listinfo, can view subscriber list, and there are > probably others. What permissions are needed for what general classes > of users? public: anyone can subscribe and read the archive. Think about an announcement mailing list of an organisation. restricted: for employees (or members - or whatever) only. So they could subscribe themself. The archive and posting may be restricted to subscribers or to anyone in that group - both would be working for me. (How to know who is allowed to subscribe is another question - having an internal mailing list which contains all the members just for this purpose would be ok for me.) private: hand-selected people, think about e.g. board or steering committees internal discussions. Of course, the archive (if there is any) should be restricted to the actual members. Posting to these lists is currently not restricted, so no derivation needed from the current set in postorius. > > Just as an idea, how about always one "custom attributes" field. So > > that from a database pov this field is always there. > > We could do that, but then we'd have to support it. I'm thinking of > situations like admin A populates the field, then leaves the > organization, and we add (some of) the supported features, and admin B > wants to migrate that. I don't see any good coming of that for us. > As Mark says, a separate table seems like the way to go for custom > attributes. Well, that problem will always exist. I don't think you would make it harder by having one "custom attributes" field. I'm going to try the plugin route Mark suggested. Andi

4 years, 3 months

Re: [MM3-users off list] Re: Welcome message template errors

by Mark

>> So, I'm thinking (in broad brush strokes) that if I'm stuck with this >> "http glitch" I could write a script to: >> >> 1. extract the text of the custom message from the database, >> 2. write that message text to a file >> 3. update the templates.uri entries to replace the >> http://localhost... with file:///path/to/file >> 4. cron the script to run every few minutes. >> >> It screams of utter clunk I know... > but it would work. > > Note that this may not be as big an issue as it seems. It doesn't > affect all templates, for example list:member:digest:footer, > list:member:digest:header, list:member:digest:masthead, > list:member:regular:footer, list:member:regular:header and > list:member:generic:footer are only used by the `out` runner when > sending messages, so these aren't affected. Right. Affected are all the "list:user:notice:***" (eg. goodbye, hold, reject,...) > > I'm still trying to determine what the issue is. To this end can you > tell me what Python version your Mailman uses and what is the output > from `pip freeze` with your venv active? $ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] $ pip freeze aiosmtpd==1.4.4.post2 alembic==1.13.1 arrow==1.3.0 asgiref==3.7.2 atpublic==4.0 attrs==23.2.0 authheaders==0.16.2 authres==1.2.0 blessed==1.20.0 certifi==2023.11.17 cffi==1.16.0 charset-normalizer==3.3.2 click==8.1.7 cmarkgfm==2024.1.14 cryptography==42.0.1 defusedxml==0.7.1 Django==4.2.11 django-allauth==0.60.1 django-appconf==1.0.6 django-compressor==4.4 django-extensions==3.2.3 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.12 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 dkimpy==1.1.5 dnspython==2.5.0 docutils==0.20.1 falcon==3.1.3 filelock==3.13.1 flufl.bounce==4.0 flufl.i18n==5.0.2 flufl.lock==8.0.2 greenlet==3.0.3 gunicorn==21.2.0 HyperKitty==1.3.9 idna==3.6 lazr.config==3.0 lazr.delegates==2.1.0 mailman==3.3.9 mailman-hyperkitty==1.2.1 mailman-web==0.0.9 mailmanclient==3.3.5 Mako==1.3.0 MarkupSafe==2.1.4 mistune==3.0.2 networkx==3.2.1 nh3==0.2.15 oauthlib==3.2.2 packaging==23.2 passlib==1.7.4 postorius==1.3.10 psutil==5.9.8 psycopg2-binary==2.9.9 publicsuffix2==2.20191221 pycparser==2.21 Pygments==2.17.2 PyJWT==2.8.0 python-dateutil==2.8.2 python3-openid==3.2.0 pytz==2023.3.post1 rcssmin==1.1.1 readme-renderer==42.0 redis==3.5.3 requests==2.31.0 requests-oauthlib==1.3.1 rjsmin==1.2.1 robot-detection==0.4 six==1.16.0 SQLAlchemy==2.0.25 sqlparse==0.4.4 types-python-dateutil==2.8.19.20240106 typing_extensions==4.9.0 urllib3==2.1.0 wcwidth==0.2.13 Whoosh==2.7.4 xapian @ file:///opt/mailman/xapian-1.4.24-cp311-cp311-linux_aarch64.whl xapian-haystack==3.1.0 zope.component==6.0 zope.configuration==5.0 zope.event==5.0 zope.hookable==6.0 zope.i18nmessageid==6.1.0 zope.interface==6.1 zope.schema==7.0.1

1 year, 4 months

Re: converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Lucio Chiappetti

Dear Mark, thanks for your interest. On Fri, 11 Feb 2022, Mark Sapiro wrote: > This may actually be a bug. I'll have to think about that. I've filed > https://gitlab.com/mailman/mailman/-/issues/978 on this. > This is https://gitlab.com/mailman/mailman/-/issues/794 (still open) Given the time needed to solve the issues (I will anyhow notify the site administrators, hopting they would update mailman when/if resolved), this means we have to find a workaround. > And those non-members all have there moderation action set to Defer > which means their posts will be accepted but the additional checks such > as too big, etc. will still be applied. not sure what you mean by "defer". The non-member options I see are called List default -- follow the list's default member action. Hold -- This holds the message for approval by the list moderators. Reject -- this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. Discard -- this simply discards the message, with no notice sent to the post's author. Accept -- accepts any postings without any further checks. Default Processing -- run additional checks and accept the message. > If they are nonmembers, you can accept the post and set moderation > action in one operation in Postorius, but the regexps in > hold_these_nonmembers will still take precedence. OK, I've found where to do it, it requires to select the held message and scroll to the bottom then set Moderation from a menu. But if hold_these_nonmembers takes priority this will be uselesws in the current setting. > I'm not sure what you are looking at here. Imported nonmembers should > all have moderation action set according to which *_these_nonmembers > they came from. Imported members should have their moderation action set > to Defer if they were unmoderated and if they were moderated, it should > be set based on the 2.1 list's member_moderation_action. I go to the non-member list, select non-member options and at the bottom see an item Administration options Moderation. The possible values are those I pasted above. The actual value for most of the imported non-members is "Default processing" while it is "List default" for thoase automatically added afresh, It is "Discard" for a number of imported non-members with spam-looking addresses (I guess they were in some other *_not_members part of the standard 2.1 antispam ... I can't recall me doing something on those) Side question: is there a way to operate IN BULK on non-members ? Like it is for members (I exported them to CSV). >> - if so, how can we do it automatically for all 189 entries ? >> - or move back the 189 addresses to accept_these_nonmembers ? > Yes, move them back. I am not so concerned of these 189 (or better of the 189 minus the discard ones which should stay) ... anyhow moving them back will be uncomfortable if there is not a bulk operation tool. I am more concerned of the new cases automatically added. Our member list includes 1043 addresses. Of these less than 20 use an external address (say gmail), so they post "from home" and will pass. 194 addresses are of the form name.surname(a)inaf.it (these are likely to be recently hired staff, who have and use onlyu the organization-wide address). All the rest (so still more than 800, can't really ask all of them to re-register (*)) are of the form username(a)institute.inaf.it (and it won't be easy also to bulk-delete and bulk-resubscribe because of the inhomogeneous mapping of username to name.surname. Of these about 800 some are lurkers and are no problem. Some are frequent posters and remember to post from username(a)institute.inaf.it and are no problem. Other may post from an alternate address (maybe even the old address exists as a receiving-only alias), and in this case with the current arrangement they will bo on hold every time. I guess we should wait for the solution of issue 794 (*) by the way do you confirm that if one is subscribed to a list with an address (be it bulk subscription, import or new fast subscription), this person CANNOT change their settings (or address) unless one does a "sign in" to a (Postorius) account ? > It is because all the legacy *_these_nonmember actions are applied > before nonmember moderation checks, so if an address matches a regex in > hold_these_nonmembers, the post will be held regardless of the > nonmember's moderation action. > Addresses still work, and accept_these_nonmembers takes precedence over > hold_these_nonmembers just as in MM 2.1. This was not my impression when I ran a thorough test of 12 cases. Except the obvious case of the subscriber posting from the subscription address, all messages went on hold. Whatever the non-member moderation would be (even if set to reject ! ... but that makes sense if *_these_nonmembers prevail on non-member options), and even if the address was set explicitly in accept_these_nonmembers (should I delete it from the non-member list ?) What is the actual order (or flow chart) of choices ? *_these_nonmembers in the order listed in the page (within each in the order of occurrence of regexp's) then non-member options ? If I have Name.Surname(a)inaf.it in accept_these_nonmembers, then hold_these_nonmembers set to ^.+@.+\.it ^.+@.+\.tng\.iac\.es what do you foresee ? And for different regexps, will processing terminate at the first non-matching one, will they be ANDed or ORed, or what ? I am reluctant to accept inconditionally ^.+\..+(a)inaf\.it (they may be falsified, only the check on their presence in the other list (issue 794) I guess I should remove the ^.+@.+\.it regexp AND AT THE SAME TIME change the Default action to take when a non-member posts to the list to Hold instead of Discard. This way we'll have to check spam (instead of having it auto-discarded), but if people with alternate addresses post, once they are entered in the Non-member list they can be authorized to pass for the future ... .. would it work ? -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html

3 years, 7 months

Mailman-users search results for query "Postorius"