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

[MM3-users] Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 5:48, Mark Sapiro escribió: > On 10/26/22 04:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I did it via pip and all seems to be working, but when I try to >> discard or accept any message via postorius it shows a Forbidden 403 >> error CSRF verification failed. >> >> In my settings.py I have commented out these variables: >> >> # Other security settings >> # SECURE_SSL_REDIRECT = True >> # If you set SECURE_SSL_REDIRECT to True, make sure the >> SECURE_REDIRECT_EXEMPT >> # contains at least this line: >> # SECURE_REDIRECT_EXEMPT = [ >> # "archives/api/mailman/.*", # Request from Mailman. >> # ] >> # SESSION_COOKIE_SECURE = True >> # SECURE_CONTENT_TYPE_NOSNIFF = True >> # SECURE_BROWSER_XSS_FILTER = True >> # CSRF_COOKIE_SECURE = True >> # CSRF_COOKIE_HTTPONLY = True >> # X_FRAME_OPTIONS = 'DENY' >> >> I've been messing with them whith no results. It's like it lacked >> some value in some template... > > > It's not an issue with the code per se or the templates. These updates > are all installed on mail.python.org and lists.mailman3.org and are > working fine. > > After upgrading did you run > > django-admin collectstatic --clear > django-admin compress > django admin migrate Since I made all the mailman3 enviroment wide server open (not using venv) I already executed the migration doing a su -m mailman3 -c "python3 manage.py collectstatic" su -m mailman3 -c "python3 manage.py migrate" Being mailman3 the user who runs all of mailman3 related stuff I had problems doing the migrate part, showing an error of lacking perms. I solved it running the migration under root (I know it could be trouble after, but...) After that the compress part showed errors... but the postorius web maintenance was working well except for the CSRF error verification. I will trace the compress errors and will try to find the problem later. With your point to the CSRF_TRUSTED_ORIGINS parameter, I can now do the accept or discard part of a receiving message to the lists (I put below the config that is working for me). All seems to be working now flawlessly. Thanks once again for your guidance. ############ SESSION_COOKIE_SECURE = True SECURE_CONTENT_TYPE_NOSNIFF = True SECURE_BROWSER_XSS_FILTER = True CSRF_COOKIE_SECURE = True CSRF_COOKIE_HTTPONLY = True X_FRAME_OPTIONS = 'DENY' # CSRF_TRUSTED_ORIGINS = [ "https://*.mydomain-example.xxx", "https://mydomain-example", "https://mydomain", ] ############ > > If you have and it doesn't help, you probably need to add > CSRF_TRUSTED_ORIGINS to your settings.py. > > See > https://docs.djangoproject.com/en/4.1/ref/settings/#csrf-trusted-origins > and note the differences between Django <4.0 and >=4.0. > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 8 months

[MM3-users] Re: Flushing/syncing hyperkitty with mailman

by Eric Abrahamsen

On 06/16/18 19:46 PM, Mark Sapiro wrote: > On 06/16/2018 06:38 PM, Eric Abrahamsen wrote: >> >> >> A bump for this, I've been getting this series of errors once a minute >> for weeks now. There must be some way to clear out dangling thread >> references? And I take it that for the meantime we shouldn't be using >> the "delete thread" feature of hyperkitty... >> >>> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >>> [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] >>> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >>> [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] >>> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >>> [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] >>> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >>> [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] >>> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >>> >>> Is there something more I should be doing to sync hyperkitty's database >>> with mailman? I've got the crontab file in place, and that appears to be >>> running without error. Anything else? > > > Except that 'django-admin runjobs minutely' is probably what's producing > the errors. Yes, I guess that was poorly phrased... > You might try 'django-admin runjob empty_threads' (normally a monthly > job) or 'django-admin runjob thread_order_depth' (normally a yearly > job). I don't know if they will clear this up or not, but I don't think > it would hurt to try. > > See 'django-admin runjob --list' to see the various jobs and note that > 'django-admin runjob update_index' which runs minutely and does an > incremental update is not the same as 'django-admin update_index' which > only runs manually and does a full search index update. I've tried all the above with no luck, and am getting ready to dive a bit deeper. It's been a bit confusing tracking all the code flows. The rebuild_thread_cache_votes error occurs once a minute, at second 21. The rebuild_email_cache_votes error is also once a minute, but at second 56. Am I right that the only job that runs once a minute is the "runjob update_index" command, and that the error must be (eventually) arising from there? Does it seem meaningful that the two errors are offset by around 30 seconds? Lastly, searching the source for the rebuild_(email|thread)_cache_votes functions, they only seem to be called within the "on_vote_added" method of Email and Thread objects, but I don't see how that can be the source of the errors (as the objects in question obviously exist). So it must be update_index, which means I should be looking in haystack (ha) for whatever eventually calls these functions. Does that all sound correct? Thanks for your pointers, Eric

7 years

[MM3-users] Re: Disable archives per list

by Stephen J. Turnbull

Bernd Wurst writes: > Am 25.02.21 um 22:01 schrieb Mark Sapiro: > > Normally a list admin can select which of the enabled archivers is > > active for that list via Postorius. To prevent this, you would have to > > modify Postorius. It would be easy enough to just remove settings from > > the relevant templates. > > This will take effect for all lists at once, I suppose. :( I'm not familiar with the content of Postorius's templates, but they support all of the Django features, so you can filter out the settings for specific lists. It would require code and database schema changes to make that configurable from Postorius, I think. > Hyperkitty has a rather cool frontend but stores all messages from all > lists together in one database table. Additionally, neither Mailman nor > Hyperkitty seems to know or tell anything about archive sizes of a list. > This is horribly for accounting. Mailman core doesn't know anything about archives except where you've told it to send them. Historical note: I'm not saying it was a good idea, but the folks who designed HyperKitty were aiming at the Fedora use-case. There's a fair amount of cross-posting between Fedora lists, so I think this makes sense for them both from the indexing and from the storage point of view. I doubt they were thinking about the hosting perspective. > So I thought if I can have a separate hyperkitty installation per user > without having to duplicate the whole mailman. You could do that, but it requires a separate port or domain for each. If you're already aliasing a server (or a server farm) for virtual domains, then that's no problem. > Alternatively, I'd like to enable archiving only for some customers > that buy a suitable plan. > I did not really get into mailman plugins. I don't think anybody has gotten into them. > Is is possible for plugins to hook into such settings? Since archiving involves getting the message from Mailman core, yes. Plugins can only deal with that end though. Everything else is controlled by the archiver itself. Without a plugin, you could disable archiving somewhat easily by giving each list a different posting pipeline that doesn't have the 'to-archive' handler in it. This wouldn't stop the list admin from configuring, but ... there wouldn't be any archives there. I don't know if that deserves a smiley. :-/ Unfortunately this would be annoying because you'd have to go in and modify for each list. With a plugin, Mailman core could refuse to configure a archive. However, stock Postorius wouldn't know anything about that. It would just see a "refused" response in the REST protocol, but without modifying Postorius, I suspect it would just log and display an error to the user. And without code changes Postorius can't provide a good UI for that. Steve

4 years, 4 months

[MM3-users] Re: Mailman3 on FreeBSD

by John Poltorak

Regarding location of mailman.cfg...FreeBSD adopt a strict directory hierachy https://www.freebsd.org/cgi/man.cgi?hier(7) Anything installed outside the base OS belongs in /usr/local I guess that issue is something for the FreeBSD porters of Mailman3... I'll use /etc/mailman.cfg for the time being but I don't know what should go in it. Can I see an example? The other problem regarding sqlite was solved by pkg install databases/py36-sqlite3 I'll get back to the install docs now. Thanks showing interest. On Sun, Aug 13, 2017 at 2:25 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Sat, 12 Aug 2017 18:10:49 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 08/12/2017 04:51 PM, Barry Warsaw wrote: > > > On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> > > > wrote: > > >> > > >> On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however > > >> I don't see any indication as to what I should put in this file > > >> and if it was in /usr/local/etc/mailman.cfg then how would mailman > > >> find it? > > > > > > It wouldn’t by default. Right now Mailman does not search > > > for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult > > > change to add. I’m not sure whether that would makes sense as a > > > general default or not. I’m not up on the FreeBSD conventions and > > > standards here; can you explain why /usr/local/etc is preferred > > > over /etc on that distro? > > > > > > I was hoping Abhilash would chime in here, because I think John is > > using the docker image and there's probably a specific path for > > mailman.cfg. > > As per his first message, I think John is using the prod setup from the > documentaion[1]. > > I don't have anything much to add on top of what Barry mentioned, it > looks like something is wrong with the Python install and missing > Sqlite3 module. > > The documentation does mention the paths where Core looks for > configuration file and anything else can be specified using -C or > MAILMAN_CONFIG_FILE environment variable. > > [1]: http://docs.mailman3.org/en/latest/prodsetup.html > > > As far as what goes in it, it could even be empty if you want to > > accept all the defaults, but you probably want at least > > > > [mailman] > > site_owner: real_person(a)example.com > > > > I expect if you do > > > > find -name mailman.cfg > > > > in your installation, you'll find at least examples. > > > > thanks, > Abhilash > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

7 years, 10 months

[MM3-users] Re: add custom styles to postorius list creation menu

by mhazan＠mandint.org

Le 2022-05-03 09:44, mhazan(a)mandint.org a écrit : > Le 2022-05-02 17:32, Mark Sapiro a écrit : >> On 5/2/22 06:39, Michael Hazan wrote: >>> Hello, >>> >>> When creating a list via postorius, i can see 3 style appear >>> (announce, discussion, private). Is it possible to either create a >>> new style and add it to that list or modify one of those style ? >> >> >> See this thread >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> > > Thanks i will look into setting up that plugin, hopefully an easier > way to do that can make it's way to the default install. working on that plugin, i have found where to inserts the various setting, however it's not clear what types and possibles value are excepted for each ? ie "advertised" is bool True/false, but what about "default_member_action" ? i've tried hold 'hold' "hold" all throw error when trying to apply the style. i cannot find the types in the documentation and all the other non bool settings. >>> Also, coming from mailman2, you could directly set the members post >>> moderation action when subscribing, now you can only do it via the >>> user menu, is there a way to automate this in mm3 ? >> >> >> I don't understand what you mean here. In MM 2.1 a member had only one >> setting - moderated yes or no and if moderated there was a list >> setting for the moderation action. There was also a list setting for >> whether new members were moderated by default. How were you setting >> the new member's moderation when subscribing? >> >> You are correct that when subscribing a new member, the member gets >> the default action for members and different action has to be set in a >> separate operation. I don't think this is significantly different from >> MM 2.1. Also, can you describe what you mean by "automate this". > > in MM2.1, if you set the list to moderated and default action to hold > posting, you can set a some member to be un-moderated (mod bit off) to > automatically allow their posting. In the web interface of MM2.1 there > is a checkbox with moderated bit on/off on the member list itself, in > the postorius interface for MM3 you have to open each members settings > page to access that. For automation, as list owner, upon registering a > member (via mass subscription) the possibility to change that ? also > the me too/dupe setting for example. > > Thanks > _______________________________________________ > 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/

3 years, 1 month

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Thank you very much Abhilash! Could you set up 'latest' tag in postotius repo <https://hub.docker.com/r/maxking/postorius/tags> please - as it exists for core/web? I'd like to have consistent approach across the images... Also it would be really great to extend image labelling used for *quay.io/maxking/mailman-*:rolling <http://quay.io/maxking/mailman-*:rolling>* images to Docker Hub ones... Version identification is quite hard for Docker... With my best regards, Danil сб, 2 мар. 2019 г. в 03:19, Abhilash Raj <maxking(a)asynchronous.in>: > > > On Thu, Feb 28, 2019, at 10:18 PM, Danil Smirnov wrote: > > Hi Abhilash, > > Thank you very much - the previous error is fixed now. > > But I have another one now, which causes the same 500 Server Error: > > bash-4.3# cat /opt/mailman-web-data/logs/uwsgi-error.log > *** Starting uWSGI 2.0.18 (64bit) on [Fri Mar 1 05:42:09 2019] *** > compiled with version: 6.3.0 on 01 March 2019 01:52:42 > os: Linux-3.10.0-693.11.1.el7.x86_64 #1 SMP Mon Dec 4 23:52:40 UTC 2017 > nodename: mailman-web > machine: x86_64 > clock source: unix > detected number of CPU cores: 2 > current working directory: /opt/mailman-web > detected binary path: /usr/local/bin/uwsgi > !!! no internal routing support, rebuild with pcre support !!! > setgid() to 101 > setuid() to 100 > chdir() to /opt/mailman-web > your memory page size is 4096 bytes > detected max file descriptor number: 1048576 > building mime-types dictionary from file /etc/mime.types...1168 entry found > lock engine: pthread robust mutexes > thunder lock: disabled (you can enable it with --thunder-lock) > uwsgi socket 0 bound to TCP address 0.0.0.0:8080 fd 8 > uwsgi socket 1 bound to TCP address 0.0.0.0:8000 fd 9 > Python version: 3.6.8 (default, Jan 30 2019, 23:58:16) [GCC 6.3.0] > Python main interpreter initialized at 0x55a2df7f57e0 > python threads support enabled > your server socket listen backlog is limited to 100 connections > your mercy for graceful operations on workers is 60 seconds > mapped 166752 bytes (162 KB) for 2 cores > *** Operational MODE: threaded *** > Traceback (most recent call last): > File > "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", > line 20, in import_string > return getattr(module, class_name) > AttributeError: module 'django.contrib.auth.middleware' has no attribute > 'SessionAuthenticationMiddleware' > > The above exception was the direct cause of the following exception: > > Traceback (most recent call last): > File "wsgi.py", line 38, in <module> > application = get_wsgi_application() > File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line > 13, in get_wsgi_application > return WSGIHandler() > File > "/usr/local/lib/python3.6/site-packages/django/core/handlers/wsgi.py", line > 136, in __init__ > self.load_middleware() > File > "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line > 34, in load_middleware > middleware = import_string(middleware_path) > File > "/usr/local/lib/python3.6/site-packages/django/utils/module_loading.py", > line 24, in import_string > ) from err > ImportError: Module "django.contrib.auth.middleware" does not define a > "SessionAuthenticationMiddleware" attribute/class > unable to load app 0 (mountpoint='') (callable not found or import error) > *** no app loaded. going in full dynamic mode *** > *** uWSGI is running in multiple interpreter mode *** > spawned uWSGI master process (pid: 1) > spawned uWSGI worker 1 (pid: 37, cores: 2) > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > --- no python application found, check your startup logs for errors --- > > As per my investigation, this error possibly caused by Django upgrade: > > *The SessionAuthenticationMiddleware class is removed. It provided no > functionality since session authentication is unconditionally enabled in > Django 1.10.* > > See https://docs.djangoproject.com/en/2.0/releases/2.0/ > > After I've removed the line > > https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > from settings.py, the container is finally working. > > I've placed PR in github: > https://github.com/maxking/docker-mailman/pull/314 > > > Thank you for your contributions! > > I have merged your pull request and it should now be out (hopefully!). > > > Thank you for your help. > > Danil > > > пт, 1 мар. 2019 г. в 04:33, Abhilash Raj <maxking(a)asynchronous.in>: > > > > On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: > > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> > wrote: > > >Hi Mark, > > > > > >Actually all this stuff happens inside the container after it's started > > >and > > >initialized without errors. I didn't amend the image anyhow. > > > > > >Also I have the configuration based on docker-compose.yaml provided in > > >the > > >repository which works just fine for mailman-web image. > > > > > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) > > >fails > > >with 500 error... > > > > > >Now answering your questions: > > > > > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > > > > > >> do you have django-q in INSTALLED_APPS in your Django settings and > > >what > > >> is set for Q_CLUSTER? > > >> > > > > > >I've checked settings.py inside the container and I haven't found any > > >of > > >the mentioned configurations there. > > > > > >Does the manage.py that's being run here point to the right > > >settings.py? > > >> > > > > > >No clue. > > > > > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK > > >configured image? > > > > > > > https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > > > > Because I am a dum dum ;-) > > > > Will work on removing those crons and stuff. Would be nice if you > > opened an issue on Github so that I don't forget. > > Should now be fixed in the latest image. > > > > > >Danil > > > > > > > > > > > >> -- > > >> 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/ > > > > > > -- > > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > thanks, > Abhilash Raj (maxking) > > > -- > thanks, > Abhilash Raj (maxking) > > >

6 years, 3 months

[MM3-users] Re: HyperKitty async tasks runner: systemd qcluster service fails eventually

by actionmystique＠gmail.com

Mark Sapiro wrote: > Did you replace <django_project_path>, <user> and <group> with > appropriate values? Yes, I did, otherwise qcluster service would not be able to start in the first place because it needs to be able to read settings.py (with the proper permissions) which is located in the django project. > They should be the same thing. Usually manage.py is just configured to > run the django-admin command for the particular project. You're right, running either command manually is successful and lead to the same result: ``` <django_project_path># python3 manage.py qcluster 10:49:41 [Q] INFO Q Cluster-1130205 starting. 10:49:41 [Q] INFO Process-1:1 ready for work at 1130235 10:49:41 [Q] INFO Process-1:2 ready for work at 1130236 10:49:41 [Q] INFO Process-1:3 ready for work at 1130237 10:49:41 [Q] INFO Process-1:4 ready for work at 1130238 10:49:41 [Q] INFO Process-1:5 monitoring at 1130239 10:49:41 [Q] INFO Process-1 guarding cluster at 1130234 10:49:41 [Q] INFO Q Cluster-1130205 running. 10:49:41 [Q] INFO Process-1:6 pushing tasks at 1130240 ``` If I replace: ``` ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings ``` with: ``` WorkingDirectory=<django_project_path> ExecStart=python3 manage.py qcluster ```` I get the same systemd service issue. If I remove the ``` remote-fs.target``` from ```After=...```, I get the following error: ``` # systemctl daemon-reload # systemctl restart qcluster # systemctl status qcluster ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-12-05 11:08:54 CET; 282ms ago Main PID: 1132324 (python3) Tasks: 1 (limit: 9284) Memory: 22.5M CGroup: /system.slice/qcluster.service └─1132324 python3 /usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: File "/usr/lib/python3/dist-packages/django/utils/log.py", line 76, in configure_logging Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: logging_config_func(logging_settings) Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: File "/usr/lib/python3.7/logging/config.py", line 800, in dictConfig Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: dictConfigClass(config).configure() Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: File "/usr/lib/python3.7/logging/config.py", line 571, in configure Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: '%r' % name) from e Dec 05 11:08:54 samsung4-ubuntu django-admin[1132324]: ValueError: Unable to configure handler 'file' Dec 05 11:08:54 samsung4-ubuntu systemd[1]: qcluster.service: Main process exited, code=exited, status=1/FAILURE Dec 05 11:08:54 samsung4-ubuntu systemd[1]: qcluster.service: Failed with result 'exit-code'. ``` This issue seems related to logging; I configured the following in ```/etc/mailman3/mailman.cfg```: ``` [logging.debian] format: %(asctime)s (%(process)d) %(message)s datefmt: %b %d %H:%M:%S %Y propagate: no level: debug path: mailman.log [logging.root] level: debug [logging.archiver] level: debug [logging.bounce] level: debug [logging.config] level: debug [logging.database] level: debug [logging.debug] level: debug [logging.error] level: debug [logging.fromusenet] level: debug [logging.http] level: debug [logging.locks] level: debug [logging.mischief] level: debug [logging.plugins] level: debug [logging.runner] level: debug [logging.smtp] level: debug [logging.subscribe] level: debug [logging.vette] level: debug ```

5 years, 6 months

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

On Thu, Sep 30, 2021 at 1:59 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Sep 29, 2021, at 2:34 PM, Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > > > > On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 9/29/21 9:50 AM, Odhiambo Washington wrote: > >>> 1. Confirmation emails to Users has wrong domain name (example.com!) > >>> <https://docs.mailman3.org/en/latest/faq.html#id1> > >>> < > >> > https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… > >>> > >>> > >>> This happens when your reverse (SSL) proxy isn’t setting up the correct > >>> headers when proxying requests. Fix this by setting the right > >>> proxy_set_header directives: > >> ... > >>> How is this supposed to be mitigated in Apache when using WSGI? > >>> > >>> My config: > >>> > >>> WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > >>> user=mailman group=mailman > >>> WSGIPythonHome "/usr/local" > >>> WSGIProcessGroup hyperkitty > >> > >> > >> You are using mod_wsgi and not proxying at all, so this is not relevant > >> in your case. > >> > >> Are you actually seeing this issue? If so, it might be related to > >> > >> > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > >> > > > > My issue is related to this, but the documentation referred to is not for > > the faint-hearted! > > I can't make head or tails of it. > > Click on “Domain” in Postorius from the top bar, which should take you to > the Domains page. > > For your domain (in the “Mail Host” column), see the corresponding “Web > Host” column, it should look something like: > > lists.mailman3.org (lists.mailman3.org) > (Edit) > SITE_ID = 1 > Mine looks different, slightly. But there is no example.com at all. [image: Abhilash.png] > > on a new-ish version of Postorius. > I have the newest versions of everything, having installed only yesterday. > > If it doesn’t show the right values and instead shows “example.com” for > you, click on the “Edit” link, which will take > you to a page that will allow you to edit both the values. > It shows the right values, but with "SITE_ID = 2". In my settings_local.py I have SITE_ID = 1. I suppose the example.com is the one tied to SITE_ID = 1 and that is what I have in my settings_local.py. Should I edit my settings_local.py? I am still confused. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 9 months

[MM3-users] Re: possible backscatter attack using Mailman3 servers

by Odhiambo Washington

On Sat, Jan 4, 2025 at 5:30 AM David Newman <dnewman(a)networktest.com> wrote: > > > On 1/3/25 5:44 PM, Mark Sapiro wrote: > > >> Greetings. On a system running Mailman 3.3.9 and Postfix, I'm seeing > >> about 20-30 entries per day in the Postfix queue where it appears a > >> Gmail user signs up for a mailing list that requires confirmation, and > >> Gmail responds that the user is too busy to handle requests. > >> > >> There are no publicly advertised email lists on this server, and I > >> don't ever see anything in the Mailman logs indicating the user ever > >> tried signing up. > > > > > > This is an attack mail bombing the user. The requests that result in the > > can come via web or email. Mailman's logging of subscribes has been > > missing most events through Mailman 3.3.10. See https://gitlab.com/ > > mailman/mailman/-/issues/1143 which will be fixed in 3.3.11, but > > subscribes waiting user confirmation still won't be logged. > > > > However, the message with subject "Please Confirm Your Email Address" > > comes from Django allauth so it isn't actually Mailman sending it but > > rather Django allauth as a result of a request to sign up for a Django > > account at https://mail.example3.com/accounts/signup/. You can probably > > find that request in your web server logs, and you may find the user > > and/or email in the Django admin UI. > > Thanks VERY much for this. > > No such users in the Django UI, but the web server logs have 252 > attempts from 132 unique IPv4 addresses registered to different ISPs > throughout Europe. > > So, even though Mailman support for more detailed logging of sub and > unsub requests would be useful, it likely would not have helped with > attacks from many source IP addresses. > > > > > Since django-mailman3 1.3.6, you can disable these signups by putting > > > > ACCOUNT_ADAPTER = > 'django_mailman3.views.user_adapter.DisableSignupAdapter' > > > > in your Django settings, but then your users won't be able to sign up > > for web accounts. > > I have made this change. As for not having web accounts, this just means > new users cannot sign up to manage their Mailman settings, correct? I > presume existing web accounts will continue to work. > You could also try this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… It really helped in many cases, although with the change you already made, it becomes a useless effort. -- 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]

5 months, 3 weeks

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

Mark, Thank you for your thoughts so far. On 6/23/20 3:22 PM, Mark Sapiro wrote: > I have done further testing. See my comment at > <https://gitlab.com/mailman/mailman/-/issues/735#note_366074014>. > > You need to set hostname: in mailman.cfg to the actual external IP > address of the Mailman host machine or to a name which resolves to that > IP both internally and externally, and also set that host name/IP in the > MAILMAN_REST_API_URL setting on the Postorius machine. I've done that, but there is no observed change in the browser (still get same 404 error). Specifically, I reset hostname to be a newly-added CNAME of the actual host address, and ensured that the 0.0.0.0 addresses were no longer there. > >> However I then get another issue. From the mailman.log file I now see in >> the last few lines. For clarity I've numbered them like this "{1}": >> >> {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" >> "GNU Mailman REST client v3.3.1" >> {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk >> HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" >> {3} [22/Jun/2020:00:58:24 +0000] "GET >> /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 >> HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" >> >> At this point the browser screen reports "Something went wrong" and the >> message "HTTP Error 404: {"title": "404 Not Found"}" > Make the above changes and see if that solves this. If not, let us know > and we'll try to help. A tcpdump now shows the GET of /3.1/domains/mailman-web.ivimey.org/lists&advertised=true&count=0&page=1 directed at mailman-core and the reply being 404 not found. The extract from core's mailman.log is now: [24/Jun/2020:20:41:11 +0000] "GET /3.1/domains/mailman-web.ivimey.org/lists?advertised=true&count=0&page=1 HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" And the entry for postorius in mailmansuite.log: ERROR 2020-06-24 21:41:11,191 13310 postorius Un-handled exception: HTTP Error 404: {"title": "404 Not Found"} Traceback (most recent call last): File "/opt/mailman3/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) [snip] File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 116, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"} Note that the mailman-web.ivimey.org address is the newly-added CNAME of greyarea-web1, mailman-core is likewise the CNAME of greyarea-post. There is nothing I can see in the other logs that looks out of the ordinary. I guess this indicates that my earlier wondering if I had something left over from a past install is dispelled, as that name didn't exist until today.

5 years

Search results for query "sapiro"