Keith Hopkins (dbmail | 2 Sep 09:32 2007
Picon

Re: SASL with saslauth rimap

Michael Monnerie wrote:
> On Freitag, 31. August 2007 Jorge Bastos wrote:
>> # saslauthd -v
>> saslauthd 2.1.22
>> authentication mechanisms: sasldb getpwent kerberos5 pam rimap shadow
>> ldap
> 
> I have this (standard openSUSE 10.2 modules):
> # saslauthd -v
> saslauthd 2.1.22
> authentication mechanisms: getpwent pam rimap shadow ldap
> 

Hi Michael,

  Sorry, but what is the objective here?  If you want postfix with sasldb in SuSE 10.2, you don't need saslauthd
(and don't need to be concerned -v doesn't list sasldb).  If you want saslauthd with rimap, you don't need sasldb.

--Keith

Some notes:

man saslauthd
     sasldb     (All platforms)
                Authenticate against the SASL authentication database.  Note that this is probabally not what you want to
be using, and is even disabled at compile-time by default.  If you want to use sasldb with the SASL library,
you probably want to use the pwcheck_method of "auxprop" along with the sasldb auxprop plugin instead.

Options for /etc/sasl2/APP.conf
  http://www.sendmail.org/~ca/email/cyrus2/options.html
(Continue reading)

Paul J Stevens | 3 Sep 16:09 2007
Picon

announce: DBMail 2.2.6 release-candidate 2


Hi all,

I'm releasing the second release candidate for dbmail-2.2.6

For a full overview of changes please review the list of closed bugs in
the tracker, or check out the commit messages:

Closed bugs:

http://www.dbmail.org/mantis/changelog_page.php

GIT changes:

http://nfg3.nfgs.net/cgi-bin/gitweb.cgi?p=dbmail.git;a=log;h=dbmail_2_2

--
  ________________________________________________________________
  Paul Stevens                                      paul at nfg.nl
  NET FACILITIES GROUP                     GPG/PGP: 1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
Michael Monnerie | 4 Sep 12:56 2007
Picon

Re: announce: DBMail 2.2.6 release-candidate 2

On Montag, 3. September 2007 Paul J Stevens wrote:
> I'm releasing the second release candidate for dbmail-2.2.6

I've downloaded & installed it - you missed to update the version:
# /usr/sbin/dbmail-util -V
This is DBMail version 2.2.6-rc1

And I've tried running dbmail-util:

# dbmail-util -tubdpy

Repairing DBMAIL messageblocks integrity...
Ok. Found [0] unconnected messageblks.

Repairing DBMAIL physmessage integrity...
Ok. Found [91746] unconnected physmessages

Then I made a break, and tried with -rc1:

# dbmail-util -tubdpy

Repairing DBMAIL messageblocks integrity...
Ok. Found [0] unconnected messageblks.

Checking DBMAIL message integrity...
Ok. Found [0] unconnected messages.

Could there be a problem?

mfg zmi
(Continue reading)

Aleksander Kamenik | 4 Sep 17:03 2007
Picon

assertion tree != NULL failed

I have these in my dbmail.err. With rc1 and rc2 of 2.2.6.

(process:6151): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
NULL' failed

(process:6151): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
NULL' failed

(process:6151): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
NULL' failed

(process:6151): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
NULL' failed

(process:24532): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
NULL' failed

(process:24532): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
NULL' failed

Should I worry?

--

-- 
Aleksander Kamenik
system administrator
+372 6659 649
aleksander <at> krediidiinfo.ee

Krediidiinfo AS
http://www.krediidiinfo.ee/
(Continue reading)

Paul J Stevens | 4 Sep 17:24 2007
Picon

Re: assertion tree != NULL failed

No. Don't worry.

Aleksander Kamenik wrote:
> I have these in my dbmail.err. With rc1 and rc2 of 2.2.6.
> 
> (process:6151): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
> NULL' failed
> 
> (process:6151): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
> NULL' failed
> 
> (process:6151): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
> NULL' failed
> 
> (process:6151): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
> NULL' failed
> 
> (process:24532): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
> NULL' failed
> 
> (process:24532): GLib-CRITICAL **: g_tree_nnodes: assertion `tree != 
> NULL' failed
> 
> 
> Should I worry?
> 
> 

--

-- 
   ________________________________________________________________
(Continue reading)

umask | 4 Sep 18:04 2007
Picon

Re: assertion tree != NULL failed


04.09.07, 19:24, Paul J Stevens (paul <at> nfg.nl):

> No. Don't worry.

And that really happens? :-|

> > 

--
umask
Aaron Stone | 5 Sep 04:07 2007

Re: [Dbmail] Aaron on vacation

On Fri, 2007-08-24 at 19:30 +0000, Aaron Stone wrote:
> I'm going to be away from Sunday 8/26 - Wednesday 9/5.
> 
> See you all in September!

... and now I am drowning in email :-P

Aaron
Aaron Stone | 5 Sep 04:10 2007

Re: dbmail-sievecmd BUG

On Mon, 2007-08-27 at 02:52 +0200, Michael Monnerie wrote:
> On Montag, 27. August 2007 Josh Marshall wrote:
> > I believe if you omit the <filename> then it expects the script to
> > come from stdin. There are a lot of other utilities like this also
> > (e.g. grep)
> 
> You're right. I wasn't thinking about it as I forgot the script name, 
> but entered the filename, which is translated as scriptname then. That 
> made it confusing.

Right, the syntax is like this:

dbmail-sievecmd -u <username> -i [scriptname [filename]]

I could write a line to stderr like "Please enter data for <scriptname>
on stdin" which would clue you in to what's happening and give
confirmation of the file name, in case it turns out to be something
unexpected.

Aaron
Aaron Stone | 5 Sep 04:40 2007

Re: Sieve error

Yes, exactly.

On Wed, 2007-08-29 at 11:34 -0600, Jesse Norell wrote:
> Aaron was looking at that a little while ago, I believe the plan is to
> simply remove the error message completely, and deliver to INBOX.  I
> believe the issue is malformed email headers, not a problem in the sieve
> parser, so the question is simply how to handle "garbage in".
> 
> 
> On Wed, 2007-08-29 at 17:24 +0100, Jorge Bastos wrote:
> > Hi,
> > I have a few of there messages, but i have no idea how to find the
> > source of it.
> > Is this enought? (supose not).
> >  
> > Jorge
> >  
> > Your Sieve script [phpscript] failed to run correctly.
> > Messages will be delivered to your INBOX for now.
> > The error message is:
> > syntax error, unexpected '<', expecting ' <at> ' or '.'
> > 
Michael Monnerie | 5 Sep 10:32 2007
Picon

Re: dbmail-sievecmd BUG

On Mittwoch, 5. September 2007 Aaron Stone wrote:
> dbmail-sievecmd -u <username> -i [scriptname [filename]]
>
> I could write a line to stderr like "Please enter data for
> <scriptname> on stdin" which would clue you in to what's happening
> and give confirmation of the file name, in case it turns out to be
> something unexpected.

Yes, that could help resolve the confusion. I guess others will run into 
the same sometimes, so it's better to write that info. Maybe only write 
that info if the script was called from command line, not from within 
another script? I don't know how to do that, though. Possibly only 
write that message if stdin has no input available?

mfg zmi
--

-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0676/846 914 666                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: EA39 8918 EDFF 0A68 ACFB  11B7 BA2D 060F 1C6F E6B0
// Keyserver: www.keyserver.net                   Key-ID: 1C6FE6B0
_______________________________________________
DBmail mailing list
DBmail <at> dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Gmane