The following issue has been SUBMITTED.
==
http://www.dbmail.org/mantis/view.php?id=516
==
Reported By:bjohnson
Assigned To:
=
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=486
==
Reported By:zak
Assigned To:
=
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=503
==
Reported By:pgilmore-ellis
Assigned To:
On Wed, 2007-02-28 at 21:40 -0700, Bernard Johnson wrote:
> Bernard Johnson wrote:
> > Paul J Stevens wrote:
> >> Seems like a bug. I'm removing the umask call.
> >
> > I would think you want the logs written as 0600 since they may have
> > sensitive data from the logs.
> >
> >> Bernard Johnson
Bernard Johnson wrote:
> Paul J Stevens wrote:
>> Seems like a bug. I'm removing the umask call.
>
> I would think you want the logs written as 0600 since they may have
> sensitive data from the logs.
>
>> Bernard Johnson wrote:
>>> (dbmail 2.2.2)
>>>
>>> In server.c, line 450 you set the umask
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
(see Paul's mail below)
We've entered the next phase in this project and are preparing an
actual proposal now. However, we're still looking for good references!
It would be really helpful if those of you with large-ish installs would
be will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
We're happy to announce the release of dbmail-2.2.3
This is mainly a bugfix maintenance release.
Some noteworthy changes:
* dbmail-users now has a -n switch for dry-run mode
* dbmail.conf now has two new entries; encoding and
The following issue has been SUBMITTED.
==
http://www.dbmail.org/mantis/view.php?id=515
==
Reported By:lrosenman
Assigned To:
When a message is returned with return code 67 because of over quota, please
LOG IT to syslog at ANY log level..
Thanks!
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock
This is what will go into 2.2.3
Aaron Stone wrote:
> Replying to myself, the half-way option is to get -n working, but
> continue to default to the -y behavior.
>
> Note that this would still be the opposite behavior of dbmail-util, but
> would continue to be consistent with past version of dbmai
Replying to myself, the half-way option is to get -n working, but
continue to default to the -y behavior.
Note that this would still be the opposite behavior of dbmail-util, but
would continue to be consistent with past version of dbmail-users.
Yea, nay?
Aaron
On Wed, 2007-02-28 at 02:13 -0800,
Hi folks,
For too long, dbmail-users would bomb out if -n/-y were used. All
actions simply were executed without the -y required to make changes.
I've changed that in SVN, for the 2.2.3 release to have the new
behavior.
I want to give a heads up that wrapper scripts will be impacted because
with
12 matches
Mail list logo
