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

[MM3-users] Re: How to use the "recipient_delimiter" postfix parameter with Mailman3?

by Pierre Malard

Ok, thanks for the documentation. But as Mailman uses this functionality for its own processing of emails, if I leave it to be used for another processing, Mailman will no longer work correctly... Ok, that means I'm going to forbid the use of the escape character when processing mailing lists. > Le 12 avr. 2022 à 16:37, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On 4/12/22 01:56, Pierre Malard via Mailman-users wrote: >> Hi, >> We are using the « recipient_delimiter » parameter with our Postfix server as « _ ». >> Visibly, Mailman have it’s own mail configuration because it doesn’t work know. >> Is it a way to conserv this Postfix functionality? > > > Mailman by default expects the recipient delimiter to be `+`. There are various settings in the [mta] section of mailman.cfg that allow you to change this. These are documented along with default settings at lines 812 - 898 of https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > > -- > 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/ -- Pierre Malard Responsable architectures système GeoSUD IRD - UMR Espace-Dev - UMS CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Les utopies ne sont souvent que des vérités prématurées » Alphonse de Lamartine |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

4 years, 1 month

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< mailman-users(a)mailman3.org>) escribió: > I think you're confused. > > You already have mail.labbrands.com set up as the MX record for > labbrands.com. And it has an A record with the same address as your > webserver. > I'm working with the hostgator mailserver, we are not running a local mailserver. As suggested I added an A record like this: [image: image.png] Is it correct? is it redirecting to my Ip so I can redirect it to my postfix/mm3 server? > > So if you're getting e-mail on that domain, there's another e-mail > server running on that IP address. You can't have 2 servers on port > 25. In that case, as has been noted before, you'll need to setup a > relay in that server, not a firewall redirect. Depending on your MTA, > you would need to relay to your internal server. And make sure your > firewall setup allows your MTA to do this. > > We can see it's EXIM: > > telnet mail.labbrands.com 25 > Trying 192.185.51.89... > Connected to mail.labbrands.com (192.185.51.89). > Escape character is '^]'. > help > 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48 > -0500 > 220-We do not authorize the use of this system to transport unsolicited, > 220 and/or bulk e-mail. > 214-Commands supported: > 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > quit > 221 gator4137.hostgator.com closing connection > Connection closed by foreign host. > > Or, consolidate all your e-mail to one server - which is a lot easier to > manage unless you have a really big operation. Postfix is probably the > right choice, but requires more setup. > > Although Mailman3 configuration is not well documented (as you've > discovered), you may want to get help from someone with more general > network and mail experience. You're now into territory that is, as > Simon indicated, not Mailman-specific. > > On 03-Aug-17 16:28, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > >> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > >> escribió: > >>>> You need to forward port 25 for SMTP mail delivery and if you want the > >>>> web UI (Postorius and HyperKitty) accessible from the outside, port 80 > >>>> for http and/or port 443 for https > >>>> < > >>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>> . > >>> I mean for incoming mail redirected from my hostgator hosting, because > >> when > >>> I suscribe an email address MM3 sends a confirmation email, so I have > to > >>> reply to be suscribed to the list. > >> > >> As I said, for mail delivery you need to forward port 25 to the Mailman > >> server. > >> > > Ok so I'll redirect in my zentyal firewall the port 25 to my local > centos7 > > with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > > > > >> > >> -- > >> 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/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > 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, 9 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Mark Sapiro

On 2/11/21 10:22 PM, hansen(a)rc.org wrote: > I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I'm sorry about that. It's too late now, but the avoidance is discussed at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. > > I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? If the user has a Django account, she can see all that info at (e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/> She gets there from `Mailman settings` in the dropdown under her user name. She can also get there via the `Manage Subscription` button on the list's Info page. That takes her to `List-based preferences` for the list. Any setting not selected there is inherited from the Address-based preferences or Global Mailman preferences > Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. You've already reported this at <https://gitlab.com/mailman/postorius/-/issues/462>, and it's been previously reported at <https://gitlab.com/mailman/postorius/-/issues/369>. > As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). I'm sorry you had to go through this. The potential issue and the avoidances should be better documented. Unfortunately, they aren't. > Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: > > a. The ability of moderators to see the list membership (a bug). As I note above, this is a known issue. We are a small project with very feew core developers, all of whom are volunteers. There is a merge request at <https://gitlab.com/mailman/postorius/-/merge_requests/423> which purports to fix <https://gitlab.com/mailman/postorius/-/issues/369>, but as you can see from the comment thread, it is not complete and the author has apparently disappeared. If you would like to take it over and address the deficiencies, we would welcome that. > b. The ability of members to change their addresses for all lists they are subscribed to. Users can add addresses to their account and can then change their subscribed address at (again, e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/list-options/mailman-users.mai…> (Get there via the `Manage Subscription` button on the list's Info page.) If one is subscribed to lists via their `primary` address, one can go to `E-mail Addresses` in their account settings and make a new address `primary` and that will change all their subscriptions. > and further, now: > > c. That when members go to look at their subscription info, they can actually see the settings. They can if they go to `Mailman settings` in the dropdown or the `Manage Subscription` button on the list's Info page and look at all the tabs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Apache Conf

by Abhilash Raj

On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: > 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" And, you have verified that the files exist at `/opt/mailman/static` on your host? > > > 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/ > > > _______________________________________________ > 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)

7 years, 7 months

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

After making that change and doing some testing. So far I’ve not had any issues and the sync are working as expected now. -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- 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/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

5 years, 2 months

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, as the original poster, I have asked the user to send a test mail through our mailman3 system (docker image maxking/mailman-core:0.4.2) and the mail passed. The user is now on Apple Mail 16, maybe that does the trick. Please find enclosed the anonymizied mail source. Best regards and thanks for caring even if the problems seems to affect only a small number of users! Rainer On Fr, 15 Apr 2022 09:03:41 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/14/22 21:33, Stephen J. Turnbull wrote: >> >> Whether we *want* to do that depends on how much trouble that causes >> for our main constituency (list and site admins), and whether we can >> provide discoverable documentation of the problem. My take is that >> this seems to be an extremely rare problem, and at least some MUAs >>are >> able to read the message, so we should let it through. > >First, we are not silently dropping this message. We are rejecting it >at LMTP time so the sender should be notified. > > Then the broader question is should we accept all messages with >defects, almost all of which are spam, or only certain defects and >which ones. > > I note that Apple has now released Mail 16 so maybe they've fixed >this. My macs are still on Big Sur, so I can't test this. > > > -- > 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/ > Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

4 years, 1 month

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Hello Mark, thanks for your hint. Postfix is runnig as mta on my machine. I tested port 25 with swaks ->mail to user on server: localhost port 25 -> everything fine Mailman is configured with localhost for incoming and outgoing mails. After stopping mailman3, deleting all files in the queue directories, restart mailman3 I sent a test-mail /var/log/mailman3/mailman.log Apr 07 12:08:23 2020 (28198) Master started Apr 07 12:08:24 2020 (28206) out runner started. Apr 07 12:08:24 2020 (28202) command runner started. Apr 07 12:08:24 2020 (28203) in runner started. Apr 07 12:08:24 2020 (28200) archive runner started. Apr 07 12:08:24 2020 (28201) bounces runner started. Apr 07 12:08:24 2020 (28210) retry runner started. Apr 07 12:08:25 2020 (28208) rest runner started. Apr 07 12:08:25 2020 (28212) digest runner started. Apr 07 12:08:25 2020 (28205) nntp runner started. Apr 07 12:08:26 2020 (28211) virgin runner started. Apr 07 12:08:26 2020 (28207) pipeline runner started. Apr 07 12:08:26 2020 (28204) lmtp runner started. Apr 07 12:09:19 2020 (28203) ACCEPT: <000f01d60cc4$96c9a8d0$c45cfa70$@[domain]> Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost on port 25 I have no idea what to do for solving my problems. Regards from Hamburg Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Montag, 6. April 2020 23:50 An: Wolfgang Bock <mailinglisten(a)wbock.de> Betreff: Re: [MM3-users] Re: Uncaught runner exception On 4/6/20 2:44 PM, Wolfgang Bock via Mailman-users wrote: > Thank you Steven for your reply! > > I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server > on port 25", the former error message didn't show again. > > As I see port 25 is reseved for postfix. So I have to fiddle out how > mailman3 could also use this port for sending mails out. .... You need an MTA for Mailman to deliver its mail to. Normally this will be Postfix, sendmail, Exim, etc running on localhost and listening on port 25. Do you have such an MTA running on localhost? Note, Mailman does not directly send mail to end recipients. It only delivers mail to an outgoing MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Setting up on ubuntu server 22.04

by Kyriakos Terzopoulos

Thanks Mark, That seemed to work: (venv) mailman@hestia:~/venv$ mailman info GNU Mailman 3.3.8 (Tom Sawyer) Python 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:XXXXXXXXXXXXX>@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: XXXXX:XXXXXX Now, off to handle other issues like nginx, exim4, etc. I will search or create another thread for this if I'm stuck. It would be nice to somehow update the documentation for https://docs.mailman3.org/en/latest/install/virtualenv.html. Thank you all for your efforts. *Kyriakos* On Wed, 4 Oct 2023 at 03:44, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/3/23 06:00, Kyriakos Terzopoulos wrote: > > > > However, I cannot find the mailman/setup.py anywhere in order to patch > it, > > since the installation was done through pip from here: > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > > Maybe I can try upgrading python from 3.10 to 3.11 and re-install > > > Upgrading Python won't help. There is currently an incompatibility issue > when following > https://docs.mailman3.org/en/latest/install/virtualenv.html because that > doc is based on the head of the GitLab branch, but `pip install > mailman3` installs the 3.3.8 released version of core and the latest > 6.1.0 version of importlib_resources and these are incompatible. > > There are two ways to fix this. > > The easy way is to downgrade importlib_resources in your venv with > ``` > pip install importlib_resources\<6.0 > ``` > The slightly more complex way is to upgrade mailman core to 3.3.9b1 from > GitLab with > ``` > pip install -U git+https://gitlab.com/mailman/mailman.git > ``` > > -- > 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 kyriakos.terzopoulos(a)gmail.com >

2 years, 7 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

$ /opt/mailman/mm/bin/mailman version GNU Mailman 3.3.2 (Tom Sawyer) So, I'm running > 3.2. Any other advice on debugging the truncated data? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, August 2, 2021 10:06 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/2/21 4:15 PM, Bryan Loniewski wrote: > Hi all -- > > $ /opt/mailman/mm/bin/mailman lists > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/commands/cli_lists.py", line 78, in lists > for mlist in list_manager.mailing_lists: > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/model/listmanager.py", line 100, in mailing_lists > MailingList._list_id).all() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3246, in all > return list(self) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 101, in instances > cursor.close() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 69, in __exit__ > exc_value, with_traceback=exc_tb, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ > raise exception > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in instances > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in <listcomp> > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 589, in _instance > populators, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 726, in _populate_full > dict_[key] = getter(row) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/sql/sqltypes.py", line 1708, in process > return loads(value) > _pickle.UnpicklingError: pickle data was truncated This is probably https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co… which was fixed in Mailman 3.2.0 by https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…. What version are you running? If your version is 3.2.0 or greater, it could be one of the other issues with MySQL/MariaDB truncating data. -- 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://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 9 months

[MM3-users] Re: Rejecting held emails

by Darren Smith

Mark, You're quite right, I meant Discard. Thanks for the clarification. I hope to be able to pull a fix in for this in the near future. :) -Darren On Thu, Apr 26, 2018 at 10:14 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/26/2018 08:43 AM, Darren Smith wrote: > > > > We recently had a phishing message make it through our spam filters and > > arrive at a mailing list. The good news is that since it was not from a > > list member it was in the held message queue. > > > > I was able to find the message in the var/messages directory by searching > > for a keyword in the subject. However, after rejecting the message from > > Postorius, the message doesn't seem to be removed from the var/messages > > directory. > > > Do you mean Reject and not Discard? Phishing/Spam should never be > "rejected" for backscatter reasons. Reject should only be used for > somehow inappropriate posts from known people. > > > > Is this expected behavior? I know that infosec people won't be too happy > > about a phishing email sitting around on our disk. (Infosec guys are > > notoriously paranoid. :) ) > > > > Is there some sort of cleanup process that would remove these messages? > If > > not, does this pose an issue where over time disk usage will creep up? > This > > could be a pretty significant problem if that is the case. > > > It's not the behavior I would "expect", but it is the way it currently > works, and yes, all your concerns are valid. This is > <https://gitlab.com/mailman/mailman/issues/257> which I just edited to > note that in addition to not removing the pending db entry, the message > isn't removed either. > > -- > 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/ >

8 years, 1 month

Search results for query "sapiro"