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

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 3:41 PM, David Newman wrote: > > There are 24 messages in the shunt queue, the most recent of which is a > digest from 0000 hours today. The test messages I sent later today are > not there. > > There are also 13 messages in the out queue. I can't read these as the > filenames appear to change on every invocation of ls. I suspect an issue trying to connect to the MTA to send the messages. This can be caused by permission errors. Check permissions on Mailman's var/templates/* >> Are there errors and tracebacks in var/logs/mailman.log? Every message in the shunt queue should have an exception and traceback logged in mailman.log. > But the Postfix log doesn't show it being distributed to me or anyone else. Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in mailman.log? > Oddly, neither of the two list owner emails (me and someone else) show > this message in the archive via the admin panel. However if I log in as > the list owner directly to the archives: > > https://lists.domain.tld/archives/ > > I can see today's test posts if logged in as the list member, but do not > see the posts if logged directly into the archive as the Django superuser. That seems strange, I don't know why the superuser would not be able to see things in the archive that a list owner or member can. > The nondelivery of list mail is more serious than the archive problem, > though. Archiving is separate from delivery. messages can be archived and still fail delivery in the out runner which is what's happening here. The question is why? I suspect you have one or more 'Cannot connect to SMTP server ... on port ...' messages in mailman.log? and I suspect this is a misleading issue in this case caused by an inability to read some file in Mailman's var/templates/lists/<list_id>/en directory. I also suspect the shunted messages are from some prior condition which has possibly been fixed, but I can't be sure without exceptions and tracebacks from mailman.log (should be timestamped the same as the mod time if the shunted file). You can view them with `mailman qfile` and unshunt (reprocess) them with `mailman unshunt`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Help with Configuring Mailman3 for Multiple Mailing Lists on a Single Server

by Mark Sapiro

On 11/28/24 12:01 AM, peterrflores(a)hotmail.com wrote: > > Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius? This is how things work. See for example https://mail.python.org/mailman3/?all-lists - each of those lists has its own settings. There are also `unadvertised` lists on that server, e.g. https://mail.python.org/mailman3/lists/capi-sig.python.org/ > Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated. Mailman core provides a REST API for list management. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… - this interface is only protected by a user name and password, so it is normally only available via `localhost` as wider access is not very secure. Postorius uses this API via the python bindings described at https://docs.mailman3.org/projects/mailmanclient/en/latest/ > Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful. A list can be anonymous id desired which means the sender of a post is not identified in any headers of the distributed email. HyperKitty archives can be private, i.e. accessible only to list members. The membership list can be restricted to only list owners/moderators or available to list members as well via list settings. There is currently no support for encrypted email. Full access to a list's settings and other info via Postorius is limited to logged in users who are either a `superuser` or an owner of the list. moderators have more limited access, list members may be allowed to see the membership. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I made a change for test purpose on the mailman.cfg file and I got this: (env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running? How do I solve this? El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 6 months

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 17/9/21 17:24, Mark Sapiro wrote: > On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 16/9/21 16:40, Mark Sapiro wrote: >>> >>> Are you asking what the equivalent MM 3 scripts would be? >>> >> More or less: I'm asking for a general direction here. I think I >> cannot use tthe "withlist" method as before, inside a python script, >> and I'm not sure how to do it. > > > You can run scripts via withlist in Mailman 3 similarly to Mailman 2. > See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > First, thanks for the prompt response, Mark. Maybe I'm a little bit ofuscated, but I readed this doc many times when I was searching how to do it... but I cannot imagine how to do a shell or a python script, using the needed parameters, that sets hold on a member of a list. I'll try to do some tests tomorrow. As said, thanks.

4 years, 5 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I put this config in mailman.cfg: To configure Core to use Postfix, add the following configuration to your mailman.cfg configuration, be sure to replace mail.example.com with your email domain: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 is this correct?? El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 6 months

[MM3-users] Re: When mass subscribing using format John Doe <john.doe@example.com>, "Members" show some with real name, others without.

by Mark Sapiro

On 10/30/19 2:08 AM, Henrik Rasmussen wrote: > > It seems (I’m not certain about this) that the one’s without real name is the one’s already having an account and thus registred in Django (admin/auth/user/), while the ones subscribed with full name associated is the ones not having an account already. That's probably correct, but not the exact reason. > However, as soon as the member (the one with the account) went to Account and changed his real name, the name was immediately associated with the subscription in Members -> Subscribers. > > I expect this to be by design, but why isn’t the name associated with the subscription when mass subscribing in the first place, taken from the account? To understand, you need a bit of background. The basic engine that manages lists, subscriptions, users, etc. is Mailman core. Core does not provide any web UI. It only provides a REST API for use by other components. It is possible to run Mailman core only without any web UI, but management would need to be done directly via the REST API and/or `mailman shell` which is not particularly convenient. Because Mailman would not be too useful without a web management UI and a web based archiver, we provide Postorius and HyperKitty for these functions. These are only one possibility. One could build an entirely different web UI or other application to communicate with core via its REST API, but few if any have done so. Postorius and HyperKitty are Django projects and run under Django. The account that you see (Postorius top right) is a Django account. Core knows nothing about this. Core knows about users and addresses in its own database which is entirely separate from Django's accounts. These user/address records in core is where the user's display_name is kept. So when a user/address is added to a list, if core already knows that user/address, it just links that to the list and doesn't update the display_name, but if it doesn't know the user/address, it creates it and uses the supplies display name. It appears there is a mechanism within Postorius to detect a change in the name associated with a Django user and update core, but this is separate from subscribing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: What to backup?

by Mark Sapiro

On 5/26/19 7:00 AM, Alain Kohli wrote: > I have noticed that especially the var/messages directory has a rather > considerable size compared to the rest. What exactly is this for and > what would be the consequences if that was lost? When a message is held for moderator approval, a pickle of the message is stored in the var/messages directory and an entry pointing to it is made in the message table in the database. An entry is also made in the list's pending requests. These are required so the held message can be handled. There is an issue in that when these messages are handled these aren't removed. See <https://gitlab.com/mailman/mailman/issues/257>. Thus, most of what's in the var/messages directory is old, but there are also currently held messages there that would be lost. You could periodically remove older messages, but this would leave entries pointing to them in the message table in the database which could cause errors but probably not. The real solution is a fix for <https://gitlab.com/mailman/mailman/issues/257>. > And more generally, would not backing up var/ at all only result in the > loss of some short term data (e.g. messages that are held or currently > processed) or would long term data also be lost? Or in other words, what > exactly would be non-recoverable if that isn't backed up? That depends in part on what your backend database is. If it's SQLite, the database is probably in the var/data directory. If not, you need to be backing up the MySQL or postgreSQL mailman database. var/archives contains archived messages for the 'prototype' archiver and messages that are queued for hyperkitty. var/cache contains a cache of recently used templates. var/data may contain a SQLite database and may contain Postfix mappings. The Postfix mappings can be regenerated by the `mailman aliases` command. var/etc may contain your mailman.cfg if you don't point to a different one. var/lists contains accumulated messages for the next digest for your lists var/locks contains locks and should probably not be restored from a backup var/logs contains Mailman's logs. var/messages is discussed above. var/queue contains Mailman's current queues. Except for 'shunt' this is all things currently in process. var/templates may contain custom templates. Also, I didn't mention it before, but your Django settings.py and settings_local.py should also be backed up. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: New Mailman 3 installation issues

by Mark Sapiro

On 5/18/21 12:30 PM, sarah.hartt(a)ionica.ca wrote: > I have been trying to get a mailman 3 installation working for longer than I'd like to admit. Core appears to be installed and working as desired but Postorius (and hyperkitty, but I haven't even started troubleshooting it while trying to get the web interface working) is only loading the main page with no lists shown and all remaining links return a server error (specific text is: "Server error > An error occurred while processing your request." with the error text highlighted). I think I followed all of the installation instructions, including the updated pythonpath line in the systemd module, but it's entirely possible that there is an error somewhere along the way. Is there more information in logs? (nginx and django) > I have had to make two minor tweaks, the /static/ location was moved from /opt/mailman/web/static to /var/www/mailman/ (owner mailman:nginx) as nginx was giving permissions errors (even if it owned the files or with the mod set to 777) with the default location and wouldn't load the css, and installed postgres directly from their repo as the method in the guide doesn't create the user. Aside from that everything should be exactly as laid out in the installation guide. The permissions is probably a SELinux or apparmor issue. Which installation guide are you following? I'm guessing https://docs.mailman3.org/en/latest/install/virtualenv.html. Are you saying that ``` sudo apt install postgresql ``` doesn't create a `postgres` user? It should. > The logs are showing everything running and the DB logs show all the queries going through successfully, there are no errors in the web logs corresponding with the errors being served on the site aside an entry for a 500 in the access logs > > [18/May/2021:12:13:01] "GET /archives/ HTTP/1.1" 500 1102 "http://mailman3/mailman3/lists/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.91 Safari/537.36" "-" This is a GET of /archives/ which is HyperKitty. Django should log something for this with more detail. > when I took a look in the DB tables many of them appear to be empty, I have a few lists in core that were imported from 2.1 but no new lists created. Empty tables per se is not necessarily a problem depending on which ones. > Mailman: 3.3.4 > Postorius: 1.3.4 > OS: Oracle Linux 8.3 > Python: 3.6 > postgres: 13.2 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/21/22 10:39, Dan Caballero wrote: > I figured out the correct import based on what was done previously. It worked. Why do you think you need to import anything? > ">>> from mailman.app.moderator import handle_message `handle_message` is not referenced in the following and doesn't need to be imported here. ``` >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... if not requestdb.get_request(req.id): > ... print(f'Bad request id: {req.id}, deleting') > ... requestdb.delete_request(req.id) > ... > Bad request id: 1694, deleting > Bad request id: 2509, deleting > Bad request id: 2727, deleting > Bad request id: 3251, deleting > Bad request id: 3265, deleting > Bad request id: 3371, deleting > Bad request id: 4844, deleting > Bad request id: 6058, deleting > Bad request id: 6201, deleting > Bad request id: 6432, deleting > Bad request id: 6502, deleting >>>> commit ()" ``` I assume after doing this, you were able to access the held messages view for the list. Note that the only names referenced in the above and not defined there are `IListRequests` and `RequestType`, but these are among the many names implicitly imported by `mailman shell` in interactive mode. ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for name in dir(): ... print(name) ... ALL_TEMPLATES ALT_TEMPLATE_NAMES ALWAYS_REPLY AcceptEvent AcceptOwnerEvent Action AddressAlreadyLinkedError AddressError AddressNotLinkedError AddressVerificationEvent AlreadySubscribedError ArchivePolicy ArchiveRenderingMode BadDomainSpecificationError BounceContext ChainEvent ClobberDate ConfigurationUpdatedEvent ContinueProcessing DMARCMitigateAction DatabaseError DeliveryMode DeliveryStatus DigestFrequency DiscardEvent DiscardMessage DomainCreatedEvent DomainCreatingEvent DomainDeletedEvent DomainDeletingEvent DuplicateStyleError EmailError ExistingAddressError FilterAction FilterType HoldEvent IAPI IAcceptableAlias IAcceptableAliasSet IAddress IArchiver IAutoResponseRecord IAutoResponseSet IBan IBanManager IBounceEvent IBounceProcessor ICLISubCommand ICacheManager IChain IChainIterator IChainLink IConfiguration IContentFilter IDatabase IDatabaseFactory IDomain IDomainManager IEmailCommand IEmailResults IEmailValidator IHandler IHeaderMatch IHeaderMatchList ILanguage ILanguageManager IListArchiver IListArchiverSet IListManager IListRequests IMailTransportAgentAliases IMailTransportAgentDelivery IMailTransportAgentLifecycle IMailingList IMember IMembershipManager IMessage IMessageStore IMutableChain IOneLastDigest IPendable IPended IPendedKeyValue IPendings IPipeline IPlugin IPreferences IRoster IRule IRunner IStyle IStyleManager ISubscriptionManager ISubscriptionService ISwitchboard ITemplate ITemplateLoader ITemplateManager IUser IUserManager IWorkflowState IWorkflowStateManager InvalidConfigurationError InvalidEmailAddressError InvalidListNameError LinkAction ListAlreadyExistsError ListCreatedEvent ListCreatingEvent ListDeletedEvent ListDeletingEvent MailmanError MemberRole MembershipChangeEvent MembershipError MembershipIsBannedError MissingConfigurationFileError MissingPreferredAddressError MissingUserError NewsgroupModeration NoSuchListError NotAMemberError PasswordChangeEvent PendType Personalization RejectEvent RejectMessage ReplyToMunging RequestRecord RequestType Response ResponseAction RunnerCrashEvent RunnerInterrupt SomeRecipientsFailed SubscriptionConfirmationNeededEvent SubscriptionEvent SubscriptionInvitationNeededEvent SubscriptionMode SubscriptionPendingError SubscriptionPolicy TokenOwner TooManyMembersError UnrecognizedBounceDisposition UnsubscriptionConfirmationNeededEvent UnsubscriptionEvent UnverifiedAddressError __builtins__ abort commit config getUtility m >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Counter-intuitive header filter processing

by Mark Sapiro

On 09/18/2018 01:04 PM, Jonas Meurer wrote: > > Maybe then the description for chain "accept" in postorius needs to be > adjusted. Currently it says "Accept immediately (bypass other rules)". > This gives the impression, that it will overrule the default action. Yes, I agree it's confusing. > A related followup question: what configuration is recommended for an > announcement list where only specific senders (e.g. sender(a)example.org) > should be allowed to post and mail from all (other) subscribers should > be rejected? > > The only way I see to achieve this currently is: > > * Set default action for member posts to "Default processing" > * Add a header filter to accept "sender(a)example.org" > * Add a header filter to reject ".*" > > In my eyes, that's very counter-intuitive and cumbersome to configure. > But maybe I just missed a more obvious and elegant solution to achieve > the same? The way to do that is to set the default action for member posts to Reject and set Member Options -> Administration options -> Moderation for the authorized posters to Accept or Default processing as desired. However, this allows anyone to post by spoofing an authorized address. To avoid that, leave everyone's Moderation setting at List default and post using "pre-approval" (see <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/approved.ht…>. The downside of this is it requires the poster to send a cleartext password in a header or body line of the post. It will be removed from the post delivered to list members, but sending it in cleartext in an email may be an issue. We will eventually do something with PGP signatures instead, but that isn't here yet. > And one more comment: if I make the list an "anonymous list" (i.e. "hide > the sender of a message, replacing it with the list address"), then > header filters for the "from" header don't work any longer. That's kind > of unexpected as well. I would have expected mailman to process the > header filters at reading the incoming mail, not after rewriting headers > of the outgoing mail? Your expectation is correct. All the applicable rules are applied to the incoming message before any message alterations such as anonymizing are applied. Possibly you were confused because some other rule's action took precedence over your header rule. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

Search results for query "sapiro"