Hi, Does anyone know why a mail to me is bounces? All mailingslist is sending me mail at "[EMAIL PROTECTED]" (a forward to another account on the same domain)
I recice all mails, I guess, but when I try to signup to the new qmailadmin-devel list, mail to me is bouncing...? Anyone? /Thomas This is a forwarded message From: Tom Collins <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Thursday, August 14, 2003, 1:55:49 AM Subject: : qmailadmin-devel member [EMAIL PROTECTED] bouncing - removed ===8<==============Original message text=============== It looks like there's a misconfiguration of your mail server that's preventing qmailadmin-devel messages from getting through. You might want to look into the problem and resubscribe to the list. Begin forwarded message: > From: [EMAIL PROTECTED] > Date: Tue Aug 12, 2003 8:35:25 PM America/Phoenix > To: [EMAIL PROTECTED] > Subject: qmailadmin-devel member [EMAIL PROTECTED] bouncing - removed > > Content-type: text/plain; charset=us-ascii > > This is a Mailman mailing list bounce action notice: > > List: qmailadmin-devel > Member: [EMAIL PROTECTED] > Action: Subscription removed. > Reason: Excessive or fatal bounces. > > > > The triggering bounce notice is attached below. > > Questions? Contact the Mailman site administrator at > [EMAIL PROTECTED] > > This message was created automatically by mail delivery software > (Exim). > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) > failed: > > [EMAIL PROTECTED] > SMTP error from remote mailer after STARTTLS: host lojmann.dk > [217.215.197.205]: > 454 TLS not available: missing RSA private key (#4.3.0): > retry timeout exceeded > > ------ This is a copy of the message, including all the headers. ------ > ------ The body of the message is 17798 characters long; only the first > ------ 10240 or so are included here. > > Return-path: <[EMAIL PROTECTED]> > Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.13] > helo=sc8-sf-list1.sourceforge.net) > by sc8-sf-list2.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 > (Debian)) > id 19mmHj-0005es-00 > for <[EMAIL PROTECTED]>; Tue, 12 Aug 2003 20:26:51 -0700 > Date: Tue, 12 Aug 2003 20:26:01 -0700 > From: [EMAIL PROTECTED] > Subject: qmailadmin-devel digest, Vol 1 #28 - 10 msgs > X-Mailer: Mailman v2.0.9-sf.net > MIME-version: 1.0 > Content-type: text/plain > To: [EMAIL PROTECTED] > Sender: [EMAIL PROTECTED] > Errors-To: [EMAIL PROTECTED] > X-BeenThere: [EMAIL PROTECTED] > X-Mailman-Version: 2.0.9-sf.net > Precedence: bulk > Reply-To: [EMAIL PROTECTED] > X-Reply-To: [EMAIL PROTECTED] > List-Help: > <mailto:[EMAIL PROTECTED]> > List-Post: <mailto:[EMAIL PROTECTED]> > List-Subscribe: > <https://lists.sourceforge.net/lists/listinfo/qmailadmin-devel>, > <mailto:qmailadmin-devel- > [EMAIL PROTECTED]> > List-Id: A list for the discussion of ongoing QmailAdmin development. > <qmailadmin-devel.lists.sourceforge.net> > List-Unsubscribe: > <https://lists.sourceforge.net/lists/listinfo/qmailadmin-devel>, > <mailto:qmailadmin-devel- > [EMAIL PROTECTED]> > List-Archive: > <http://sourceforge.net/mailarchive/forum.php?forum=qmailadmin-devel> > Message-Id: <[EMAIL PROTECTED]> > > Send qmailadmin-devel mailing list submissions to > [EMAIL PROTECTED] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/qmailadmin-devel > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of qmailadmin-devel digest..." > > > Today's Topics: > > 1. New list, vpopmail-devel (Tom Collins) > 2. [vchkpw] New list, vpopmail-devel (Tom Collins) > 3. Fwd: maildrop filter config gui? (Oden Eriksson) > 4. Re: [qmailadmin] maildrop filter config gui? (Oden Eriksson) > 5. qmailadmin alias' question (again) (Brian) > 6. Re: qmailadmin alias' question (again) (Jeff Hedlund) > 7. Should --enable-modify-quota be on by default? (Tom Collins) > 8. RE: Should --enable-modify-quota be on by default? (Benjamin > Tomhave) > 9. RE: Should --enable-modify-quota be on by default? (Benjamin > Tomhave) > 10. Re: Should --enable-modify-quota be on by default? (Tom Collins) > > --__--__-- > > Message: 1 > Date: Mon, 11 Aug 2003 21:21:15 -0700 > From: Tom Collins <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], > vpopmail list <[EMAIL PROTECTED]> > Subject: [qmailadmin-devel] New list, vpopmail-devel > Reply-To: [EMAIL PROTECTED] > > > --Apple-Mail-51-750497288 > Content-Transfer-Encoding: 7bit > Content-Type: text/plain; > charset=US-ASCII; > format=flowed > > By request, I've created vpopmail-devel on SourceForge as a companion > list to qmailadmin-devel. Those of you interested in vpopmail in > addition to qmailadmin should probably sign up. Michael Bowe has been > reviewing the source, and we have some work to do. > > http://lists.sourceforge.net/mailman/listinfo/vpopmail-devel > > The list we be focused on the ongoing development of vpopmail, > including discussions on how to implement new features, discussions of > bugs, and talk of optimizing or rewriting portions of the source. It > is NOT for questions regarding installation/configuration of vpopmail. > Please continue to use [EMAIL PROTECTED] for those questions. > > -- > Tom Collins > [EMAIL PROTECTED] > http://sniffter.com/ - info on the Sniffter hand-held Network Tester > --Apple-Mail-51-750497288 > Content-Transfer-Encoding: 7bit > Content-Type: text/enriched; > charset=US-ASCII > > By request, I've created vpopmail-devel on SourceForge as a companion > list to qmailadmin-devel. Those of you interested in vpopmail in > addition to qmailadmin should probably sign up. Michael Bowe has been > reviewing the source, and we have some work to do. > > > http://lists.sourceforge.net/mailman/listinfo/vpopmail-devel > > > The list we be focused on the ongoing development of vpopmail, > including discussions on how to implement new features, discussions of > bugs, and talk of optimizing or rewriting portions of the source. It > is NOT for questions regarding installation/configuration of vpopmail. > Please continue to use [EMAIL PROTECTED] for those questions. > > > -- > > Tom Collins > > [EMAIL PROTECTED] > > http://sniffter.com/ - info on the <bold>Sniffter</bold> hand-held > Network Tester > --Apple-Mail-51-750497288-- > > > > --__--__-- > > Message: 2 > Date: Mon, 11 Aug 2003 21:21:15 -0700 > From: Tom Collins <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], > vpopmail list <[EMAIL PROTECTED]> > Subject: [qmailadmin-devel] [vchkpw] New list, vpopmail-devel > Reply-To: [EMAIL PROTECTED] > > > --Apple-Mail-51-750497288 > Content-Transfer-Encoding: 7bit > Content-Type: text/plain; > charset=US-ASCII; > format=flowed > > By request, I've created vpopmail-devel on SourceForge as a companion > list to qmailadmin-devel. Those of you interested in vpopmail in > addition to qmailadmin should probably sign up. Michael Bowe has been > reviewing the source, and we have some work to do. > > http://lists.sourceforge.net/mailman/listinfo/vpopmail-devel > > The list we be focused on the ongoing development of vpopmail, > including discussions on how to implement new features, discussions of > bugs, and talk of optimizing or rewriting portions of the source. It > is NOT for questions regarding installation/configuration of vpopmail. > Please continue to use [EMAIL PROTECTED] for those questions. > > -- > Tom Collins > [EMAIL PROTECTED] > http://sniffter.com/ - info on the Sniffter hand-held Network Tester > --Apple-Mail-51-750497288 > Content-Transfer-Encoding: 7bit > Content-Type: text/enriched; > charset=US-ASCII > > By request, I've created vpopmail-devel on SourceForge as a companion > list to qmailadmin-devel. Those of you interested in vpopmail in > addition to qmailadmin should probably sign up. Michael Bowe has been > reviewing the source, and we have some work to do. > > > http://lists.sourceforge.net/mailman/listinfo/vpopmail-devel > > > The list we be focused on the ongoing development of vpopmail, > including discussions on how to implement new features, discussions of > bugs, and talk of optimizing or rewriting portions of the source. It > is NOT for questions regarding installation/configuration of vpopmail. > Please continue to use [EMAIL PROTECTED] for those questions. > > > -- > > Tom Collins > > [EMAIL PROTECTED] > > http://sniffter.com/ - info on the <bold>Sniffter</bold> hand-held > Network Tester > --Apple-Mail-51-750497288-- > > > > > > --__--__-- > > Message: 3 > From: Oden Eriksson <[EMAIL PROTECTED]> > Date: Tue, 12 Aug 2003 16:37:59 +0200 > To: [EMAIL PROTECTED] > Subject: [qmailadmin-devel] Fwd: maildrop filter config gui? > Reply-To: [EMAIL PROTECTED] > > > > ---------- Vidarebefordrat brev ---------- > > Subject: maildrop filter config gui? > Date: tisdagen den 12 augusti 2003 13.20 > From: Oden Eriksson <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > > Hi. > > I'm evaluating the "new" method of using maildrop+spamassassin, it > works > pretty well. But I was thinking it would be a great idea if a skilled > coder > would have the time to rip out the filtering functions from sqwebmail > so that > we could use it as a stand alone or in qmailadmin. Or even better make > a > smarter web gui as Mr. Sam's isn't. For example you cannot have one > named > rule with many exceptions. > > So, am I the only one that would like this? > > -- > Regards // Oden Eriksson, Deserve-IT.com > > ------------------------------------------------------- > > -- > Regards // Oden Eriksson, Deserve-IT.com > > > --__--__-- > > Message: 4 > From: Oden Eriksson <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Tue, 12 Aug 2003 16:44:47 +0200 > Cc: [EMAIL PROTECTED] > Subject: [qmailadmin-devel] Re: [qmailadmin] maildrop filter config > gui? > Reply-To: [EMAIL PROTECTED] > > tisdagen den 12 augusti 2003 16.41 skrev Jeff Hedlund: >> Oden Eriksson wrote: >>> I'm evaluating the "new" method of using maildrop+spamassassin, it >>> works >>> pretty well. But I was thinking it would be a great idea if a skilled >>> coder would have the time to rip out the filtering functions from >>> sqwebmail so that we could use it as a stand alone or in qmailadmin. >>> Or >>> even better make a smarter web gui as Mr. Sam's isn't. For example >>> you >>> cannot have one named rule with many exceptions. >>> >>> So, am I the only one that would like this? >> >> No, you are not the only one! It's a potential feature in the next >> development cycle for qmailadmin. >> >> Jeff > > x posting to [EMAIL PROTECTED], maybe we should > continue > it there. Well..., anyway..., I need this functionality badly and I > can help > if it's not related to actually write code ;) I tried to figure out > where the > magic is in the sqwebmail code but it's far to nested to me, hard to > follow... > > -- > Regards // Oden Eriksson, Deserve-IT.com > > > --__--__-- > > Message: 5 > Date: Tue, 12 Aug 2003 11:18:33 -0400 > From: Brian <[EMAIL PROTECTED]> > Organization: Adriance Memorial Library > To: [EMAIL PROTECTED] > Subject: [qmailadmin-devel] qmailadmin alias' question (again) > Reply-To: [EMAIL PROTECTED] > > So I think I found what someone used to use alias' for. > > When using the mail robot, (one of my users says) that he used to be > able to define an alias that went to multiple people, and then in the > robot use that alias. So that multiple people would get the 'message' > from the robot. > > Now obviously w/ the alias stuff removed, he's no longer able to do > this, and that I have to create this functionality for him by hand. > > Could they have done this? > > Brian > > > > --__--__-- > > Message: 6 > Date: Tue, 12 Aug 2003 12:05:01 -0400 > From: Jeff Hedlund <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: [qmailadmin-devel] qmailadmin alias' question (again) > Reply-To: [EMAIL PROTECTED] > > Brian wrote: >> So I think I found what someone used to use alias' for. >> >> When using the mail robot, (one of my users says) that he used to be >> able to define an alias that went to multiple people, and then in the >> robot use that alias. So that multiple people would get the 'message' >> from the robot. >> >> Now obviously w/ the alias stuff removed, he's no longer able to do >> this, and that I have to create this functionality for him by hand. >> >> Could they have done this? > > Yes, they could have. But they still should be able to. Just create a > forward that forwards to the users that want a copy, and put the > forward > in the robot "Send copy to". > > Jeff > > > > --__--__-- > > Message: 7 > Date: Tue, 12 Aug 2003 10:37:49 -0700 > From: Tom Collins <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [qmailadmin-devel] Should --enable-modify-quota be on by > default? > Reply-To: [EMAIL PROTECTED] > > I just got an email from someone who didn't know about the modify-quota > feature. > > I'm wondering if we should turn it on by default. I would think that >> 50% of users would make use of it, but more importantly, if you don't > know it's available, you might not go looking for it. If the modify > quota feature shows up unexpectedly, and you don't want it, you'll > definitely look at the configure options on how to remove it. > > I'm also thinking about rewriting the configure help to show the y/n > options like this: > > --disable-ezmlm-mysql Disable MySQL options for mailing lists. > --enable-no-cache Prohibit caching via http headers. > --disable-ipauth Disable IP address checks (NAT/proxy > systems may not use the same IP for the whole session). > --disable-user-index Don't display user index on show users > page. > --disable-modify-quota Allow domain admin (postmaster) to modify > user quotas. > --enable-domain-autofill Autofill the domain on login page based on > the URL hostname. > > By just listing the option to alter default behavior, I think we make > the options clearer. The old formats will still work, but I think that > it's easier to understand --disable-modify-quota than > --enable-modify-quota=n. > > I'm even tempted to change the options where you specify something to > use "with" and "without", and list the default in square brackets > (saving space used by "default is" on every line): > > --with-qmaildir={dir} Directory where qmail is installed > [/var/qmail]. > --with-maxusersperpage=15 Number of users to display at a time > [15]. > --with-maxaliasesperpage=25 Number of aliases to display at a time > [25]. > > My understanding of the configure script is that the following are > equivalent: > > --with-feature > --enable-feature > --with-feature=y > --enable-feature=y > > and: > > --disable-feature > --without-feature > --enable-feature=n > --with-feature=n > > I think we should use the one that makes the most sense (and is easiest > to read) in ./configure --help. > > Thoughts? > > -- > Tom Collins > [EMAIL PROTECTED] > http://sniffter.com/ - info on the Sniffter hand-held Network Tester > > > > --__--__-- > > Message: 8 > From: "Benjamin Tomhave" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: RE: [qmailadmin-devel] Should --enable-modify-quota be on by > default? > Date: Tue, 12 Aug 2003 12:36:20 -0600 > Reply-To: [EMAIL PROTECTED] > >> --with-feature >> --enable-feature >> --with-feature=y >> --enable-feature=y >> >> and: >> >> --disable-feature >> --without-feature >> --enable-feature=n >> --with-feature=n >> >> I think we should use the one that makes the most sense (and is >> easiest >> to read) in ./configure --help. >> >> Thoughts? >> > Personally, I'm a fan of using enable/disable w/o the =y/n ending for > switch > flags. For those flags with multiple values to be defined, then the > --with > flags can be handy, such as when specifying a path or option X of N, > etc. > > In terms of what's enabled/disabled by default, it would probably be > worthwhile to list out where things currently are set and then evaluate > based on consensus which ones make more sense as enabled, and which > ones > make more sense as disabled. For instance, in addition to the quota > support, if the help files were packaged with qmailadmin (will they be > ever?), then it might make sense to enable them by default, etc. > > > > --__--__-- > > Message: 9 > From: "Benjamin Tomhave" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: RE: [qmailadmin-devel] Should --enable-modify-quota be on by > default? > Date: Tue, 12 Aug 2003 15:19:46 -0600 > Reply-To: [EMAIL PROTECTED] > > btw, side-note on the --enable-modify-quota capability...even though my > default in vpopmail is 15MB, qmailadmin defaults to setting it at > NOQUOTA....this should not be the case, but should in fact be > consistent > with vpopmail... > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Behalf Of Tom >> Collins >> Sent: Tuesday, August 12, 2003 11:38 AM >> To: [EMAIL PROTECTED] >> Subject: [qmailadmin-devel] Should --enable-modify-quota be on by >> default? >> >> >> I just got an email from someone who didn't know about the >> modify-quota >> feature. >> >> I'm wondering if we should turn it on by default. I would think that >>> 50% of users would make use of it, but more importantly, if you don't >> know it's available, you might not go looking for it. If the modify >> quota feature shows up unexpectedly, and you don't want it, you'll >> definitely look at the configure options on how to remove it. >> >> I'm also thinking about rewriting the configure help to show the y/n >> options like this: >> >> --disable-ezmlm-mysql Disable MySQL options for mailing lists. >> --enable-no-cache Prohibit caching via http headers. >> --disable-ipauth Disable IP address checks (NAT/proxy >> systems may not use the same IP for the whole session). >> --disable-user-index Don't display user index on show users >> pag > > -- Tom Collins [EMAIL PROTECTED] http://sniffter.com/ - info on the Sniffter hand-held Network Tester ===8<===========End of original message text===========It looks like there's a misconfiguration of your mail server that's preventing qmailadmin-devel messages from getting through. You might want to look into the problem and resubscribe to the list.
Begin forwarded message:
From: [EMAIL PROTECTED]--
Date: Tue Aug 12, 2003 8:35:25 PM America/Phoenix
To: [EMAIL PROTECTED]
Subject: qmailadmin-devel member [EMAIL PROTECTED] bouncing - removed
Content-type: text/plain; charset=us-ascii
This is a Mailman mailing list bounce action notice:
List: qmailadmin-devel
Member: [EMAIL PROTECTED]
Action: Subscription removed.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
[EMAIL PROTECTED]
This message was created automatically by mail delivery software (Exim).
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]
SMTP error from remote mailer after STARTTLS: host lojmann.dk [217.215.197.205]:
454 TLS not available: missing RSA private key (#4.3.0):
retry timeout exceeded
------ This is a copy of the message, including all the headers. ------
------ The body of the message is 17798 characters long; only the first
------ 10240 or so are included here.
Return-path: <[EMAIL PROTECTED]>
Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.13] helo=sc8-sf-list1.sourceforge.net)
by sc8-sf-list2.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian))
id 19mmHj-0005es-00
for <[EMAIL PROTECTED]>; Tue, 12 Aug 2003 20:26:51 -0700
Date: Tue, 12 Aug 2003 20:26:01 -0700
From: [EMAIL PROTECTED]
Subject: qmailadmin-devel digest, Vol 1 #28 - 10 msgs
X-Mailer: Mailman v2.0.9-sf.net
MIME-version: 1.0
Content-type: text/plain
To: [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.0.9-sf.net
Precedence: bulk
Reply-To: [EMAIL PROTECTED]
X-Reply-To: [EMAIL PROTECTED]
List-Help: <mailto:[EMAIL PROTECTED]>
List-Post: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/qmailadmin-devel>,
<mailto:[EMAIL PROTECTED]>
List-Id: A list for the discussion of ongoing QmailAdmin development. <qmailadmin-devel.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/qmailadmin-devel>,
<mailto:[EMAIL PROTECTED]>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=qmailadmin-devel>
Message-Id: <[EMAIL PROTECTED]>
Send qmailadmin-devel mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/qmailadmin-devel
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of qmailadmin-devel digest..."
Today's Topics:
1. New list, vpopmail-devel (Tom Collins)
2. [vchkpw] New list, vpopmail-devel (Tom Collins)
3. Fwd: maildrop filter config gui? (Oden Eriksson)
4. Re: [qmailadmin] maildrop filter config gui? (Oden Eriksson)
5. qmailadmin alias' question (again) (Brian)
6. Re: qmailadmin alias' question (again) (Jeff Hedlund)
7. Should --enable-modify-quota be on by default? (Tom Collins)
8. RE: Should --enable-modify-quota be on by default? (Benjamin Tomhave)
9. RE: Should --enable-modify-quota be on by default? (Benjamin Tomhave)
10. Re: Should --enable-modify-quota be on by default? (Tom Collins)
--__--__--
Message: 1
Date: Mon, 11 Aug 2003 21:21:15 -0700
From: Tom Collins <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED],
vpopmail list <[EMAIL PROTECTED]>
Subject: [qmailadmin-devel] New list, vpopmail-devel
Reply-To: [EMAIL PROTECTED]
--Apple-Mail-51-750497288
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
By request, I've created vpopmail-devel on SourceForge as a companion
list to qmailadmin-devel. Those of you interested in vpopmail in
addition to qmailadmin should probably sign up. Michael Bowe has been
reviewing the source, and we have some work to do.
http://lists.sourceforge.net/mailman/listinfo/vpopmail-devel
The list we be focused on the ongoing development of vpopmail,
including discussions on how to implement new features, discussions of
bugs, and talk of optimizing or rewriting portions of the source. It
is NOT for questions regarding installation/configuration of vpopmail.
Please continue to use [EMAIL PROTECTED] for those questions.
--
Tom Collins
[EMAIL PROTECTED]
http://sniffter.com/ - info on the Sniffter hand-held Network Tester
--Apple-Mail-51-750497288
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
charset=US-ASCII
By request, I've created vpopmail-devel on SourceForge as a companion
list to qmailadmin-devel. Those of you interested in vpopmail in
addition to qmailadmin should probably sign up. Michael Bowe has been
reviewing the source, and we have some work to do.
http://lists.sourceforge.net/mailman/listinfo/vpopmail-devel
The list we be focused on the ongoing development of vpopmail,
including discussions on how to implement new features, discussions of
bugs, and talk of optimizing or rewriting portions of the source. It
is NOT for questions regarding installation/configuration of vpopmail.
Please continue to use [EMAIL PROTECTED] for those questions.
--
Tom Collins
[EMAIL PROTECTED]
http://sniffter.com/ - info on the <bold>Sniffter</bold> hand-held
Network Tester
--Apple-Mail-51-750497288--
--__--__--
Message: 2
Date: Mon, 11 Aug 2003 21:21:15 -0700
From: Tom Collins <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED],
vpopmail list <[EMAIL PROTECTED]>
Subject: [qmailadmin-devel] [vchkpw] New list, vpopmail-devel
Reply-To: [EMAIL PROTECTED]
--Apple-Mail-51-750497288
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
By request, I've created vpopmail-devel on SourceForge as a companion
list to qmailadmin-devel. Those of you interested in vpopmail in
addition to qmailadmin should probably sign up. Michael Bowe has been
reviewing the source, and we have some work to do.
http://lists.sourceforge.net/mailman/listinfo/vpopmail-devel
The list we be focused on the ongoing development of vpopmail,
including discussions on how to implement new features, discussions of
bugs, and talk of optimizing or rewriting portions of the source. It
is NOT for questions regarding installation/configuration of vpopmail.
Please continue to use [EMAIL PROTECTED] for those questions.
--
Tom Collins
[EMAIL PROTECTED]
http://sniffter.com/ - info on the Sniffter hand-held Network Tester
--Apple-Mail-51-750497288
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
charset=US-ASCII
By request, I've created vpopmail-devel on SourceForge as a companion
list to qmailadmin-devel. Those of you interested in vpopmail in
addition to qmailadmin should probably sign up. Michael Bowe has been
reviewing the source, and we have some work to do.
http://lists.sourceforge.net/mailman/listinfo/vpopmail-devel
The list we be focused on the ongoing development of vpopmail,
including discussions on how to implement new features, discussions of
bugs, and talk of optimizing or rewriting portions of the source. It
is NOT for questions regarding installation/configuration of vpopmail.
Please continue to use [EMAIL PROTECTED] for those questions.
--
Tom Collins
[EMAIL PROTECTED]
http://sniffter.com/ - info on the <bold>Sniffter</bold> hand-held
Network Tester
--Apple-Mail-51-750497288--
--__--__--
Message: 3
From: Oden Eriksson <[EMAIL PROTECTED]>
Date: Tue, 12 Aug 2003 16:37:59 +0200
To: [EMAIL PROTECTED]
Subject: [qmailadmin-devel] Fwd: maildrop filter config gui?
Reply-To: [EMAIL PROTECTED]
---------- Vidarebefordrat brev ----------
Subject: maildrop filter config gui?
Date: tisdagen den 12 augusti 2003 13.20
From: Oden Eriksson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Hi.
I'm evaluating the "new" method of using maildrop+spamassassin, it works
pretty well. But I was thinking it would be a great idea if a skilled coder
would have the time to rip out the filtering functions from sqwebmail so that
we could use it as a stand alone or in qmailadmin. Or even better make a
smarter web gui as Mr. Sam's isn't. For example you cannot have one named
rule with many exceptions.
So, am I the only one that would like this?
--
Regards // Oden Eriksson, Deserve-IT.com
-------------------------------------------------------
--
Regards // Oden Eriksson, Deserve-IT.com
--__--__--
Message: 4
From: Oden Eriksson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Tue, 12 Aug 2003 16:44:47 +0200
Cc: [EMAIL PROTECTED]
Subject: [qmailadmin-devel] Re: [qmailadmin] maildrop filter config gui?
Reply-To: [EMAIL PROTECTED]
tisdagen den 12 augusti 2003 16.41 skrev Jeff Hedlund:
Oden Eriksson wrote:
I'm evaluating the "new" method of using maildrop+spamassassin, it works
pretty well. But I was thinking it would be a great idea if a skilled
coder would have the time to rip out the filtering functions from
sqwebmail so that we could use it as a stand alone or in qmailadmin. Or
even better make a smarter web gui as Mr. Sam's isn't. For example you
cannot have one named rule with many exceptions.
So, am I the only one that would like this?
No, you are not the only one! It's a potential feature in the next
development cycle for qmailadmin.
Jeff
x posting to [EMAIL PROTECTED], maybe we should continue
it there. Well..., anyway..., I need this functionality badly and I can help
if it's not related to actually write code ;) I tried to figure out where the
magic is in the sqwebmail code but it's far to nested to me, hard to
follow...
--
Regards // Oden Eriksson, Deserve-IT.com
--__--__--
Message: 5
Date: Tue, 12 Aug 2003 11:18:33 -0400
From: Brian <[EMAIL PROTECTED]>
Organization: Adriance Memorial Library
To: [EMAIL PROTECTED]
Subject: [qmailadmin-devel] qmailadmin alias' question (again)
Reply-To: [EMAIL PROTECTED]
So I think I found what someone used to use alias' for.
When using the mail robot, (one of my users says) that he used to be
able to define an alias that went to multiple people, and then in the
robot use that alias. So that multiple people would get the 'message'
from the robot.
Now obviously w/ the alias stuff removed, he's no longer able to do
this, and that I have to create this functionality for him by hand.
Could they have done this?
Brian
--__--__--
Message: 6
Date: Tue, 12 Aug 2003 12:05:01 -0400
From: Jeff Hedlund <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [qmailadmin-devel] qmailadmin alias' question (again)
Reply-To: [EMAIL PROTECTED]
Brian wrote:
So I think I found what someone used to use alias' for.
When using the mail robot, (one of my users says) that he used to be
able to define an alias that went to multiple people, and then in the
robot use that alias. So that multiple people would get the 'message'
from the robot.
Now obviously w/ the alias stuff removed, he's no longer able to do
this, and that I have to create this functionality for him by hand.
Could they have done this?
Yes, they could have. But they still should be able to. Just create a
forward that forwards to the users that want a copy, and put the forward
in the robot "Send copy to".
Jeff
--__--__--
Message: 7
Date: Tue, 12 Aug 2003 10:37:49 -0700
From: Tom Collins <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [qmailadmin-devel] Should --enable-modify-quota be on by default?
Reply-To: [EMAIL PROTECTED]
I just got an email from someone who didn't know about the modify-quota
feature.
I'm wondering if we should turn it on by default. I would think that
50% of users would make use of it, but more importantly, if you don'tknow it's available, you might not go looking for it. If the modify
quota feature shows up unexpectedly, and you don't want it, you'll
definitely look at the configure options on how to remove it.
I'm also thinking about rewriting the configure help to show the y/n
options like this:
--disable-ezmlm-mysql Disable MySQL options for mailing lists.
--enable-no-cache Prohibit caching via http headers.
--disable-ipauth Disable IP address checks (NAT/proxy
systems may not use the same IP for the whole session).
--disable-user-index Don't display user index on show users page.
--disable-modify-quota Allow domain admin (postmaster) to modify
user quotas.
--enable-domain-autofill Autofill the domain on login page based on
the URL hostname.
By just listing the option to alter default behavior, I think we make
the options clearer. The old formats will still work, but I think that
it's easier to understand --disable-modify-quota than
--enable-modify-quota=n.
I'm even tempted to change the options where you specify something to
use "with" and "without", and list the default in square brackets
(saving space used by "default is" on every line):
--with-qmaildir={dir} Directory where qmail is installed
[/var/qmail].
--with-maxusersperpage=15 Number of users to display at a time
[15].
--with-maxaliasesperpage=25 Number of aliases to display at a time
[25].
My understanding of the configure script is that the following are
equivalent:
--with-feature
--enable-feature
--with-feature=y
--enable-feature=y
and:
--disable-feature
--without-feature
--enable-feature=n
--with-feature=n
I think we should use the one that makes the most sense (and is easiest
to read) in ./configure --help.
Thoughts?
--
Tom Collins
[EMAIL PROTECTED]
http://sniffter.com/ - info on the Sniffter hand-held Network Tester
--__--__--
Message: 8
From: "Benjamin Tomhave" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: RE: [qmailadmin-devel] Should --enable-modify-quota be on by default?
Date: Tue, 12 Aug 2003 12:36:20 -0600
Reply-To: [EMAIL PROTECTED]
--with-featurePersonally, I'm a fan of using enable/disable w/o the =y/n ending for switch
--enable-feature
--with-feature=y
--enable-feature=y
and:
--disable-feature
--without-feature
--enable-feature=n
--with-feature=n
I think we should use the one that makes the most sense (and is easiest
to read) in ./configure --help.
Thoughts?
flags. For those flags with multiple values to be defined, then the --with
flags can be handy, such as when specifying a path or option X of N, etc.
In terms of what's enabled/disabled by default, it would probably be
worthwhile to list out where things currently are set and then evaluate
based on consensus which ones make more sense as enabled, and which ones
make more sense as disabled. For instance, in addition to the quota
support, if the help files were packaged with qmailadmin (will they be
ever?), then it might make sense to enable them by default, etc.
--__--__--
Message: 9
From: "Benjamin Tomhave" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: RE: [qmailadmin-devel] Should --enable-modify-quota be on by default?
Date: Tue, 12 Aug 2003 15:19:46 -0600
Reply-To: [EMAIL PROTECTED]
btw, side-note on the --enable-modify-quota capability...even though my
default in vpopmail is 15MB, qmailadmin defaults to setting it at
NOQUOTA....this should not be the case, but should in fact be consistent
with vpopmail...
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Tom
Collins
Sent: Tuesday, August 12, 2003 11:38 AM
To: [EMAIL PROTECTED]
Subject: [qmailadmin-devel] Should --enable-modify-quota be on by
default?
I just got an email from someone who didn't know about the modify-quota
feature.
I'm wondering if we should turn it on by default. I would think that
50% of users would make use of it, but more importantly, if you don'tknow it's available, you might not go looking for it. If the modify
quota feature shows up unexpectedly, and you don't want it, you'll
definitely look at the configure options on how to remove it.
I'm also thinking about rewriting the configure help to show the y/n
options like this:
--disable-ezmlm-mysql Disable MySQL options for mailing lists.
--enable-no-cache Prohibit caching via http headers.
--disable-ipauth Disable IP address checks (NAT/proxy
systems may not use the same IP for the whole session).
--disable-user-index Don't display user index on show users pag
Tom Collins
[EMAIL PROTECTED]
http://sniffter.com/ - info on the Sniffter hand-held Network Tester
