Paul J Stevens wrote:
Becki,
The CVE you refer to is *not* about dbmail. It's about Xmail, a different
product all together.
That said: don't use 1.2.11 on a new system. Use 2.0.6 instead. 1.2.x is old,
and not maintained any more.
Is there any known bug on 1.2.11 ?
Leonel
If there is I don't want to know about it :-)
Seriously though: 1.2 suffers from the sql-injection bug. The code
doesn't check i.e. whether the 'create' command for imap (which creates
mailboxes) doesn't contain malicious code. It is possible for attackers
to execute any kind of sql command:
some
Hello, everybody.
I'd like to ask about the update for the 2.0.x branch - when will it be
ready? Approximately ;-)
And, please, tell me where can I get the current patches for 2.0.6
(interested in "FreeBSD bugfixes") if there are any.
--
Best regards,
Danil V. Gerun.
smime.p7s
Descrip
Danil,
You can always pickup the latest snapshot. Since I don't think there are
any urgent pending matter regarding 2.0, I might as well release 2.0.7 I
guess.
Danil V. Gerun wrote:
> Hello, everybody.
>
> I'd like to ask about the update for the 2.0.x branch - when will it be
> ready? Approxim
What should dbmail-users -l at x dot comm be displaying if I
correctly setup mail forwarding using the -t switch?
Jamie
On 8/25/05, Jamie Doherty <[EMAIL PROTECTED]> wrote:
> I have pasted the session:
>
> [EMAIL PROTECTED] ~]# dbmail-users -c x at x -t y at y
> Opening
Jamie,
Forget about dbmail-users. Look at the tables directly. dbmail-users
won't show *everything*. In fact it doesn't show forwards at all (in 2.0).
if you want to have multiple users receive the same address:
1) two local dbmail users receive [EMAIL PROTECTED]
dbmail_users:
userid
Dbmail 2.0.7 released
This is a bugfix release only.
* Removed all unsafe code from the signal handlers. This should
mostly benefit FreeBSD users which may have suffered from unreliable
behaviour in the process pool code.
* Added 'ON UPDATE CASCADE' to all foreign key restraints in the
M
Paul J Stevens wrote:
Dbmail 2.0.7 released
This is a bugfix release only.
* Removed all unsafe code from the signal handlers. This should
mostly benefit FreeBSD users which may have suffered from unreliable
behaviour in the process pool code.
* Added 'ON UPDATE CASCADE' to all foreign k
Paul,
After analyzing the tables, I went ahead and added [EMAIL PROTECTED] as an
alias to the 2 mailboxes I wanted delivery to and that worked
perfectly. Your help is appreciated!
Jamie
On 9/5/05, Paul J Stevens <[EMAIL PROTECTED]> wrote:
> Jamie,
>
> Forget about dbmail-users. Look at the tab
Leonel Nunez wrote:
> to migrate from 2.0.6 to 2.0.7
> Is there a script to add the ON UPDATE CASCADE for PostgreSQL or
> we have to look at the create scripts to see those ALTERS :)
>
> or does not matter if those ON UPDATE CASCADE are not updated
Those ON UPDATE CASCADE-s where ad
> * Added 'ON UPDATE CASCADE' to all
> foreign key restraints in the MySQL (InnoDB) and Postgresql create_table
> files.
How to apply this to the existing tables?
11 matches
Mail list logo
