On 1/19/19 2:44 PM, Kenneth G. Gordon wrote:
> One of my subscribers is complaining that he cannot activate the digest mode
> for his
> account. I can find nothing wrong in the admin database.
>
> Where should I look for this problem?
What does the user do and what happens?
--
Mark Sapiro
One of my subscribers is complaining that he cannot activate the digest mode
for his
account. I can find nothing wrong in the admin database.
Where should I look for this problem?
Ken Gordon
--
Mailman-Users mailing list
On 13 March 2013 22:56, Mark Sapiro m...@msapiro.net wrote:
Lists can be configured to send digests periodically
(digest_send_periodic = Yes), but the frequency is determined by how
often Mailman's cron/senddigests runs.
You have probably set digest_size_threshhold to 0 thinking this means
ml lists wrote:
I had/have the following
digest_size_threshhold = 30
digest_send_periodic = no
digest_volume_frequency = weekly
And if I understood correctly, this regardless of threshhold size
should only send weekly, no?
No. This will send a digest whenever the size reaches about 30K bytes
Hello,
I am having some problems with a mailman list that i administer. The list
is configured to send digest emails once a week (via the web ui) but this
is not happening, instead emails are being sent individually, as they are
posted to the list, but tagged as digest.
Would anyone have any
ml lists wrote:
I am having some problems with a mailman list that i administer. The list
is configured to send digest emails once a week (via the web ui)
Lists can be configured to send digests periodically
(digest_send_periodic = Yes), but the frequency is determined by how
often Mailman's
Dear Mark, dear listers,
I responded much too quickly that the issues with digest-mode were
fixed. In reality they are not fixed, they reproduced and it is being
a pain. In collaboration with our host, we have cleared, several
times, the buffer, discarding repeteadly volumes (to get rid of
Lluis Montoliu writes:
At hosting level they keep indicating that mailman is outdated, no
longer maintained and that we should consider moving to other
programs
Your hosting service is either really failing to do their homework, or
outright lying to you. Mailman is very much
Thanks for support Stephen. I'm using version 2.1.11 and you've got it
right. Our main problem is lack of access at root level, therefore we
are limited to what we can do through the mailman admin panel and to
suggest our hosting service to do this or that, which they can choose
to do or
Lluis Montoliu wrote:
The fact that two of my lists are experiencing these problems and not
the rest suggest me that some email addresses that could be shared
among the two could be the culprit. I'm investigating this.
This doesn't seem likely.
Currently, problems can't be related to
Thanks Mark, just tried what you suggested, and toggled off and back
on the digestable options. Will see how it goes on the next couple of
days, whether digest will be dispatched automatically or not.
Found only 13 addresses shared by the two lists from users that had
selected digest-mode.
Dear Mark,
excellent suggestion, indeed there were messages heavily formatted
which apparently affected mailman and its normal processing of digest
buffer. There was no need to remove these messages. Re-starting the
list server did the miracle and both lists are now working fine,
Some more data. Hosting provider can't find anything wrong. I have set
a new list, fake users for testing purposes. Set one of them for
standard the other for digest-mode and played with size limits and
daily and everything worked as expected, in this test list, whereas
the two large list
Lluis Montoliu wrote:
the two large list are not sending any digest-mode, with the exact
same settings, even if I decrease the value to 256 or if I trigger
sending a new digest dispatch right now, which does not happen. I'm
totally amazed. I've seen the archives of mailman and,
Dear listers,
Suddenly, some users of two mailman (version 2.1.11) lists I am
administering have started to complain about digest-mode not functioning
properly. In brief, messages are not being sent in digest-mode. Settings
are 1024 Kb for size before sending a digest message or daily, if this
Why do digest mode links rename a .jpg file? A Mac OS X user can't see
attachments.
URL:
http://lists.metalartists.org/mailman/private/sandbox/attachments/20100219/9e05e1cf/attachment.obj
-- next part --
A non-text attachment was scrubbed...
Name: DSC04246.JPG
Type:
John Griessen wrote:
Why do digest mode links rename a .jpg file? A Mac OS X user can't see
attachments.
URL:
http://lists.metalartists.org/mailman/private/sandbox/attachments/20100219/9e05e1cf/attachment.obj
-- next part --
A non-text attachment was scrubbed...
Name:
On 28-Feb-10 09:59, John Griessen wrote:
A non-text attachment was scrubbed...
Name: DSC04246.JPG
Type: application/octet-stream
Because it was defined incorrectly as an application/octet stream
instead of as an image/jpeg
--
I draw the line at 7 unreturned phone calls.
On 28-Feb-10 11:03, Mark Sapiro wrote:
SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True
Would that be considered unsafe?
I mean, it SEEMS unsafe, but is it really?
--
Overhead, without any fuss, the stars were going out.
--
Mailman-Users
LuKreme wrote:
On 28-Feb-10 11:03, Mark Sapiro wrote:
SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True
Would that be considered unsafe?
I mean, it SEEMS unsafe, but is it really?
It could be. Suppose I send a message to your list with an attached
evil_app.exe file that I call Content-Type:
On Aug 12, 2005, at 03:40, Michael LaFarr wrote:
I would like to set up a list that does not give the user the
choice of how they will receive messages (individually or grouped). I
would like to configure the list so that when I approve incoming
messages,
all messages will all be sent
Larry McMahon-Padolski wrote:
When a user attaches a non-txt file, Mailman provides a URL pointing to
the attachment.
This seems only to apply to digest mode.
For example:
/pipermail/test_domain.com/attachments/20050201/d8f9df80/ReneeSUMMERSCOURSESCAPP.doc
However the proper URL is:
Hi,
When a user attaches a non-txt file, Mailman provides a URL pointing to
the attachment.
This seems only to apply to digest mode.
For example:
/pipermail/test_domain.com/attachments/20050201/d8f9df80/ReneeSUMMERSCOURSESCAPP.doc
However the proper URL is:
Mailman 2.1b2 allows subscribers to select digest delivery mode - even
if the list is set up not to deliver digests at all. What happens then
is that these subscribers do not get any mail at all. The admin is not
informed, but when the list of subscribers is browsed, he is informed
that there are
.
SD
- Original Message -
From: Peter Bengtson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, June 25, 2002 3:03 AM
Subject: [Mailman-Users] Digest mode bug in 2.1b2
| Mailman 2.1b2 allows subscribers to select digest delivery mode - even
| if the list is set up
For your specific question, this is not a bug, Mailman is not just
another out of the box, ready to go, software; there are many ways
to customize it, but you have failed complete your customization.
I must say that your answer is a bit surprising. Mailman offers an
enormous wealth of
I think it would be extremely useful to be able to click on an index
entry at the top of the digest and have it take you down to the place in
the digest where that mail starts. Some of my digests are very large
and I only care about a couple of the messages. They can be very
cumbersome to find.
27 matches
Mail list logo
