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

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Thomas G

Hi, https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/incoming.p… I changed "sender" for this; # Sender try: from_str = header_to_unicode(message['From']) from_name, from_email = parseaddr(from_str) from_name = unidecode.unidecode(from_name).strip() except (UnicodeDecodeError, UnicodeEncodeError): raise (ValueError("Non-ascii sender address", message)) try: sender_address = from_email.encode('ascii').decode("ascii").strip() except (UnicodeDecodeError, UnicodeEncodeError): if from_name: sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) if not sender_address: sender_address = "unknown(a)unknown.com" else: sender_address = "unknown(a)unknown.com" print("Non-ascii sender addre -- Sender address replaced by ", sender_address) I got this output (example): |Non-ascii sender address -- Sender address replaced by stephaneblipblopstlablipblopgmailcom It's not really perfect, I'm working to do something better, but basically it's works. I think that there is a issue in the original code: Because : "" raise ValueError("Non-ascii sender address", message) "" The second part will be never call: if not sender_address: if from_name: sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) if not sender_address: sender_address = "unknown" sender_address = "{}(a)example.com".format(sender_address) else: sender_address = "unknown(a)example.com" If you bypass : "" raise ValueError("Non-ascii sender address", message) "", by a simple print(), you will get an error due to an unassigned variable (sender_address). Le mar. 30 oct. 2018 à 04:10, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/28/18 12:03 PM, Guiseppin Thomas wrote: > > Hi, > > > > I imported some mbox archives in Hyperkitty. > > > > I have lot issues like: > > > > /\Failed adding message <5b0900ab.1c69fb81.70ab.2f87(a)mx.google.com>: > > ('Non-ascii sender address', <email.message.EmailMessage object at > > 0x7f05f1606048>)// > > //Non-ascii sender address from "Stéphane blipblop <stlablipblop at > > gmail.com>" about [HATLAB][It] Re: A débarrasser ! / > > > > It's probably because "Stéphane". > > > The 'Non-ascii sender address' message comes from > > > try: > > from_str = header_to_unicode(message['From']) > > from_name, from_email = parseaddr(from_str) > > from_name = from_name.strip() > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > raise ValueError("Non-ascii sender address", message) > > Possibly the exception is thrown in parseaddr(), but much more likely, > the email address, not the display name contains non-ascii. > > > Some advise to fix it ? > > > All the other messages should have been imported. If you can find and > fix the 'bad' ones in the mbox, you can make a new mbox with just those > and import that. You could also import the entire mbox with fixed > messages. The already added ones won't be re-imported because of > duplicate Message-ID:, but it's extra processing. > > If the actual bad message From: header is > > From: Stéphane blipblop <stlablipblop(a)gmail.com> > > or > > From: Stéphane blipblop <stlablipblop at gmail.com> > > That shouldn't cause the error, so I'g guessing that 'blipblop' is not > the actual value and the actual value in <stlablipblop at gmail.com> has > non-ascii. > > -- > 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/ >

6 years, 8 months

[MM3-users] Re: templates

by Christian

From bounce.log May 05 07:59:00 2023 (765) Member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 07:59:00 2023 (765) Member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:01:00 2023 (765) Member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 08:01:00 2023 (765) Member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:11:01 2023 (765) Member vortexanthony(a)hotmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 1. May 05 08:13:01 2023 (765) Member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 08:13:01 2023 (765) Member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:15:01 2023 (765) Probe bounce received for member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:01 2023 (765) Disabling delivery for juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:15:02 2023 (765) Probe bounce received for member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:02 2023 (765) Disabling delivery for alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:15:02 2023 (765) Probe bounce received for member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:02 2023 (765) Disabling delivery for baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:17:02 2023 (765) Residual bounce received for member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:17:02 2023 (765) Residual bounce received for member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:17:02 2023 (765) Residual bounce received for member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, May 5, 2023 4:39 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/5/23 15:27, Christian via Mailman-users wrote: > Okay I sent a test message this morning and subscribers are reporting > they did not receive it. The smtp.log shows 'smtp to > degrowcali(a)lists.ccalternatives.org for 25 recips, completed in > 3276.275292634964 seconds' (see below) I alone received it however and > it is listed in the archive. Below is the excerpt from smtp.log. Two > of my 5 lists are exhibiting this behavior, while > 2 other lists are working normally. Please advise. Thank you. That message says Mailman delivered the message for 25 recipients to the outgoing MTA. If only one recipient received it, you first need to check the outgoing MTA's logs to see whether the message was delivered to the recipient's mail servers or not. Those logs should indicate that either the message was delivered to each recipient's first hop mail server or not. If not, there should be a reason why in the logs. If the message was delivered, it could have been rejected by an MTA further down stream in which case a DSN message should be returned, but possibly not for days, or it could have been delivered to the user's spam/bulk/junk/promo/whatever folder or silently discarded. Do your list's do bounce processing? If so, what's in Mailman's bounce.log? -- 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/ XI52IZUTFWKEFTWELYVVG2MHQ53J65DF/ This message sent to csa(a)web-analysts.net

2 years, 2 months

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Friday, November 3, 2017 2:27:03 PM EST Mark Sapiro wrote: > How about "user that installed Mailman" or "user that Mailman's runners > run as"? I installed it as root. From "man useradd" in Linux: -r, --system Create a system account. System users will be created with no aging information in /etc/shadow, and their numeric identifiers are chosen in the SYS_UID_MIN-SYS_UID_MAX range, defined in /etc/login.defs, instead of UID_MIN-UID_MAX (and their GID counterparts for the creation of groups). Note that useradd will not create a home directory for such an user, regardless of the default setting in /etc/login.defs (CREATE_HOME). You have to specify the -m options if you want a home directory for a system account to be created. Pierre -- lo ponse be lo mruli ku po'o cu ga'ezga roda lo ka dinko

7 years, 8 months

[MM3-users] Re: Starting from scratch

by Benjamin Ragheb

On Tue, Apr 10, 2018, at 12:14 AM, Mark Sapiro wrote: > If you are comfortable with 2), I think that's the better option. After > PyCon in May when we release 3.2 and the rest of the suite, you should > be able to install everything with pip and have it work. I'm not sure > what the issues are now with a pip install. Thanks, Mark. It wasn't clear to me by poking around how stable/unstable the master branches were, but if you think they should be stable enough for a hobby server, that's good enough for me. If I get things working and I'm feeling bold enough to contribute back to the documentation, are there guidelines? The Contributor Guide covers the technical stuff... should I just submit a merge request in GitLab? -- Ben

7 years, 2 months

[MM3-users] Re: mailman start - can't open file

by Mark Dale

Thanks for the pointer Mark. I've edited mailman.cfg as follows and all is well. [paths.local] var_dir: /var/tmp/mailman bin_dir: /usr/local/bin log_dir: $var_dir/logs lock_dir: $var_dir/locks data_dir: $var_dir/data cache_dir: $var_dir/cache etc_dir: $var_dir/etc messages_dir: $var_dir/messages archive_dir: $var_dir/archives template_dir: $var_dir/templates pid_file: $var_dir/master.pid lock_file: $lock_dir/master.lck [mailman] layout: local Best, Mark On 8/2/19 2:03 am, Mark Sapiro wrote: > On 2/6/19 9:58 PM, Mark Dale wrote: >> Hi All, >> >> On a new installation (pip), when starting Mailman it seems it cannot >> find the "master" file. Have I missed a configuration somewhere that >> tells it to look in "/usr/local/bin" rather than "/usr/bin"? > > > See > <http://docs.mailman3.org/en/latest/config-core.html#configuring-filesystem-…>. >

6 years, 5 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Odhiambo Washington

On Mon, Jan 30, 2023 at 9:01 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 09:46, Odhiambo Washington wrote: > > > > So, if I understand this correctly, there is no need for the addition of > > this parameter: > > > > ``` > > configuration: /path/to/postfix-mailman.cfg > > ``` > > to the mta config block in mailman.cfg in a non-docker environment, or > when > > only using hash tables?? > > > Correct. > Great. So, since the creation of that file is prominent in the doco, maybe a note can be added to that effect? Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Am 15.06.23 um 00:34 schrieb Mark Sapiro: >> - Then I tried settings_local.py with: >> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' > > > That is the correct place. It should work. Did you restart the container > after making this change? > Mh, unfortunately it does not work. - I changed the file and rebuilt the container. - I also restarted all 3 containers again. - I checked in the container the settings_local.py to verify that the change "arrived" and found it. - It still sends the "reset-password"-email with postorius@$SERVE_FROM_DOMAIN as shown in the screenshot. Is there any other way to test or check it? Any more ideas? Thank you in advance. ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: image/png Name: Bildschirmfoto_2023-06-15_22-55-29.png

2 years

[MM3-users] Use WHAT-WG decoding strategy? [was: Another interesting error...]

by Stephen J. Turnbull

Mark Sapiro writes: > > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: > > illegal multibyte sequence I'm pretty sure 0x87 is reserved by the later GBK standard (implemented as an encoding in GB18030) as a prefix for extensions. This is a common problem with Chinese and Japanese encodings: junky email clients use "traditional" names denoting encodings with smaller repertoires to denote modern encodings. I wonder if we shouldn't just promote all gb* to gb18030 and all Shift JIS to the most recent version, as in the WHAT-WG web encodings standard. If nobody says "that's really stupid", I'll write up a RFE later this week. I think there's already a module on PyPI we can use to implement. Steve

7 years, 2 months

[MM3-users] Re: Reset digest number and volume

by Andrew Bernard

HI Mark, I get: >>> commit() Traceback (most recent call last): File "<console>", line 1, in <module> NameError: name 'commit' is not defined Andrew On 26/6/19 11:49 pm, Mark Sapiro wrote: > On 6/26/19 3:08 AM, andrew.bernard(a)gmail.com wrote: >> How to do this? After lots of testing on my pre-release beta testing list, I want the first production digest to be reset toVolume 1, Number 1. > > You can do this in `mailman shell` by setting the list's `volume` and > `next_digest_number` to 1. E.g., > > > $ ./mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > The variable 'm' is the list(a)example.com mailing list >>>> m.volume = 1 >>>> m.next_digest_number = 1 >>>> commit()

6 years

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 28, 2020, at 4:56 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/28/20 4:39 PM, Mark Dadgar wrote: >> >> The patch does not apply cleanly against /usr/lib/python3/dist-packages/hyperkitty/models/email.py >> >> patching file email.py >> patch: **** malformed patch at line 4: import os > > > That probably isn't because of version mismatch. That would give applied > at offset or with fuzz or a reject. malformed patch means the patch file > is not formatted correctly. Here it is again as an attachment. That may > help. That gives a slightly different error: mark@mail:/usr/lib/python3/dist-packages/hyperkitty/models$ sudo patch < /tmp/patch.txt patching file email.py Hunk #1 FAILED at 24. patch: **** malformed patch at line 23: - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years

Search results for query "sapiro"