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

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Odhiambo Washington

On Sun, May 7, 2023 at 8:52 PM Volkmar Grote <volkmar(a)grote-family.com> wrote: > Hi Mark, > > On 07.05.23 01:31, Mark Sapiro wrote: > > On 5/6/23 16:02, volkmar(a)grote-family.com wrote: > >> > >> My urls.py: > >>> (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py > >>> from django.contrib import admin > >>> from django.urls import include, reverse_lazy, re_path > >>> from django.views.generic import RedirectView > >>> > >>> urlpatterns = [ > >>> re_path(r'^$', RedirectView.as_view( > >>> url=reverse_lazy('list_index'), > >>> permanent=True)), > >>> re_path(r'^postorius/', include('postorius.urls')), > >>> re_path(r'^hyperkitty/', include('hyperkitty.urls')), > >>> re_path(r'', include('django_mailman3.urls')), > >>> re_path(r'^accounts/', include('allauth.urls')), > >>> # Django admin > >>> re_path(r'^admin/', admin.site.urls), > >>> ] > > > > > > We and the various docs are inconsistent about 'postorius' vs > > 'mailman3' and 'hyperkitty' vs 'archives' in urls. Add these > > > > re_path(r'^mailman3/', include('postorius.urls')), > > re_path(r'^archives/', include('hyperkitty.urls')), > > > > to your urlpatterns list in urls.py to cover both variants. > > > thanks for the quick reply. > I am one step closer to a solution, > "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. > I get the functionality, but it looks ugly w/o any graphics, for which I > get yet another, slightly similar, error message: > > > > > > Page not found (404) > You can run: '/opt/mailman/mm/bin/django-admin clear_cache' as the mailman user. After that you can also restart Nginx, then test again and see if everything works. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 years, 2 months

[MM3-users] Re: Installation Questions [Installation}

by Odhiambo Washington

On Mon, Nov 4, 2024 at 10:34 AM Gerald Vogt <vogt(a)spamcop.net> wrote: > Hi, > > On 04.11.24 02:06, Mark Sapiro wrote: > > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > > We should probably cover this in the docs, but for /etc/mailman3, you > > should do > > ``` > > sudo mkdir /etc/mailman3 > > sudo chown mailman:mailman /etc/mailman3 > > sudo chmod 755 /etc/mailman3 > > ``` > > Then you can create all the subordinate files as the mailman user. For > > other things like the systemd service and the postfix and web server > > configs, you need to do them as root (via sudo). > > is it really necessary that the mailman user can write that directory? > For most services, directories and files in /etc/ may be readable for > the service but usually not writable as you don't want the service > itself change it's core configuration. > > On your server it looks like this: > > # ls -la /etc/mailman3 > total 28 > drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . > drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. > -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf > -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg > -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg > -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py > > and it works just fine. > True, but making the mailman user own the files makes life easier when you operate from the virtualenv - you do not have to exit the virtualenv to edit the files in /etc/mailman3, and then re-enter the virtualenv. You do not have to give the mailman user sudoer rights. That's the whole point about the below: ``` sudo mkdir /etc/mailman3 sudo chown mailman:mailman /etc/mailman3 sudo chmod 755 /etc/mailman3 ``` -- 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]

1 year, 8 months

[MM3-users] Bounce of HCL Notes invitations - CloseBoundaryNotFoundDefect() - 501 Message has defects (in reply to end of DATA command)

by Stephen J. Turnbull

Ulf R. writes: > >>> msg.defects > [CloseBoundaryNotFoundDefect()] This means that the message declares a MIME multipart Content-Type, and some part had a "start" boundary line but no "end" boundary line. > Is there a quick fix for this available? No. If the sending software isn't quite broken, this defect means that a chunk of the message was lost somewhere. Ignoring this kind of defect is obviously a bad idea, and any other fix (on the Mailman side) requires knowing precisely what's causing the defect to be detected. > Is it a problem of the python code or the format of the HCL Notes > Server? Nothing's impossible, but I would bet that the problem is in the HCL Notes format. The MIME multipart spec goes back to the early 1980s, and I'm sure the Python Email package implements it exactly by default. I can't say more without the exact MIME structure of a message that causes this error, preferably the whole message (header and body). That said, it might be something that (a) can be worked around with a slightly more lenient existing email policy, or (b) that we could create a new policy that ignores the problem. > In the .eml file I see 25 header fields calles "X-Notes-Item". May > be it is an overflow? Extremely unlikely. All header fields have been successfully processed by the time a CloseBoundaryNotFoundDefect can be detected, and the copy of the field you provide in your followup email is well-formed and contains no interesting content (such as non-ASCII characters, even after decoding the MIME-words). I cannot say why removing the first instance of the field would resolve the error without seeing the whole message. > Any ideas? Not without the full message. If you're not comfortable sending the message to the list, but do trust us enough, you can send a message that causes the error to me and/or Mark Sapiro <mark(a)msapiro.net>. Regards, Steve

1 year, 4 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote: > > > > > On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > > > On Sat, 13 Mar 2021 14:46:55 -0500, > > Mark Sapiro wrote: > >> > >> On 3/13/21 11:14 AM, John Covici wrote: > >>> > >>> Now one thing came up while trying to create the database, I got a > >>> traceback complaining about a revision error because gentoo had a > >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I > >>> upgrade mailman, am I going to have to do something to the database as > >>> well and why should the database have some kind of reference to the > >>> mailman version? > >> > >> > >> I don't know why this is an issue. You shouldn't need to do anything > >> with the database when you upgrade. Please post the full traceback and > >> error message. > > > > Sorry I can't reproduce it, after dropping and recreating the database > > the error went away, but it was in alembic and it was talking about an > > invalid revision and gave a long hex string. > > > > > My guess is that you updated the database (perhaps, by invoking the mailman > command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes > up and sees a new revision for the database migration added from 3.3.3 but > can’t find the same migration in its source (because it is 3.3.2). That is sort of what happened, except in the opposite direction, it was from 3.3.3 to 3.3.2. My question is therefore, do I have to update this alembic_version when I upgrade mailman to a newer version? That is what I was getting at. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 4 months

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Mark Dadgar

On Nov 4, 2021, at 3:05 PM, Andreas Barth <aba(a)ayous.org> wrote: > * Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: >> >> >> --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro >> <mark(a)msapiro.net> wrote: >> >>> On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: >>>> >>>> My conclusion: >>>> I ask you to consider these experiences in an update for the mailman3 >>>> packages in debian bullseye. It would save time, questions and nerves. >>> >>> >>> Issues with Debian packaging should be directed to Debian. >> >> Or as previously discussed, the debian packages should be avoided entirely. > > I strongly disagree with that statement. > > Distribution packages have their own up- and downsides. Of course, how > they are done is to be discussed with the distribution, so: if > something is wrong with a debian package, please follow the > instructions on bugs.debian.org on reporting bugs. > > However, they have the advantage that they're integrated with the > distribution. They have the disadvantage that they're stable for some > time - that is why it's called a stable release. If they have all the > features someone wants, they usually work fine (and my first > mm3-installation was the default debian package). If one looks for > bleeding edge, of course that's not what one can expect from a > distribution package - but that's also a feature. You left out the fact that the distro edition of mailman3 has very poor support because Debian doesn’t know how to do it and the setup is different enough from vanilla that this community has a hard time supporting it as well. You can certainly try to run it, but I’m willing to bet that you’ll regret it. Having tried it myself, I can’t in good conscience recommend it to anyone. The bottom line is that, IMHO, distro works great for fairly mature projects. MM3 isn’t that yet. YMMV, my $0.02, you get what you pay for, etc. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 8 months

[MM3-users] Re: spanish localization

by Abhilash Raj

On Sun, Feb 14, 2021 at 01:08, Victoriano Giralt <victoriano(a)uma.es> wrote: > El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió: >> What translations are those? Please give specific examples. What I >> am >> saying is Mailman core 3.3.3 is currently up to date with weblate. >> There >> are no Spanish translations for core done after 7 November in >> weblate >> and weblate shows 100% completion for Spanish for Mailman core. > > Mark, please, how do you check when translations happened? Nov 7th is > a > very significant date for me (it is my wedding anniversary) and I'm > 90% > sure that I dedicated time to Weblate after that date... You can look at the commit history of the spanish po file to get a detailed history of when and who made the changes. For example: Core: <https://gitlab.com/mailman/mailman/-/commits/master/src/mailman/messages/es…> Postorius: <https://gitlab.com/mailman/postorius/-/commits/master/src/postorius/locale/…> You find similar histories in all the repos. Each person's changes should be an individual commit in the repo, typically all outstanding translations are committed every night in Weblate. > > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, > after > updating to the latest releases, are still in Englanish (more English > than > Spanish). Could this be because of the .mo files not being up-to-update? There used to be some strings that were translated incorrectly, but I think we fixed all of those that we found. Abhilash > This is not a fight, we want to help, but do not know how. > > Thanks! > > -- > Victoriano Giralt Innovation Director > Digital Transformation Vicerectorate University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. >> Q: Are you sure ? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting annoying in email ? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> thanks, Abhilash Raj On Sun, Feb 14, 2021 at 00:57, Victoriano Giralt <victoriano(a)uma.es> wrote: > El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) > via > Mailman-users escribió: >> On 13/2/21 20:00, Mark Sapiro wrote: >> > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> > wrote: >> > > But... here is a thing that I can not understand: If the source >> (the >> > > .po >> > > file) is from november 7th, it doesn't matter how many times you >> > > recompile it: the result will be the same. >> > Correct, but the point is if you download the latest >> > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov >> 7 >> > file >> > in the distribution, you will find they are identical, so it it >> appears >> > that the weblate translation hasn't changed since that time. >> > >> > If there are issues in this mailman.po, they exist in weblate too >> and >> > need to be fixed there. >> >> That clarifies all. Thanks. As I said in my previous message, I'll >> wait >> for the next upgrade and hopingly the translations done after 7h of >> november (by others and me) will be there. > > I've visited Weblate, all Spanish strings are translated. Spanish is > 100% > translated, but, none of them have been "approved", whatever that is. > It > seems that a reviewer needs to approve the translation in order for > them to > be incorporated or released or whatever. I was sure I had reviewed > everything between November 7th and the day Abhilash announced the > release > candidate and asked for translation review, but nothing has made it > to the > released version. > > Maybe there's something in the translation flow that we are doing > wrong. > I'm starting to miss the good old days when Mailman 2 translators just > downloaded the .po files and returned them :-) > >> > Also note that the translations on weblate only affect strings in >> the >> > core code. The Mailman core templates are not currently >> translated in >> > weblate and there are currently no Spanish language templates. One >> > would >> > need to create Spanish translations of all the templates in >> > < >> > >> <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> >> > > >> > and submit a merge request to add them to a mailman/templates/es/ >> > directory. >> > >> I will make the template translations locally, test them, and then, >> if >> they are yet lacking in the main repo, follow your suggestion. > > I'm a bit short on time, but I'll help Guillermo with that, at least > reviewing or doing a second pass. I'm not proficient enough to speak > about > Mailman core templates, but for Django templates, there is a nice tag > for > marking text with translations in the .mo files ... > > -- > Victoriano Giralt Innovation Director > Digital Transformation Vicerectorate University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. >> Q: Are you sure ? >>> A: Because it reverses the logical flow of conversation. >>>> Q: Why is top posting annoying in email ? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

5 years, 5 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-25 01:37, Mark Sapiro wrote: > I think the difference is http vs https, not the IP vs domain name. > > Also, with either of these, you are addressing the web server and not > the wsgi server. The wsgi server is presumable listening on port 8000 > and in the beginning when you had the default > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' With this default, the template URI is in the format of http://localhost:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… Looking at this URI in lynx (on the same server as Mailman) it returns the text of the custom Welcome template, as does curl and wget. And it's the same if 127.0.0.1 is used in place of localhost -- ie. http://127.0.0.1:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… And the same result if the domain name is used with https -- ie. https://mydomain.com/mailman3/api/templates/list/mytestlist.mydomain.com/li… So, the template is all good, it can be accessed by Lynx, but the part of the Mailman suite that sends out the custom Welcome message cannot access it and spits out the error. Where are the custom templates stored? Is there a permissions issue perhaps? A grep for the text of my Welcome message turns up zero results. # grep -Rnw '/' -e 'Test two million for welcome' By the way, in Lynx when the template's URI uses the public ip adress -- ie. http://my-public-ip-address/mailman3/api/templates/list/mytestlist.mydomain… ... it returns a "404 page not found" in Lynx. Given that this is pretty much an out-of-the-box installation (venv installation as per the docs) and everything else works perfectly I'm thinking surely others have encountered this. Or is it just me? It's completely done my head in, so if anyone can offer a glimmer of light I'll grab it. > <REDACTED-PUBLIC-IPv4-ADDRESS> instead of 127.0.0.1. Also, > Have you set > ALLOWED_HOSTS in your settings.py? It should be something like > ``` > ALLOWED_HOSTS = [ > "localhost", # Archiving API from Mailman, keep it. > "127.0.0.1", > "<REDACTED-PUBLIC-IPv4-ADDRESS>", > "MYDOMAIN.COM", > ] Yes.

2 years, 3 months

[MM3-users] Re: Monthly Password Reminders

by Odhiambo Washington

On Fri, Feb 3, 2023 at 3:05 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > On Thu, Feb 2, 2023 at 8:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 2/2/23 06:29, Odhiambo Washington wrote: > > > > Does MM3 send these monthly subscription reminders the way MM2 used > to > > > do? > > > > I am looking for the setting, but can't find that in the list > settings. > > > > > > No, it does not. > > > > The rationale behind the decision to toss away that feature? Security?? > > For the passwords, yes. It was frequently reported as a bug, in fact. > Mostly the reminders generate requests to know how to shut them off. > You're the first in probably a decade who's asked how to turn them on! > It's because I only recently migrated to MM3 after watching from the periphery for years :) I have been on MM2, and even there I disabled it. I was just curious. While in theory we could protect in transit with SMTP over TLS, we > can't guarantee end-to-end encryption (eg, if there's a .forward at > the subscribed address), and while TLS is widely implemented, it's > still not universal. And there's no way to protect unencrypted email > from admins at the receiving host. Receiving encrypted email is > pretty much not implemented at all, except in some specialized > communities. Also, now that passwords (if they're used) are > attributes of Users who may have several Addresses and worse, they may > have admin privileges. So Mailman 3 passwords are generally higher > value than in Mailman 2. > > I can imagine a use for the list of subscriptions part that a few > users might like, but most folks would prefer not to get another > regular mailing. > > Steve > That makes complete sense, and I am satisfied with the decision. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 5 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On May 12, 2020, at 3:46 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/12/20 3:02 PM, Mark Dadgar wrote: >> >> The second patch did not work either. Ahh, well. > > > I think you need to do something like this: > > $ mm/bin/django-admin shell > Python 3.7.1 (default, Dec 14 2018, 13:17:01) > [GCC 5.4.0 20160609] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import Email >>>> emails = Email.objects.all() >>>> for email in emails: > ... if email.content.find('\u200b'*5) >= 0: > ... print('Found in ml {}, hash {}'.format( > ... email.mailinglist.name, > ... email.message_id_hash)) > ... >>>> _NAME/message/HASH/ Finally getting around to looking into this now that I’ve migrated from sqlite3 to postgres (writeup on that coming soon for the archives). Here’s what I get when I attempt the above commands: root@mail:/usr/lib/mailman3/bin# sudo -u list django-admin shell Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email Traceback (most recent call last): File "/usr/lib/python3.8/code.py", line 90, in runcode exec(code, self.locals) File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/hyperkitty/models/__init__.py", line 25, in <module> from .category import ThreadCategory File "/usr/lib/python3/dist-packages/hyperkitty/models/category.py", line 61, in <module> class ThreadCategory(models.Model): File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 103, in __new__ app_config = apps.get_containing_app_config(module) File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 252, in get_containing_app_config self.check_apps_ready() File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 134, in check_apps_ready settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 79, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 60, in _setup raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. >>> I am in no way a django expert. Thoughts? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 1 month

[MM3-users] urllib.error --was: Re: No module named 'mailman3hyperkitty'

by Axel Rau

> Am 17.01.2022 um 00:19 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/16/22 10:24 AM, Axel Rau wrote: >> ModuleNotFoundError: No module named 'mailman3hyperkitty' > > This comes from mailman.cfg from the class: definition in the [archiver.hyperkitty] section you probable have something like > > class: mailman3hyperkitty.Archiver > > instead of > > class: mailman_hyperkitty.Archiver Correcting this, does not stop server errors. While selecting a list in the browser, I’m getting: - - - Traceback (most recent call last): File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get 'hyperkitty' in archivers and # noqa: W504 File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ self[key] File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} - - - Question: Am I missing aliases in my nginx.conf? I just have: - - - location / { uwsgi_pass unix:///tmp/uwsgi.sock; include /usr/local/etc/nginx/uwsgi_params; } location /static { alias /usr/local/mailman3/static; } location /static/favicon.ico { alias /usr/local/mailman3/static/postorius/img/favicon.ico; } - - - Any help appreciated, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

4 years, 6 months

Search results for query "sapiro"