patch in my
archives. I no longer have access to that Mailman system.
--Barry Finkel
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/li
uot;legalese" in the
footer of mail messages. [Note that I nave removed the footer
from Carl's reply.]
--Barry Finkel
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
h
I wanted to get support from Mark and this list,
instead of from Debian. So, I figured out how to create a package from
the Mailman source. This was on an older version of Mailman, but I
assume that my technique should work with the latest Mailman 2 source.
Contact me
lman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
Member address: bsfin...@att.net
Mailman is NOT listserv. Listserv is a different mailing list
management software from Lsoft.
--Barry Finkel
--
Mai
r message gives NO information as to why the
was not delivered.
--Barry Finkel
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.
ogin attempts are coming. I have
no idea if this is related to the problem that started this thread.
--Barry Finkel
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
http
ear in his/her reply.
Mailman has no method for changing the Subject: line.
A subsequent recipient who replies to the list has the option
of changing the Subject: line to remove this addition.
--Barry Finkel
On 12/8/2021 2:30 AM, Christian Buser via Mailman-Users wrote:
Good morning
This can be in
he appropriate error code; the
program that produces the message must know which of the two
cases occurred. If the error message has options, then the
support personnel who have to respond to the message have to
do additional debugging to determine the exact cause
building a package from subsequent new source
distributions.
I do not know about Centos Mailman, but if Centos has taken 2.1.15 and
retrofitted subsequent security patches, then the 2.1.15 version would
not have all of the non-security (DMARC et alia) enhancements.
--Barry Finkel
a_Camilla?=
To: Biblioteknorge
Subject: Ledig stilling - Fredrikstad bibliotek - LittFri - et tilb ...
And, of course, this mail is not a bounce message that the bounce
processor can parse.
--Barry Finkel
--
Mailman-Users mailing list -- mailman-user
ansferred, you’ll need to coordinate with the GNU project.
Cheers, and good luck!
-Barry
signature.asc
Description: Message signed with OpenPGP
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users
nable to find the options page for this list via other means.
I do not get the digest, so I cannot see the footer therein, but the
URL you posted does have
mailman3
not
mailman2 .
--Barry Finkel
--
Mailman-Users mailing list -- ma
spent a lot of time
determining how to create a Debian/Ubuntu package from the source.
I think that this was around 2.1.14, but I assume that my instructions
would work on on the latest 2.1.x source. For details, contact me
offline. The procedure is not complicated,
--Barry Finkel
-
erating system to cause the problem. By that time,
of course, we had modified the software to get around the problem.
I would consider changing a domain AND migrating Mailman to be two
"big" changes that should not occur at the same time.
--Barry Finkel
---
rary that sometimes was needed. So I spent time creating my
own Ubuntu package for Mailman from the source. I assume that my
method would work for the current release of Mailman. For information
contact me off-list. My procedure is not complex.
--Barry Finkel
---
a Mailman issue, host issue, domain issue? or?
thanks
My first thought - are you sure that xyz is an invalid userid?
Try sending a test message from a personal e-mail account.
(Note that I have removed the previous list footer in my reply.)
--Barry Finkel
ware writes this line.
I am not an expert in MIME, but I do not see how any "X-" header
line could be treated as a malformed MIME header.
If you have users who are using digest mode, then removing that option
will cause consternation with those users. And I doubt that the diges
me that what I did would work for the current Mailman 2.x release.
Those who want details can contact me off-list.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman F
er MM3. So I suspect, at the risk of some
> duplication, both with have to make the cut.
Very cool, Rich. And I think you’ve got exactly the right focus. Best of luck
and do let us know when you’ve got something you need reviewed, or if you have
any questions at all (esp. regard
t Abhilash will bring to the project, and I know that he will do a
great job. To me, Mailman has always been about collaboration, and the best
way for it to succeed is for you to continue to contribute your insights,
experiences, opinions, and skills with positive intention.
-Barry
https://www.we
fortable to write your own
clients against Core’s REST API, you can do so using whatever technology you
want, since it’s just HTTP+JSON. You can augment the functionality currently
available via REST with shell access.
Cheers,
-Barry
signature.asc
Description: Message si
.br.
david
I would report this to mail-ab...@cert.br .
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: ht
briefly mention at Pycon that ARC was getting turned on at various
large providers. I'd like to target ARC support for Mailman 3.2.
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-
s also been announced, I think
we'll see Debian packages soon.
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http:/
Hello Mailpeople!
On behalf of the entire team and all our wonderful contributors, I'm happy to
announce the release of GNU Mailman 3.1 final. My deep thanks go to all the
Mailman project sprinters at Pycon 2017 for getting us over the line!
Two years after the original release of Mailman 3.0, t
On Apr 05, 2017, at 11:36 AM, Stephen J. Turnbull wrote:
>Barry encourages participation by musicians!
>
>Not official Barry-spokesman, but reasonably good at channeling :-)
Don't forget the secret bassplayer.py handler! You email it a drum pattern
and it replybots you a funky gr
REST API of Core is a
fully administrative API. It can be protected by some basic auth secrets, but
nothing more than that, so just make sure that the Core REST API isn't
published on some public IP address and you should be fine.
Cheers,
-Barry
On Mar 30, 2017, at 04:11 PM, Mark Sapiro wrote:
>I'm afraid Node.js is still a requirement.
Of the web interface of course. Technically those are optional components,
but practically speaking if you want to control Mailman 3 via the web, that's
the only op
ied
I'll fix that to use the https URLs.
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.or
the re-send happens to be sent over a "good" (in RR terms) IP address
to the RR inbound mail servers.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman
on GitLab, and we're
very grateful for that too!
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://w
x27;)
< owner_mail = owner_emails[0]
---
> _('Enter the email of the person running the list: '))
215,217d210
< # assign the owners
< mlist.owner = owner_emails
<
256c249
< owner_emails, siteowner,
---
>
lling the package will
overwrite any existing Debian/Ubuntu installation.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Pol
On Sep 08, 2016, at 08:15 AM, Jim Popovitch wrote:
>> ('OutgoingRunner', 3), # outgoing messages to the smtpd (change to three
>> '3' queues)
Slices must be a power of 2.
Cheers,
-Barry
--
Mailman-
t, core and Postorius are, and
here's what's left:
https://gitlab.com/dashboard/milestones/31?title=3.1
For core, all the big stuff is in except the unsub workflow, and I have a
branch in progress for that.
Cheers,
-Barry
--
Mailman-Users
s. Or Postfix
will give an error or warning message about the duplicate entry.
There is no way for Postfix to know whether to deliver the mail to the
Mailman list or to the local user.
In short, I believe that what you want is not possible.
Even with virtual domains, you still have the name conflct.
--
t
to get involved in. Almost anything you *want* to do *needs* to be done, and
we developers are a nice bunch of people, so please join us!
Cheers,
-Barry
pgp0x1WbwS4lG.pgp
Description: OpenPGP digital signature
--
Mailman-Users mailing l
roject page:
https://gitlab.com/mailman/lemme/tree/master
Several of us are going to start working on this after the MM3.1 release goes
out (hopefully in the next month or so). It will take work in the Core as
well as work on Lemme, so we invite anybody interest
On Apr 18, 2016, at 08:57 AM, Jim Popovitch wrote:
>Mark, Thank You for your hard work and dedication to providing the
>worlds best mailinglist manager, it is much appreciated by many
>people.
Indeed! Mark has my deepest gratitude for his ongoing care of Mailman 2.1
;
would for the help
line worrk? Or rather not?
Thank you, Christian
Why not create a test list and experiment? Or, I assume, you could
experiment with the already-created 9but seldom used) Mailman list.
--Barry Finkel
--
Mailman-Users mai
ave all
of the Mailman aliases for each list?
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list
hat we'll
release 3.1 by Pycon 2016.
I know that bundler provides 3.0.2 right now, but it shouldn't be too
difficult to switch. The few folks I know running Mailman 3 in production are
running Core off the git master branch.
Cheers,
-Barry
---
n - it just keeps
working.
Barry
--
===
832 Hendecourt Rd.
North Vancouver BC V7K 2Y2
778-848-5586
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FA
's a display problem in Postorius.
You can also file a bug for the core and Postorius and let us sort it out. :)
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
M
" points to
>"http://example.com/MYADDRESS";, which is clearly wrong. Instead of
>example.com there should be MYHOST, and perhaps something more before
>MYADDRESS.
That's a known deficiency in the templating system for MM3. There a
one that placed libraries in the proper
directories for Debian/Ubuntu.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Secur
, what on what type of Unix box are you issuing the
"mail" command?
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA
to a list via "Bcc:", you have to change the list
configuration to allow implicit destination. The mailman-supplied
default is to not allow the list name in a "Bcc:"
--Barry Finkel
--
Mailman-Users mailing list Mailman-User
nt might be is
anyone's guess.
P. S.
> their informational news listserv which is running on Mailman version
2.1.20.
Listserv (R) is a registered trademark of Lsoft, and that term does
NOT pertain to Mailman. Both products are mailing list management
software, but only List
t the changes in each component by following
the version links in that overview page.
Enjoy,
-Barry (on behalf of the entire Mailman development team)
pgp5r3d3nuyDx.pgp
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-
tu Mailman package. It took
me a while to figure out how to do it, but once I did it, I had
the instructions to re-do it for subsequent SF Mailman releases.
I wanted to know exactly what source I was running, so I could get
assistance from the authors via this list.
--Barry Finkel
--Barry Finke
On Aug 12, 2015, at 02:44 PM, Brad Rogers wrote:
>*All* lists run from list.debian.org are to have their footers turned off
>because of valid DKIM signature breakage.
FWIW, lists.debian.org does not run Mailman.
Cheers,
-Barry
pgphyutcfmO1m.pgp
Description: OpenPGP digital sig
>developers on the Mailman Developers list.
You did good, Steve! :)
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Sec
maybe extract
a handful of messages from each (or take the entire files), combine
them, and make an archive for a new test list.
If I remember correctly,
bin/arch --wipe ...
I do not remember the other parameters, but a search of this list's
archives will find the comm
t at:
https://gitlab.com/mailman/mailman
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
cripts developed by Mark Sapiro, and he referenced them in a
posting earlier today or yesterday.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.
two great
organizations with one donation.
Cheers,
-Barry
pgpdQmc9dTuWG.pgp
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wik
irms the settings.
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archiv
You probably want to start with the bundler and let it grab and install all
the other parts.
More information is available at:
http://www.list.org
http://wiki.list.org
http://launchpad.net/mailman
#mailman on freenode
mailman-develop...@python.org
Happy Mailman Day,
-Barr
assist you if you posted the
error messages that you have received.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security
were written to solve. And one patch removes a library that is
sometimes needed. I decided at that time that it was better for me to
create my own Ubuntu package from the SourceForge source and install
that. If I had a problem, I could post it on this list and get
expert advice.
--Barry Fink
could file a bug (tagged 'mailman3') and try to port your
changes to the Mailman 3 trunk? No promises, but I'd like to look at your
work.
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org
l almost exclusively
and it has very good reply-to-list support.
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy:
ough different styles in widespread use
that it's best to conform to the norms of the community. My own feeling is
that interleaved-with-trimming is the most conducive to mailing list
discussions.
Cheers,
-Barry
--
Mailman-Users mailing li
On Jan 26, 2015, at 10:10 AM, Barry Warsaw wrote:
>If you had write access to the old wiki and want it again for the new wiki,
>you will have to re-submit a request to mailman-ca...@python.org. Please be
>sure to register with wiki.list.org and provide us with your user name.
Paul r
le we appreciate the years of service donated to
us by Atlassian and Contegix, it's important that we set an example by
utilizing an entirely free software stack for our development and outreach.
The wiki was our last remaining non-free bits.
Let the gardening begin!
Cheers,
-Barry
(On behalf
t with Debian/Ubuntu.
I told him that I was more comfortable with the SourceForge source
and the support I got from this list. He allowed me to build a Mailman
package from the SourceForge source, and that is what I did.
I never installed the Debian/Ubuntu Mailman package, so I never had to
ta
his excellent Falcon Framework package, which now
replaces restish as our WSGI-compatible REST layer. Both of these changes
were critical in allowing me to port the core to Python 3.
Enjoy, and Happy New Year.
-Barry
[*] Postorious and HyperKitty will port to Python 3 on their own tim
ion
or four?
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: h
On Dec 03, 2014, at 08:14 AM, Andrew Stuart wrote:
>Where can I find the documentation that explains the required configuration
>for cron in Mailman 3?
Mailman 3 is best discussed on mailman-developers. There isn't much existing
documentation on running any cron scripts for MM3.
Che
On Dec 03, 2014, at 08:15 AM, Andrew Stuart wrote:
>If I run the mailman command it keeps creating “var” directories in whatever
>the current directory is.
>
>Is that intentional?
Mailman 2 or 3? If Mailman 3, please discuss on the mailman-developers list
for now.
Ch
to avoid using a Mailman list.
And Mailman provides an archive of the postings and can control
who can post to the list.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-
uot;, in my opinion, means something drastic;
adding a ">" in front of "From " does not make the message
unintelligible.
I dislike the format that uses "Content-Length:" to determine the end
of a message. If I edit an archive file a
Very soon (perhaps this weekend) I will land the port to SQLAlchemy as our ORM
layer for MM3 in the trunk. This is based on great work by Abhilash and
Aurelien. There have been some reports of SQLite locking problems in MM3 and
it will be interesting to see whether the port from Storm to SA will
permissions to the Confluence wiki.
Huge thanks also go out to the Python Software Foundation and the PSF
infrastructure team for donating the resources that the new wiki is running
on. Thanks too to the other Mailpersons who have helped review the moin
conversion process.
Cheers,
-Barry
signa
atter is the Urgent header, but IIRC, that only
bypasses digesting rules. I.e. digest members will get an immediate
delivery.
It would be an interesting feature for MM3.
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
ssue? Are there any settings I can use
or steps I can take to help resolve this?
Thanks in advance.
Sincerely,
-Alan
Alan, I think that you are experiencing DMARC problems. You need the
latest Mailman (2.1.18-1) to handle DMARC issues. See the archives
of this
he number of
DNS requests back to the master DNS server. A domain owner should
have multiple DNS servers so that one is always accessible for queries.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailm
re is a mailing list named
mailman
You need to create that list before Mailman will start.
The instructions for this should be on the web; I do not
have the URL handy.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
ht
It probably does not
have the aliases (listed above) that are required for Mailman to run.
Run the "newaliases" commmand, and then check the aliases file.
If these aliases are not in the file, then you have to add them and
use "newaliases" to rebuilt the aliases database files.
tfix-to-mailman.py ?
That piece is not recommended by the Mailman developers. See
http://wiki.list.org/pages/viewpage.action?pageId=15564817
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/m
ime for greylisting. You would have to look at the mail logs
from the NUWVICMS2 machine to see what it was doing from 08:50 until
09:11 (GMT+1000) to know why the mail was delayed. Also, the logs
on the server16 machine would probably tell if server26 tried an earlier
connection to the NUWVICMS2
mail that was being sent,
I cannot tell what Comcast might have thought objectionable.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x
now
avoiding using an e-mail address ".@chase.com" because
the address is not shown as the sender in some MUAs.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mai
"From email address date"
line beginning in column 1 at the start of each message in the file.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman
Am I missing something?
I run a cancer support group. Is there some way to append the list address
appended to "CC" of incoming messages? I would like my members to simply
"Reply to all" and share response with the others in the group.
Respectf
e, I had no problems
building packages for subsequent Mailman releases. IIRC, the last
Mailman for which I built a package was 2.1.14. I do not know if
any changes since then would require changes to the package-build
process. I have de
kely will be tuned to protect
Hotmail users if Hotmail should decide to use the "reject" policy).
> Nielsen's First Law of Computer Manuals:
> People don't read documentation voluntarily.
How (sadly) apropos!
HTH
Steve
Is this also true?
Users from DMARC-reje
as defined and implemented today is poison to mailing lists,
and it's a shame that you, our dear users, are the canaries. I hope we can
have some constructive discussions with the DMARC advocates about how to
restore usability to mailing lists in a DMARC pervasive world.
at will be just as effective at phishing as .invalid.
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.
wiirc.com/
Cheers,
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archive
on the
mailman-developers mailing list, or on IRC via the freenode #mailman channel.
Enjoy!
-Barry
(On behalf of the entire GNU Mailman development team)
P.S. My personal, deepest thanks to Florian, Terri, Aurélien, Mark, John, and
Piotr for coming to Pycon, working hard and joyfully at the s
On Apr 18, 2014, at 03:07 AM, Stephen J. Turnbull wrote:
>Getting it right by design ... well, that's why we need Mailman 3.
And really, Python 3. The email package in Python 3.4 rocks.
-Barry
--
Mailman-Users mailing list Mailm
o a good, stable, final release.
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable
n
>mm_cfg.py, nor why there has to be exactly one value for any given language
>which mailman supports.
The big problem is that you can't have multilingual footers. I'm hoping to
fix this in MM3 by supporting a lookup scheme that would allow different
footers (and other decoratio
y.
>It's not limited to mailing lists, either. Anybody who has a
>forwarding mailbox is at some risk (in a personal .forward this is a
>simple pass-through preserving the DKIM signature so it should be OK,
Yeah that sucks too. I sure hope none of the FLOSS projects I work
or not, and
then allow the list admins to select the approach that is least unpalatable
for their users.
-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.li
t way to do it is to submit a merge proposal against the lp:mailman/2.1
branch (it would be against lp:mailman if it were for 3.0). Then Launchpad
will create an easily displayable diff, e.g.
https://code.launchpad.net/~jimpop/mailman/dmarc-reject/
non-zero bounce score.
Check the archives for a link to the script.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Securi
t;the mail itself in a message/rfc822 part. As far as I know, no
>component of DMARC allows digging into a message and trying to DMARC
>the MIME parts.
That's what I mean by "we can fix it if we make the user experience
horrible". See all the complaints about the MIME-prope
1 - 100 of 1348 matches
Mail list logo
