My Mailman system sends out duplicate (two copies) of some
administrative-type messages. There are two password reminder
messages sent out each month, two copies of the once-a-day message
that announces pending messages in a list, and two messages each
morning at 8:00 a.m. from the list
On 1/6/2013 11:31 AM, David Andrews wrote:
My Mailman system sends out duplicate (two copies) of some
administrative-type messages. There are two password reminder messages sent
out each month, two copies of the once-a-day message that announces pending
messages in a list, and two messages each
On 1/6/2013 1:31 PM, David Andrews wrote:
My Mailman system sends out duplicate (two copies) of some
administrative-type messages. There are two password reminder
messages sent out each month, two copies of the once-a-day message
that announces pending messages in a list, and two messages
I am getting duplicate messages once a day, the 8:00 a.m. messages
sent out by every list telling of what messages pending. My users
also get two copies of the password reminder once a month. And ...
not sure if it is related, but probably, I get two copies of a
message each morning at 8:00
On 7/1/2012 2:12 PM, David Andrews wrote:
I am getting duplicate messages once a day, the 8:00 a.m. messages
sent out by every list telling of what messages pending. My users
also get two copies of the password reminder once a month. And ...
not sure if it is related, but probably, I get two
All,
I did some searching and don't seem to be able to find anything in the archives
related to this, so...
I previously was running a series of lists on a Mac OS 10.4 Server, which I
believe runs Mailman 2.1.3. And there were no real problems with duplicate
messages.
I have just now
Ryan Stasel wrote:
I previously was running a series of lists on a Mac OS 10.4 Server, which I
believe runs Mailman 2.1.3. And there were no real problems with duplicate
messages.
I have just now updated to 10.6.2, which runs Mailman 2.1.12rc1, and Dovecot
(which I wouldn't think would
On Jan 5, 2010, at 06:59 , Mark Sapiro wrote:
Ryan Stasel wrote:
I previously was running a series of lists on a Mac OS 10.4 Server, which I
believe runs Mailman 2.1.3. And there were no real problems with duplicate
messages.
I have just now updated to 10.6.2, which runs Mailman
On Tue, Jan 05, 2010 at 08:28:58AM -0800, Ryan Stasel wrote:
On Jan 5, 2010, at 06:59 , Mark Sapiro wrote:
2) something in the outgoing MTA to you path that used to deliver only
1 of multiple messages with duplicate message-ids changed and is no
longer dropping dups.
This looks like the
Adam,
My bad, as I realized it wasn't an MTA, but was caught up reading something
else when I was typing. However, this doesn't change the fact that previously,
Cyrus did duplicate suppression, and Dovecot does not... which is why this
worked when my imap/pop server was Cyrus, and now I get
On Tue, Jan 05, 2010 at 09:25:58AM -0800, Ryan Stasel wrote:
I'm not sure postfix (the MTA) should be doing the duplicate
suppression. But looking around online, it seems like there is a very
large argument that goes something like: Dovecot should do it -
It's not dovecot's problem, it's the
See the FAQ at http://wiki.list.org/x/TIA9 for more on umbrella lists
and workarounds including how to use regular_include_lists to make a
'better' umbrella list if you're not concerned about digest members of
the sub-lists or processing bounces of posts sent to the everyone
list.
Just
At 02:08 PM 8/4/2009, Barry Finkel wrote:
David Andrews dandr...@visi.com wrote:
I have a problem, and don't know if there is an easy or viable
solution. I run a bunch of lists for an organization, over 150
lists, about 80 percent public and 20 percent private. Periodically
there are messages
David Andrews wrote:
This was the only response I got, and appreciated. Is this the only
possible approach? I am not sure I want to subscribe people to a
list they didn't subscribe to, although I am considering it. Any
other approaches -- or do I have to wait to MM3 which is who knows when.
At 03:29 PM 8/9/2009, Mark Sapiro wrote:
David Andrews wrote:
This was the only response I got, and appreciated. Is this the only
possible approach? I am not sure I want to subscribe people to a
list they didn't subscribe to, although I am considering it. Any
other approaches -- or do I have
David Andrews
At 03:29 PM 8/9/2009, Mark Sapiro wrote:
You can see the FAQ at http://wiki.list.org/x/TIA9, but the approach
there is essentially the same.
The alternative is to use Mailman's regular_exclude_lists feature
(under Non-digest options) as mentioned in the above FAQ, but with
150+
I have a problem, and don't know if there is an easy or viable
solution. I run a bunch of lists for an organization, over 150
lists, about 80 percent public and 20 percent private. Periodically
there are messages that need to go to everyone, or almost
everyone. However, people belong to
David Andrews dandr...@visi.com wrote:
I have a problem, and don't know if there is an easy or viable
solution. I run a bunch of lists for an organization, over 150
lists, about 80 percent public and 20 percent private. Periodically
there are messages that need to go to everyone, or almost
After applying the most recent Security Update to our Mac OS X Server
10.4.10 installation, we are encountering the following two problems
with Mailman lists hosted on this server that were working fine earlier:
1) Each message sent to any of our Mailman-based e-mail lists appears
to be
Alan Sill wrote:
After applying the most recent Security Update to our Mac OS X Server
10.4.10 installation, we are encountering the following two problems
with Mailman lists hosted on this server that were working fine earlier:
Since Apple's OS X Server Mailman is modified from our
On Mon, 31 Jul 2006, Mark Sapiro wrote:
There are several possibilities here.
3) if a message is shunted because SMTPDirect.py can't write the 'post'
log, it has already been sent, but OutgoingRunner.py doesn't know this
when it catches the exception and shunts the message. So those
Hi all,
Recently I found a fairly huge amount of files in the shunt queue (around
1500). All I could gather from the error log is that most of them were from an
old bug in parsing weird charsets and the later ones were due to the post and
smtp-failur logfiles being owned by root. So I fixed
Charles Sprickman wrote:
Then I ran bin/unshunt.
Then people started complaining that they were getting a few hundred old
messages. :)
There are several possibilities here.
1) users are complaining that they received messages posted long ago in
threads long since dead, not necessarily that
Hi y'all. Sorry if this is a little long.
The continuing problem is that 1) the welcome to the mailman list e-mail (in
German no less), 2) the first message I sent to the mailman list and then 3)
the administrative warning message from Maillman regarding a subsequent message
all go out to me
Dan Collins wrote:
The second message I sent to the mailman list had attachments for testing
scrub; over 50 mb no doubt. That subsequent e-mail has never arrived, but a
Mailman message informing me that there is an administrative task arrived. I
went to the web admin and discarded the
Reuben Meyer wrote:
I am having a problem with Mailman v 2.1.2
The problem is that every mail sent form the mailing list doubles
and the subscribers ends up receiving 2 mails in stead of one.
Does anybody know what causes this, and what I can do to fix it?
Careful inspection of Received:
I know this was asked but I do not see an answer - I have one list that
decides to send a lot more than one email to the same person - and it
just started.
Thoughts?
Thanks.
Lloyd F. Tennison
[EMAIL PROTECTED]
No trees were harmed in the transmission of this message.
However, a rather large
On 11 Jun 2004, at 13:35, Lloyd F. Tennison wrote:
I know this was asked but I do not see an answer - I have one list that
decides to send a lot more than one email to the same person - and it
just started.
Thoughts?
Have you checked the Mailman post and smtp logs, correlated with the
outbound
Since it only does it one one list I have to assume it is Mailman.
The SMTP log? What useful information about an email that has gone out is there? All
I ever get is weird errors that mailman creates by itself in there, i,e.
Jun 11 05:14:30 2004 (32685) All recipients refused: please run
On 11 Jun 2004, at 14:07, Lloyd Tennison wrote:
Since it only does it one one list I have to assume it is Mailman.
Or the data that Mailman has been fed such as the list subscriber
addresses or the incoming messages are crap.
The SMTP log? What useful information about an email that has gone
I use mailman from my web hosting service. I have several mail lists. One
consistently sends two messages to every user. Does anyone have a clue what
would cause this?
--
Mailman-Users mailing list
[EMAIL PROTECTED]
I am using Mailman 2.1.3 as provided by a web hosting service for several
mail lists. On one mail list, each time a message is posted, all
subscribers receive the message twice. Has anyone encountered this problem?
Any suggestions what to look for?
Please respond to me directly at [EMAIL
I am using Mailman 2.1.3 as provided by a web hosting service for several
mail lists. On one mail list, each time a message is posted, all
subscribers receive the message twice. Has anyone encountered this problem?
Any suggestions what to look for?
Please respond to me directly at [EMAIL
On Thu, 2003-07-17 at 16:46, Ed Wilts wrote:
I'm trying to discover why mailman sent the same message multiple times
to the same recipients. I don't believe it happened to every recipient
on my list, but as Murphy's Law would have it, some key people did get
the message more than once - some
I'm trying to discover why mailman sent the same message multiple times
to the same recipients. I don't believe it happened to every recipient
on my list, but as Murphy's Law would have it, some key people did get
the message more than once - some got it at least 3 times.
The message really was
At 3:46 PM -0500 2003/07/17, Ed Wilts wrote:
I'm trying to discover why mailman sent the same message multiple times
to the same recipients. I don't believe it happened to every recipient
on my list, but as Murphy's Law would have it, some key people did get
the message more than once - some
I've been using gate_news to port a number of news
groups to mailing lists. It's worked well for several
months, up until a week or so ago. I am using FreeBSD
4.3, Mailman 2.0.8, and Postfix (sorry, I forgot which
version).
Now, I'm re-getting older messages. Today, the 21st,
I'm getting
How do I avoid duplicate messages to users when sending to an umbrella list?
I've made announcement lists for different computational resources we have at
our site. My intention is that the users should subscribe to the list that
match the resource he/she is using. Moreover, I have an umbrella
38 matches
Mail list logo
