On Fri, 05 Apr 2002 20:48:53 -0800
Chuq Von Rospach <[EMAIL PROTECTED]> wrote:
> On 4/5/02 8:41 PM, "Ron Jarrell" <[EMAIL PROTECTED]> wrote:
>> At which point he'll refuse to confirm your subscription unless you
>> can bring him a shrubbery.
> Almost makes me sorry I brought this up. Was just t
On Fri, 5 Apr 2002 21:17:50 -0500
Barry A Warsaw <[EMAIL PROTECTED]> wrote:
> I'd like to get some feedback on bug #223533:
>
>http://sourceforge.net/tracker/index.php?func=detail&aid=223533&group_id=103&atid=100103
> It's fairly old but it's complaining that there is no way to
> tell the di
On Fri, 5 Apr 2002 12:11:25 -0500
Jay R Ashworth <[EMAIL PROTECTED]> wrote:
> The problem is that they're already in a database (filePro for Unix on
> SCO 5, on a machine behind a Linux 7.1 firewall), and they want to be
> able to selectwhom to mail on an adhoc basis.
Sounds like a job for 2.1
On Fri, 5 Apr 2002 17:25:48 +0200
Norbert Bollow <[EMAIL PROTECTED]> wrote:
>> Improving the templating system (for MM3) is more than just picking
>> one and going with it. The real issue is that folks want to put all
>> kinds of web skins on Mailman, to integrate them into their own way
>> of
On Fri, 5 Apr 2002 10:19:09 -0500
Barry A Warsaw <[EMAIL PROTECTED]> wrote:
>> "DJ" == David Jeske <[EMAIL PROTECTED]> writes:
DJ> Also, in fishing through the TODO list, I notice that adding some
DJ> kind of templating system is still on there.
> Improving the templating system (for MM3)
On Thu, 04 Apr 2002 23:09:32 -0800
Chuq Von Rospach <[EMAIL PROTECTED]> wrote:
> On 4/4/02 10:49 PM, "J C Lawrence" <[EMAIL PROTECTED]> wrote:
>> Keep the just-hit-reply model,
> How about keeping the reply model, but requiring the reply come from
> the address being subscribed?
Problem: That
> "RJ" == Ron Jarrell <[EMAIL PROTECTED]> writes:
RJ> and be greeted by a grumpy gnome of a man named Melvin, who'll
RJ> shriek "What! What! Why do you all keep bothering me? Don't
RJ> you have enough to do without being on *another*
RJ> mailinglist??"
Check out Melvin!
htt
> "RJ" == Ron Jarrell <[EMAIL PROTECTED]> writes:
>> You don't. While the error message is misleading, your
>> config.db file will be automatically updated to config.pck the
>> first time you load your list (via web, qrunner, or command
>> line script).
RJ> Ah hah. And
On 4/5/02 9:56 PM, "Barry A. Warsaw" <[EMAIL PROTECTED]> wrote:
> List-* headers. I don't see where the other List-* headers make much
> sense for an admin message, but the List-ID header /does/ make sense
> for such a posting.
I agree the other headers shouldn't be there -- but most mail clien
> "AP" == Andrew Pimlott <[EMAIL PROTECTED]> writes:
AP> Another possibility would be to propose a revision to the
AP> RFC's that adds a header just for list messages. Then, at
AP> least you would have the force of an RFC behind you if people
AP> complain about another heade
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
CVR> I feel that flagging them with a list-id of foobar.domain.org
CVR> is incorrect, because the source is the server, not the
CVR> list. It's about the list, but not from the list. I think
CVR> that's an important dist
> "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
MM> I'll get someone to increase the page length to 100 bugs.
MM> No, don't thank me, I'm just glad I could help :-)))
Beauty. Okay, I'm done! :)
MM> Actually I've found this annoying too, to be honest.
MM> I guess one wa
At 08:48 PM 4/5/02 -0800, Marc MERLIN wrote:
>Right...
>
>You got instructions on how to unsubscribe when you subscribed (you should
>have read and saved the Email) and you get a reminder every month, with
>again, instructions on how to unsubscribe.
I like the ones who reply to a message posted t
On Fri, Apr 05, 2002 at 09:17:50PM -0500, Barry A. Warsaw wrote:
> I'm in a mad quest to reduce the number of open Mailman bugs to under
> 50 so it fits on one page.
(If someone's smart, he'll ask sourceforge to shorten the page
length every time Barry closes a bug.)
> It's fairly old but it's
> GK> OSError: [Errno 2] No such file or directory:
> GK> '/h/mailman/lists/test/config.pck'
>
> GK> because the configuration is stored as config.db.
>
> GK> How do I convert the config.db to config.pck ?
>
> You don't. While the error message is misleading, your config.db fil
On 4/5/02 8:48 PM, "Marc MERLIN" <[EMAIL PROTECTED]> wrote:
>> Pl unsubscribe my email address from your list with imm effect
>> failingwhich I will be contrained to initiate appropriate legal action as
>> may be advised.
>
> Right...
Heh.
I finally changed the standard footer on all of my l
On 4/5/02 8:41 PM, "Ron Jarrell" <[EMAIL PROTECTED]> wrote:
> At which point he'll refuse to confirm your subscription unless you can
> bring him a shrubbery.
Almost makes me sorry I brought this up. Was just trying to help. I sure
didn't expect the bloody spanish inquisition...
--
Chuq Vo
On Fri, Apr 05, 2002 at 11:41:35PM -0500, Ron Jarrell wrote:
> At 12:13 AM 4/5/02 -0500, Barry A. Warsaw wrote:
> >E.g. we could shut off email confirms altogether and force only web
> >confirmations. Or we could be more Majordomo-ish as JC describes.
>
> I think all potential subscribers to *an
On Fri, Apr 05, 2002 at 07:26:09PM -0800, Dan Mick wrote:
> > It's fairly old but it's complaining that there is no way to
> > tell the difference between a list posting and an administrative
> > message via the List-* headers.
>
> What's an "administrative message"?
message foo needs moderat
On Fri, Apr 05, 2002 at 11:50:35AM -0800, Bill Wagner wrote:
> > Then again, it'd be better if qmail could just be taught to
> > automatically recognize Mailman lists, but again, I don't know enough
> > about qmail to write the appropriate recipes.
>
> Are there no developers running qmail? I kn
At 12:13 AM 4/5/02 -0500, Barry A. Warsaw wrote:
>E.g. we could shut off email confirms altogether and force only web
>confirmations. Or we could be more Majordomo-ish as JC describes.
I think all potential subscribers to *any* mailman list should be required
to trek in person to a lonely aband
At 04:09 PM 4/4/02 -0500, Barry A. Warsaw wrote:
> GK> OSError: [Errno 2] No such file or directory:
> GK> '/h/mailman/lists/test/config.pck'
>
> GK> because the configuration is stored as config.db.
>
> GK> How do I convert the config.db to config.pck ?
>
>You don't. While the er
On 4/5/02 6:17 PM, "Barry A. Warsaw" <[EMAIL PROTECTED]> wrote:
> It's fairly old but it's complaining that there is no way to
> tell the difference between a list posting and an administrative
> message via the List-* headers. I think it's actually recommending to
> add another header(!) only
> I'd like to get some feedback on bug #223533:
>
>
http://sourceforge.net/tracker/index.php?func=detail&aid=223533&group_id=103&ati
d=100103
>
> It's fairly old but it's complaining that there is no way to
> tell the difference between a list posting and an administrative
> message via t
On Fri, Apr 05, 2002 at 09:17:50PM -0500, Barry A. Warsaw wrote:
> I'm in a mad quest to reduce the number of open Mailman bugs to under
> 50 so it fits on one page. I'm nearly there.
I'll get someone to increase the page length to 100 bugs.
No, don't thank me, I'm just glad I could help :-)))
I'm in a mad quest to reduce the number of open Mailman bugs to under
50 so it fits on one page. I'm nearly there.
I'd like to get some feedback on bug #223533:
http://sourceforge.net/tracker/index.php?func=detail&aid=223533&group_id=103&atid=100103
It's fairly old but it's complaining
> "BW" == Bill Wagner <[EMAIL PROTECTED]> writes:
BW> That did the trick! (BTW, I'm sure it's near the bottom of
BW> your TODO list, you might want to eventually update
BW> $MailmanHome in contrib/qmail-to-mailman.py to reflect MM's
BW> new $HOME of /usr/local/mailman).
Don
> "BW" == Bill Wagner <[EMAIL PROTECTED]> writes:
BW> Makes sense. Here's what's in logs/error (sorry for the
BW> formatting):
Hmm, this means your messages aren't getting unix-from headers from
your MTA. Can you send me a .db/.pck pair from your shunt directory?
And which MTA are
> "BW" == Bill Wagner <[EMAIL PROTECTED]> writes:
BW> mailmanctl is running and the cronjob's in place so I don't
BW> know the next step. I'm presuming that all messages go into
BW> the shunt dir first before being delivered, (is this
BW> incorrect?) but what would cause the
> "RJ" == Ron Jarrell <[EMAIL PROTECTED]> writes:
RJ> Ok. Diff against cvs again. Handles the VERP tokens just
RJ> fine. If I wasn't *still* here fiddling at 7am it'd probably
RJ> be a tad more elegant, but it work.
Thanks, I've just committed this to cvs.
-Barry
__
> "BW" == Bill Wagner <[EMAIL PROTECTED]> writes:
BW> That patch basically just changes it to point to mail/mailman
BW> now, right?
Check cvs because I also just caught up on a few changes that Ben
Gertzfield contributed.
>> From what I can tell, it's still not going to work.
> "BW" == Bill Wagner <[EMAIL PROTECTED]> writes:
BW> First off, I'm sorry if this isn't the appropriate forum, but
BW> I felt it more appropriate than mailman-users.
This one's fine!
BW> I'm running a Mandrake 8.0 box with qmail and have 2.0.9
BW> running fine but am testi
> "JP" == Jon Parise <[EMAIL PROTECTED]> writes:
JP> It looks like README.POSTFIX is missing a word in here. See
JP> the attached patch.
Fixed, thanks.
-Barry
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/
It looks like README.POSTFIX is missing a word in here. See the
attached patch.
--
Jon Parise ([EMAIL PROTECTED]) . Information Technology (2001)
http://www.csh.rit.edu/~jon/ : Computer Science House Member
Index: README.POSTFIX
On Fri, Apr 05, 2002 at 10:19:09AM -0500, Barry A. Warsaw wrote:
> > "DJ" == David Jeske <[EMAIL PROTECTED]> writes:
>
> DJ> Also, in fishing through the TODO list, I notice that adding
> DJ> some kind of templating system is still on there.
>
> Improving the templating system (for M
On Fri, Apr 05, 2002 at 12:24:38PM -0500, Barry A. Warsaw wrote:
> > "JRA" == Jay R Ashworth <[EMAIL PROTECTED]> writes:
> JRA> The problem is that they're already in a database (filePro
> JRA> for Unix on SCO 5, on a machine behind a Linux 7.1 firewall),
> JRA> and they want to be
Good morning,
First off, I'm sorry if this isn't the appropriate forum, but I felt it more
appropriate than mailman-users.
I'm running a Mandrake 8.0 box with qmail and have 2.0.9 running fine but
am testing 2.1b1 and have run into a problem.
When passing mail through qmail-to-mailman.py, lines
On 4/5/02 9:11 AM, "Jay R. Ashworth" <[EMAIL PROTECTED]> wrote:
> I know this is a pretty kettle of fish; anyone have any suggestions?
>
> I'm willing to take a swing at writing a Python module to encompass
> filePro if I have to do that, but I'm not sure that's enough here: the
> user data isn
> "JRA" == Jay R Ashworth <[EMAIL PROTECTED]> writes:
JRA> The problem is that they're already in a database (filePro
JRA> for Unix on SCO 5, on a machine behind a Linux 7.1 firewall),
JRA> and they want to be able to selectwhom to mail on an adhoc
JRA> basis.
JRA> This
I have a client who wishes to send a bunch of mail.
They're good little boys and girls; the address are all opt-in, to my
personal knowledge.
The problem is that they're already in a database (filePro for Unix on
SCO 5, on a machine behind a Linux 7.1 firewall), and they want to be
able to selec
> Improving the templating system (for MM3) is more than just picking
> one and going with it. The real issue is that folks want to put all
> kinds of web skins on Mailman, to integrate them into their own way of
> managing their sites. Some people don't care about the integration,
> and for the
> "DJ" == David Jeske <[EMAIL PROTECTED]> writes:
DJ> Also, in fishing through the TODO list, I notice that adding
DJ> some kind of templating system is still on there.
Improving the templating system (for MM3) is more than just picking
one and going with it. The real issue is that
> "GK" == Georg Koch <[EMAIL PROTECTED]> writes:
GK> but I cannot, because MailList.py stops with an uncatched
GK> exception first. __load is called from load like this:
| for file in (pfile, plast, dfile, dlast):
| dict, e = self.__load(file)
GK> so i
I've manually dug through one too many pipermail archives, so I've
decided it's time to help fix the problem by connecting a search index
to mailman/pipermail. I'm probably going to use mifluz (after I swig a
python wrapper for it). If anyone has this in progress or wants to
coordinate on it, drop
44 matches
Mail list logo
