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

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Thor Atle Rustad

I go with the workaround from Cameron Smith: sudo docker-compose exec mailman-web ./manage.py runjobs yearly makes messages appear However, there was "something" else that caused my messages not only NOT to show up in Hyperkitty, but also caused them not to be sent in the first place. I believe the reason was wrong subdomain in SERVE_FROM_DOMAIN in docker-compose.yaml. 2017-11-22 0:38 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 11/21/2017 01:53 AM, Thor Atle Rustad wrote: > > I have had this working before, so I guess it's a simple setup error. > > > > When I send a message from the Postorius interface, it is neither sent > out > > or stored. I briefly see this message: "Your reply has been sent and is > > being processed.", and then nothing happens. > > > I assume you mean HyperKitty. Postorius has no facility for posting > messages to a list. > > > > I have installed maxking's docker-mailman and copied my old setup with > > basic stuff like passwords and such. The only new thing is that I'm now > > running in userspace by putting in /etc/subuid and subguid: > > > When you post from HyperKitty, HyperKitty creates a > django.core.mail.EmailMessage() instance and calls it's send() method > which causes Django to send the message to the list address. It then has > to be received and processed by Mailman the same as any email post > before it will appear in the archive. > > Are you running with DEBUG = True. If so, Hyperkitty won't send the mail. > > If DEBUG = False and normal posting is working, perhaps there is some > Postfix issue in delivery of the message from Django to Mailman. > > -- > 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/ >

7 years, 6 months

[MM3-users] Re: at the finish line of mailman3 docker, but can't sign in.

by Abhilash Raj

On Fri, Jul 30, 2021, at 11:01 AM, Mark Sapiro wrote: > On 7/30/21 10:47 AM, bob B wrote: > > > > Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? > > > I'm not sure what the actual command would be do run the django-admin > interface in the docker image, but from below, it looks like it's > `mailman-web`. Run `mailman-web createsuperuser` to create an admin ID. Container images don't support mailman-web command yet, it has to be ported to use the mailman-web command. You can run commands with `docker exec -it mailman-web ./manage.py <command>`. For creating the superuser, you can run[1] [1]: https://asynchronous.in/docker-mailman/web.html#running Although, if you have set the MAILMAN_ADMIN_EMAIL, that command should have already run in the setup process. You want to figure out the email sending process. Although, you can create a second admin and set the password for it and login using that using the command mentioned at [1]. > > > > Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. You can run docker exec -it mailman-web ./manage.py sendtestemail youremailid@domain > > This command tries to send the mail via SMTP to localhost port 25. > > > > How can I make sure my containers can send and receive mail? > > > The MTA should be listening on port 25 and that need to be visible in > the mailman-web container. See > <https://asynchronous.in/docker-mailman/#setting-up-your-mta> > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

3 years, 10 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/17/19 6:39 PM, paul(a)arenson.org wrote: > > A) Thoughts before summarizing tests. > 1) I had originally thought of making archives only for subscribers to give them the benefit of posting from the archives directly and being able to find stuff more like a forum (email is always hard to follow). Anyone logged in to an account can post from Hyperkitty. Their post is treated the same as if they posted by email. > 2) But in retrospect it seems people can get an idea what the list is about from free access. So that is now what I have. OK > 3) On the other hand, it is a bit confusing that a non member can post from the archives without realizing that they need to register, with my settings I can moderate and decide if I want to add him or her to the list based on whether that is spam or not. So ok. A non-member is a non-member. A post from a non-member is handled according to "Default action to take when a non-member posts to the list" unless that non-member has a Moderation action other than List Default. > B) THE TESTS > I was testing too many variables so, to simplify things, I made my settings as follows > > 1) Subscription—> Confirm > > 2) Message Acceptance—> Default processing (so only members may post) > > 3) Testing Procesure > I added people three ways—> To do that I created 3 unique addresses to see if they can send and receive by email. > > > 3a) subscribe without creating an account—from here (bottom) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > 3b) Subscription / Unsubscription from same page, navigate to Login and again navigate to signup > Comment 1: Confusing because even after creating an account, they are not subscribed to the list. Maybe it makes sense if a person has many lists, but I only have this one. It does not say clearly that one has to subscribe after creating an account. I understand it's not totally explicit, but it says "To subscribe or unsubscribe from this list, please log in first. If you have not previously logged in, you may need to set up an account with the appropriate email address." To me the implication is once you have created an account, you have to come back, log in and subscribe. What do you want it to say? > Comment 2: The other thing is that it does not show my domain but that of mailman3.emwd.com <http://mailman3.emwd.com/>. Talk to Brian (emwd) > 3c) Mass Subscribe by me. Which is what I intend for my 600 users from another list company. > Comment This worked fine. > > > C) Summary > 1) I have been thinking of having an account as a good way to get users used to using the archives as a way to confirm current and past topics (as opposed to keeping track by email. But it seems I need to tell them to BOTH subscribe AND create an account. Am I thinking about it the wrong way? That's correct. They need an account and they need to subscribe that account to the list. > 2) When a person wants to unsubscribe, they go to discuss-request(a)list.tokyoprogressive.org <mailto:discuss-request@list.tokyoprogressive.org> with subject bline help. > > a) Isn’t there a better way to unsubscribe by email? email to discuss-leave(a)list.tokyoprogressive.org (or discuss-unsubscribe(a)list.tokyoprogressive.org) Or you can login, go to https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… and click the big red unsubscribe button. > b) And how about a way to remove their account itself? Log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/ and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/delete -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[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.

3 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

7 years, 10 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

4 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)

6 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>

4 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

3 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

5 years, 2 months

Search results for query "sapiro"