Will Yardley writes:
On Fri, Aug 28, 2015 at 01:37:18PM +0900, Stephen J. Turnbull wrote:
Stock Mailman 2.1.12 doesn't do any DMARC detection. This is quite
bizarre that they would backport such a feature rather than update to
2.1.18-1 or later. Mailman 2.1 is hardly an unstable
Sorry, serious finger fumble there. Please ignore the messed up one.
Andrew Hodgson writes:
That is interesting, and I wonder if this is something to do with
the way that Redhat have implemented the new feature.
My guess is that Red Hat backported 2.1.17 or 2.1.18-1. After getting
Mark writes:
First, apologies if this has been discussed before. I run a number
of mailman lists on a Centos 6 platform and mailman 2.1.12-25. This
version was updated in July as follows:
https://rhn.redhat.com/errata/RHSA-2015-1417.html and included
fixes for a number of DMARC issues.
Woody Mon via Mailman-Users writes:
So I tried entering RegExp ^.*+ but Mailman rejected this entry.
That's illegal syntax for a regexp because + is an operator.
The version you want is ^.*\+. However, that is a very bad idea if
you have any posters with email skills, because embedding + in
billy noah writes:
Downgrade detected, from version 0x20112f1 to version 0x20110f0
This is probably not safe.
The basic answer is You're going to need help from Ubuntu experts
anyway because the package database is out of sync with reality, so go
ask them.
That said, there are three
Billy Crook writes:
Am I just missing where this setting is, or has this not been
thought of yet.
It's been thought of, and it's just plain hard to do, because
automatically editing mail bodies robustly is just plain hard to do.
If you have a vast majority of users who use the same MUA, you
Billy Crook writes:
The part below here, is what I think I can just remove since I don't
want public archives provided via pipermail. (Just private archives
via the mailman path.)
Alias /pipermail/ /var/lib/mailman/archives/public/
Ah, OK, yes, you can remove that part. The
Billy Crook writes:
Any reason I should keep pipermail's config in apache around if I don't
want the list archives viewable anonymously?
Mailman doesn't serve HTTP, Apache does. The Apache config is what
makes them viewable on the web. If you expect them to be viewable to
subscribers, you
Mark Sapiro writes:
On August 24, 2015 12:44:02 PM PDT, Nina Nicholson
nnichol...@dioceseofnewark.org wrote:
Andrew - I am using Plesk, and Mailman does interface with it.
According to the FAQ at
http://wiki.list.org/DOC/Mailman%20and%20Plesk, updating Plesk
Mailman from source is
FTR, I've updated the FAQ 6.15 to refer to this thread:
http://forum.odin.com/threads/fix-for-mailman-posts-being-rejected-due-to-yahoo-and-aol-dmarc-policy.302641/
Steve
--
Mailman-Users mailing list Mailman-Users@python.org
Mark Sapiro writes:
On 08/23/2015 08:13 AM, Stephen J. Turnbull wrote:
Executive summary: if you're sure you've got all your hosts covered by
the SPF record, use -all as Jim P says.
There is an issue with -all. SPF does not work with .forwards or other
relaying of that nature
Paul Arenson/tokyoprogressive writes:
Actually I am not sure what PTR is…..but my reseller hosting is
just that, I pay for space from EZPZ and then can do as described
above.
Ah, sorry. PTR is the pointer record from a numeric IP address to a
human-readable domain name.
I see. Not sure
Dennis Carr writes:
The a:smtp.comcast.net is necessary so I can send email remotely
through my ISP and clear out successfully.
That does mean that anybody who can send through smtp.comcast.net can
send as a mailbox from your domain and pass DMARC, most likely. I
don't see a way to
Mark Sapiro writes:
On 08/23/2015 10:59 AM, Stephen J. Turnbull wrote:
Mark Sapiro writes:
The scenario is your list member is u...@example.com.
u...@example.com is set to forward all mail to example_u...@yahoo.com.
Heh. This user is screwed if you use
Nina Nicholson writes:
Our listservs are hosted by MediaTemple which provides Mailman
ver. 2.1.9. I understand that if I were to upgrade to the latest
version there are new features that would solve this problem.
Yes. They don't completely solve the problem, but they provide a
level of
Paul Arenson/tokyoprogressive writes:
Right. I received it.
I responded once from the same account. And once from the
Tokyoprogressive account.
To st...@turnbull.sk.tsukuba.ac.jp?
I don't see either one yet, but that could be my network. The
university just upgraded the network and
Paul Arenson/tokyoprogressive writes:
I looked in Cpanel and could see no directory starting with /usr/.
cPanel won't give you access to that, I'm pretty sure. You need to
have shell access to the host or virtual machine. If you don't know
if you have shell access, you probably don't. Large
Ulf Dunkel writes:
Thank you, but I won't send unmoderated news to any newsletter. I am
using Mailman for felt decades and I am so happy that the moderated flag
always kept me from sending postings too early.
Unmoderate yourself in the member view, and then use a privacy filter
with your
Richard writes:
Below is why I think it's a bad idea. Why can't we encode the
original email address in a comment or quoted token on the From:
line instead of jamming it onto Reply-To?
Because that makes it very inconvenient to reply to author. On some
lists, that's a crucial feature.
Robert Heller writes:
Is it true that the quickest way for a list admin to change a
subscriber's E-Mail address is to do a 'mass removal' then a 'mass
subscription?
Yes. Addresses don't change frequently, are even less frequently
reassigned to other users. In most cases the user does it
Selva Gaja writes:
I am using Cpanel third party mailman.
You're going to need to get help from your host and/or from cPanel.
This is a system-level issue. Mailman as we distribute it doesn't
change permissions on executable files after installation. Even the
fix permissions script only
Stephen J. Turnbull writes:
I suspect you need
Directory //mailman/admin/
Options FollowSymLinks
AllowOverride None
/Directory
Oops, that // in the Directory start tag should be a single /.
Sorry
Noah writes:
[Mon Jul 13 06:46:52.951120 2015] [core:error] [pid 7324] [client
ipaddr:50359] AH00037: Symbolic link not allowed or link target not
accessible: /var/lib/mailman/archives/public/maillist_name, referer:
http://hostname/mailman/admin/maillist_name
This is an Apache
Mark Sapiro writes:
nmtopics: ???
topics: ???
I don't think topics are implemented in MM3.
No.
I think there is a Google Summer of Code student working on dynamic
sublists which is a different approach to topics.
Yes. Topics are system whose structure is controlled by the list
Isaac Bennetch writes:
I feel I'm missing something here, any idea what it could be?
Dunno what's going with your import, but you probably won't find the
core HyperKitty devs here -- they are mostly on
mailman-develop...@python.org.
Sorry I can't be of more direct help!
Steve
Teijo writes:
After updating from Ubuntu 12.04 to 14.04 (Apache 2.2 to 2.4), only page
content I seem to get is Bug in Mailman version 2.1.20.
Don't assume it's Mailman, although the fact that you're getting to a
bug page is a strong indication that it is Mailman. The upgrade from
Apache
Bill Cole writes:
On 6 Jul 2015, at 9:26, Laura Creighton wrote:
2 somebodies I know want to merge their mailing lists.
Have they bothered asking each and every subscriber and received an
affirmative reply? No? Imagine my shock...
The correct answer to this is No, you can't.
JB via Mailman-Users writes:
I for one run a number of server with cPanel/WHM. They are using
the latest 2.x version of MM now. I was hoping that there would be
a way for cPanel/WHM to update to he 3.x tree and have all existing
list migrated to the new tree.
Thanks for the suggestion.
Mark Sapiro writes:
The short answer is yes, there is a plan and it is one of the things we
plan to include with Mailman 3.1, but no, there is not yet an ETA for MM
3.1.
I'm planning to migrate a bunch of lists by the end of July. I will
be moving from Mailman2 + Exim on Debian GNU/Linux
Peter Shute writes:
True. I was thinking more along the lines of someone taking an
unofficial peek at a few mailboxes to compile an unofficial hit
list.
A valid concern, and I agree that it could easily apply to the OP's
use case.
Steve
Peter Shute writes:
Ron Webb wrote:
I will also wish to add some type of disclaimer that no one
will probably give it much thought, but it will state that
statements made are the of the sole responsibility of the
author of the statement and they are not the official opinion
Jim Popovitch writes:
For the purpose of something like fail2ban all that is needed is
the IPaddr. Having all the others would be a nice to have, but
would really drive up the patch size.
From 10 lines to 20? I'd be more worried about the size of message or
msgdata objects.
P.S. I'm not at all opposed to the patch as you propose it, I'm just
thinking about loud about extensions. It's all blue sky though, and
you have a concrete reason for this. As the Timbot said:
Now is better than never.
Although never is often better than *right* now.
The first is for
Are you proposing this for inclusion in a future Mailman distribution?
If so, RFC 7239 Forwarded-For should be supported as well.
Also, since one of the purposes of this information appears to be
detection of attacks of various kinds, I would think that instead of
falling back to REMOTE_HOST or
Yasir Assam writes:
I noticed that this list, mailman-users@python.org, doesn't add a
DKIM header unless the list itself generates the email, i.e. the
email you sent to this list only has your DKIM header
(d=msapiro.net), whereas the original welcome email has DKIM with
d=python.org.
Mark Sapiro writes:
The safe thing is for 'you' to not have write permission on the mbox. If
you did have in the past, this may be how the group was changed.
Quite likely.
Basically, there are two ways to change the content of a file on
Unix-like systems. One way is to write-lock (at
Peter Shute writes:
Thanks, I think we're safe from all those methods, but I also think
it would be safer to leave the name blank, just in case something
changes.
You are right about safer, but note that at least one Mailman
developer (me) would consider inadvertantly exposing more
Mark Sapiro writes:
To: the_list@...
Sender: her_real_address@...
From: the_list_or_some_bogus_address@...
*Don't* recommend using a bogus address -- that requires skill on the
part of the user. The list address is known good, use that.
Problem example: if she's not at yahoo.com and uses
Robert Heller writes:
admin(16001): if id not in senderactions[sender]['message_ids']:
admin(16001): KeyError: 'message_ids'
Is this something I need to worry about? Or is it likely to have
been caused by an illformed spam message?
I'm not familiar with that particular part of the
Mark Sapiro writes:
Thats because they should be %(user_address)s, etc., not $(user_address)s.
Oops, sorry about that. Too much shell programming (and I don't use %
formatting anymore, I almost always use .format).
--
Mailman-Users mailing
Barry Warsaw writes:
On May 29, 2015, at 01:49 AM, casi.pw wrote:
According to my mailman.log, mails with special characters (in this case
€, but also Germanic umlauts as ö) in their bodies are shunted and
not delivered.
This looks like a legitimate bug.
It doesn't just look like
James Nightly writes:
How can I configure mailman on Debian to reject messages with
X-Spam-Score over 8? We are getting bombarded with spam, messages are
tagged by Spamassasin, but for some reason Exim4 still sends these to
Mailman.
Evaluating numbers by regexp is finicky, but there's a
EyeLand writes:
insert next variables on mail, top and futer
user_address
user_delivered_to
user_password
user_name
user_optionsurl
but they are not convert and I receive on subscriber email simple text
user_address
user_delivered_to
Regis writes:
Indeed 72 hours after the mailing, i continue to see permanently about
500 messages in the queue of my messaging server (i have a linux centOS
VPS with Qmail).
Using Qmail is asking for trouble. Dan Bernstein is unquestionably a
genius, but his software tends to assume
Allan Hansen writes:
69,74d68
# Added to deal with DMARC issuej
name, addrs = parseaddr(msg.get('from'))
addrs += '.invalid'
This is known to be a bad idea, as it increases the spam score at many
sites (because the author's mail domain doesn't resolve).
Allan Hansen writes:
Checking for aol.com and yahoo.com here alone will not work. I have
a bunch of other subscribers that have accounts with providers
that are owned by Yahoo (mostly) and AOL, but whose addresses are
not of this form.
Oddly enough, it turns out that they only use DMARC
Mark Sapiro writes:
On 05/17/2015 04:04 PM, Peter Shute wrote:
This isn't something that's happening right now, and I doubt it
will, but you never know. Apple is playing with mail formats
intended to display as a message summary on an Apple Watch, but
show the full message on a
renaud courvoisier writes:
Hi,
since I've updated from 2.1.13-5 to 2.1.13-6 the language option keep
chinese (taiwan) event if I uncheck it.
2.1.13 is very old, and the -5 is not part of the Mailman version.
You may be able to get better help from your OS distributor than from
us.
Try
Steve Matzura writes:
I have charge of a very mixed system--current OS (Fedora 20--OK 21's
out but I just haven't upgraded yet), current (or nearly so) Mailman
(2.1.18-1), Postfix 2.10 with a configuration file sfrom something a
lot older which I've run through the upgrade-configuration
Mark Sapiro writes:
On 05/12/2015 06:56 PM, bill.co...@unh.edu wrote:
I installed Python v3 yesterday with no problems. But I am
finding the Mailman v3 install instructions a bit hard to follow.
If I run into brick wall, is this the appropriate forum for any
questions I may
bill.co...@unh.edu writes:
The auto-responder feature built into Mailman looks like it would
be perfect for the site-wide list as a way of letting users know
when somebody will be looking at their questions (normal business
hours) and to point them to self-help documentation.
Mark Sapiro writes:
On 05/03/2015 06:17 AM, Laura Creighton wrote:
On all the machines I can ssh to, I have an
/etc/mailman/mm_cfg.py as well as a /usr/lib (or /var/lib)
/mailman/Mailman/mm_cfg.py, and the second is a symbolic link to
the first. Why do we have an
Mark Sapiro writes:
Debian also puts the files where they belong, including putting
mm_cfg.py in /etc/mailman/ which I agree is the right place, but Mailman
still thinks all the files are in /var/lib/mailman
Ah, OK, I see what you mean. Except IIRC Mailman proper knows the
absolute paths
EyeLand writes:
I not see OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES
Defaults are set in /usr/lib/mailman/Mailman/Defaults.py on my Debian
system. You should not change that file, any changes will be
overwritten the next time you upgrade. Instead, add those variables
Thomas Stein writes:
Exim gives no error. Just a loop between goodnews-bounces and goodnews. What
did i wrong this time? :-)
It appears that Exim can't send mail at all, and so first the error
happens in the mailing list, then it tries to send the error
information to the list-owner, but
Dennis Longnecker writes:
I really -- really want the list set so when someone gets an e-mail
from the list they can see who sent it and when they click reply it
goes to the original sender.
Given your user base, the only way to accomplish this is to set your
list so that there is *no*
Mark Sapiro writes:
As I said before, this is reported as a bug
https://bugs.launchpad.net/mailman/+bug/1447445 which is fixed for
the next release, and which fix has been installed for the
mail.python.org Mailman.
Note that the RFC-ly correct fix would involve a reverse lookup, which
is
Fil writes:
On Thu, Apr 23, 2015 at 7:29 AM, Fil f...@rezo.net wrote:
1) how to add a default value in mm_cfg.py
from the release notes I guess it's something like
DEFAULT_DMARC_MODERATION_ACTION = 1 # Munge
just to be clear: this line doesn't seem to bring anything to
Adam McGreggor writes:
I think that will help drive community contributions, immensely. It's
one barrier removed.
Immensely? I'm not terribly optimistic. I personally want to use
git, but moving to git has not appreciably changed the equation for
Emacs (which also made the move from Bazaar
Steven D'Aprano writes:
Can you suggest anything I can do to avoid triggering the ISP's
system?
humor mood=DMARC black, very very black, Sir!
Start by removing all yahoo.com and aol.com addresses! ;-)
/humor
The timing is wrong, and knowing you I suppose you probably already
have a
Laura Creighton writes:
become all the more common in the future. Is insisting that the IP
addresses match serving a useful purpose?
Yes. Differing request origins is the characteristic signature of a
CSRF attack.[1] I suppose the site could resolve the IP to a domain,
but that would slow
Laura Creighton writes:
Maybe at the point where we mention 'you must have cookies enabled'
we should mention that load balancers can cause problems?
I don't think nontechnical users will know what load balancer means.
By now most users either know about cookies because they've disabled
Thomas Gramstad writes:
How can I find out what version number of Mailman I'm using?
Visit the web interface (for subscribers, moderators, or admins), it's
in the footer. If you have shell access to the server, you can look
in mailman/Mailman/Version.py. If you have a package manager and
Executive summary:
1. Some aspects of accessibility (providing text alternatives for
non-text media) can be treated like translation (and will increase
the burden on translation!)
2. Frameworks need to help point out the pain points. Like: Yo!
there's an ALT-less image here that
Teijo writes:
As to WCAG 2.0, it's W3C's recommendation for Web Content Accessibility
Guidelines (http://www.w3.org/TR/WCAG20/).
Maybe this standard is better, but most W3C standards are not very
helpful to app developers. They're intended for library and framework
developers, as well as
David Andrews writes:
A reminder that any web UI, whether end user, or
administrator, needs to be accessible to disabled
persons -- preferably it will use the WCAG 2.0 AA standards.
We do use industrial-strength web frameworks, mostly Django. To the
extent they support the
Peter Shute writes:
But this time I tried unticking the Plain option for my
subscription. I was surprised to see that they did start coming
through as individual attachements, and that I could open them and
reply to them properly. This works in both Outlook and iOS Mail.
But all I
Peter Shute writes:
I've seen a plain text section that didn't match the html version
(if I'm remembering that incident correctly).
Indeed, occasionally you'll see the arrogant your MUA doesn't deal
with MIME properly notice in a text/plain MIME part, rather than in
the preamble.
Lindsay Haisley writes:
One of two things is eventually going to have to happen. Either people
who design and publish standards for email are going to have to come to
agreement on a proper standard for this kind of content
enhancement,
We have that, IMO. It's called HTML5 + link
Lindsay Haisley writes:
On Mon, 2015-03-23 at 11:58 -0700, Mark Sapiro wrote:
Yes. The MIME type of the digest part is multipart/digest. The
individual messages are message/rfc822 sub-parts.
So ideally, a proper MUA should be able to extract and deal with the
message/rfc822
Al Black writes:
I spent a few hours yesterday thinking about a cleaner to improve
the signal noise for the kind of posts were talking about. Not a
simple problem to solve (well for me anyway).
If you're serious about maintaining the relevant content, it's *very*
hard (requires AI natural
Mark Sapiro writes:
There is one case with Mailman lists where [to vs. cc] matters, at
least in MM 2.1, but I think MM 3 too.
If a list member has 'avoid dups' set and that member is a Cc: addressee
of a post, that member will not receive the post from the list AND that
member's
Lindsay Haisley writes:
I never quite understood all the fuss about top posting.
Usenet over UUCP via 300 baud modems on backbone servers with 5MB
disks.[1]
The reason behind quoting in the first place is to provide context
for a reply, but some MUAs make it very difficult to not top
jdd writes:
Le 20/03/2015 01:45, Mark Sapiro a écrit :
This is a major hot-button issue for me, The above is only scratching
the surface.
smartphones makes things horrible, on android, selecting text for
deletion is nearly impossible :-((
This is true.
On many lists I
Andrew Stuart writes:
For example I’m still not really clear on which field the list
address should go into,
To or CC. Most Mailman lists will refuse to accept mail BCC'd to the
list.
and does it matter what other addresses go into to and cc fields.
It doesn't matter for mechanical
Barry Warsaw writes:
This is an interesting question for me because I think the
netiquette rules I've been using for decades may be changing.
http://turnbull.sk.tsukuba.ac.jp/Teach/IntroSES/socsys.html
Yes-Virginia-economics-can-be-useful-ly y'rs,
Lindsay Haisley writes:
As far as editing, top posting, bottom posting, etc. it's just a matter
of using good sense.
But there's one aspect of good sense you left out, namely When in
Rome This list strongly prefers interlinear posting (posting
below the relevant paragraph) if you reply
Hey, if anybody is interested in *using* this patch, speak up
*now*, because tomoorwr GSoC intern applications open. I can add this
to the task list (specifially, port to MM3 and maintain for MM2
preetty please). But I'd like to know how high to prioritize when
evaluating proposals.
Steve
Thanks for the feedback, Jim and Ron!
GSoC project description here:
http://wiki.list.org/DEV/Google_Summer_of_Code_2015 (#12).
Steve
Jim Popovitch writes:
On Sun, Mar 15, 2015 at 2:40 AM, Stephen J. Turnbull step...@xemacs.org
wrote:
Hey, if anybody is interested in *using* this patch
Laura Creighton writes:
Apologies, apologies ...
(from somebody who only learned that about CentOS only _after_ she thought
thatinstalling a more modern Python system-wide would be in everybody's
interest)
Yes, indeed. Don't touch /usr/bin/python is an ancient Red Hat and
Centos
John McIntyre writes:
2015-02-20 0:16 GMT+00:00 Stephen J. Turnbull step...@xemacs.org:
For the webserver, I think a virtualhost configuration in Apache like
VirtualHost *:80
ServerName mailman.example.com
[...]
/VirtualHost
Thanks for that, I'm about to try
John McIntyre writes:
I'm guessing that apache can proxy for the mailman server, but what
about e-mail?
For the webserver, I think a virtualhost configuration in Apache like
VirtualHost *:80
ServerName mailman.example.com
ServerAdmin y...@example.com
Location /
Tapia, Rene writes:
The only issue that I have is that when certain large email lists
send emails containing attachments the .pck bounce messages in
/var/lib/mailman/data grow rapidly and fills up all the disk. These
lists are large and I know for a face a lot of these email
addresses
Malcolm Austen writes:
What I would really like is a (simple) way to trap the absence of a
subject header but I think, we can (understandably) only trap on the
content of something that is present :-(
As a workaround, procmail supports negative assertions of that kind:
:0:
* !
Laura Creighton writes:
Hi Laura!
While some people want to continue receiving digests, and some
people don't, everybody is in favour of having the mail only go out
in batches at set intervals during the day. So maybe once a day is
too infrequent, and 3 times a day would be nicer, but
Kim, DongInn writes:
Is there a way to setup a master list to allow any users in the
master list to subscribe all the other lists in the same domain
without admin approval?
Not exactly that without altering the code. Such a facility will
probably be available in Mailman 3. (If it isn't
Dan Speranzo writes:
i am attempting to create a new email address to be used for
posting. Please help.
This is a personal address, so that you can send mail to a mailing
list? We can't help you with that.
Or is this a mailing list that can have mail addressed to it and will
be delivered
Peter Shute writes:
A lot of people use the cPanel version and can't do anything
complicated for support. Even though this particular case is about
trying to help a difficult user to do something that's normally
straightforward that's probably pointless anyway, I hope v3 at
least gives
Gary Merrill writes:
I know the kinds of problems you guys are facing -- although you
should be somewhat grateful that you aren't dealing with the FDA,
insurance companies, gigantic healthcare organizations, the CDC,
and multiple pharma companies. :-)
I don't have to deal with them, but
John R Levine writes:
[About munging p=reject addresses in From]
I've been doing this for the better part of a year, with some very
non-technical users on lists for my church and a bunch of folk
dancers. For the most part, they don't even notice it. Perhaps one
or two wrote to me to ask
John Levine writes:
Have you tried any sort of reversible rewriting? On my lists, sending
addresses in dmarc'ed domains get a local domain appended on the From:
line, e.g. mail From: mari...@yahoo.com -
mari...@yahoo.com.dmarc.fail.
[...]
It's gross and disgusting, but no worse than
Andrew Stuart writes:
Image a mailing list myl...@example.org
Is there any reason why the users could not be told to use
adifferentl...@adifferentdomain.org which simply forwards mail to
myl...@example.org
Would this raise any potential problems?
Depends on what you are trying to
Timothy Murphy writes:
So it seems the simplest thing to do is to get my sysadmin
to create a new list, and delete the old one.
Yes. Since you're at a university, it seems likely there are lots of
such lists and the sysadmin is familiar with the procedure.
I don't know if it's easy to
Mark Sapiro writes:
On 12/26/2014 09:21 AM, Greg Sims wrote:
Is there a way to have a robots.txt file for the
lists.raystedman.org subdomain?
Absolutely. Just put it in the root directory that contains the page
which is served when you go to http://lists.raystedman.org/. I.e., put
Steven D'Aprano writes:
Some of my Yahoo subscribers are reporting that emails from my
mailing list are being flagged as spam. As far as I can tell, I'm
not using spammy words, and the emails are plain text not HTML. I
have SPF set up.
I think it might be helpful to set up DKIM as well.
Lucio Chiappetti writes:
I hope it is allowed to post a few screendumps to demonstrate
Unfortunately, Mailman @python.org doesn't pass those, and they don't
get into mail-archive.com because it's subscribed by mail, not direct
from the Mailman daemon.
This satisfies your item 1 in three
Lucio Chiappetti writes:
Actually, most Emacs-based MUAs are able to treat digests as folders
by default. No customizations required.
Then you are beyond my mark,
Not really. My primary MUA is VM, which presents a rather simple
menubar toolbar interface to the average user.
Peter Shute writes:
They create problems when they reply by constructing the reply by
hand with a different subject line, or by simply replying to the
digest email, with unchanged subject line and quoting the digest in
full. The only reason they use digest mode in the first place is
Andrew Hodgson writes:
I run a high volume list (around 80 messages per day), and we have
complaints from digest users that the digests are difficult to work
with. One requested feature is could the digests be in HTML
format, and a link be presented in the table of contents to go to
Andrew Hodgson writes:
One of the examples I saw from another setup was to use in page
links for each message in the TOC, so the links in the TOC just put
the focus onto the next message.
I don't understand what this means in terms of the link's href. It's
definitely not a matter of just
501 - 600 of 1551 matches
Mail list logo
