REQUEST WHY
--- ---
fix md5 Broken on Sparc (64bit, big endian).
(comments) No patch here, sorry, but we'll sure make
a login to our server available if you'd like
refer to:
https://mailman.fastxs.nl/pipermail/dbmail
Hello,
I'll throw out a comment, on a similar need we have,
and maybe they can both get solved together. We intend
to use [EMAIL PROTECTED] type usernames, but for some historic
accounts we still need to support a plain username (no
@domain) login, till we can get completely transitioned.
This
Outstanding issues from me:
account suspension - Temporarily suspends an email account so it can't
be retrieved or delivered to (non paying customers) without deleting the
account fully -- Patch sent previously, no comment so far from devel
autoconf fixes - added a couple more paths to the look
Hi,
i'm going home now; this is what i've gathered today:
REQUEST WHO WHY
multiple usernamesMarc Mackay uses 2 ISP's and 1
dbmail
MAIL_PORT & AUTH_PORT Philip Warner multiple pgSQL instan
On Wed, 2002-09-11 at 14:31, Philip Warner wrote:
>
> A few suggestions...
>
> 1. MAIL_PORT & AUTH_PORT
>
>
> We use multiple PostgreSQL instances on different ports; this is not
> uncommon and insulates one PostgreSQL instance from others. I am happy to
> submit (triv
me to :)
On Wed, 2002-09-11 at 21:27, Sam Przyswa wrote:
> Roel Rozendaal ([EMAIL PROTECTED]) écrivait:
> >
> >Hi,
> >
> >we do like this idea but i think it would be best to retain this in the
> >long-term todo list - that is not scheduling it for release 1.0. It simply
> >is a major change to th
Roel Rozendaal ([EMAIL PROTECTED]) écrivait:
>
>Hi,
>
>we do like this idea but i think it would be best to retain this in the
>long-term todo list - that is not scheduling it for release 1.0. It simply
>is a major change to the table structure. Besides we would like to discuss
>the current structu
Hi,
we do like this idea but i think it would be best to retain this in the
long-term todo list - that is not scheduling it for release 1.0. It simply
is a major change to the table structure. Besides we would like to discuss
the current structure to see what other optimizations/changes would be
f
When will be the next release of dbmail?
From:Dirk Meyer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Subject: ports/34505: New port: DBMAIL IMAP4rev1/POP3 mail servers
--- Original message text -
Synopsis: New port: DBMAIL IMAP4rev1/POP3 mai
Philip Warner ([EMAIL PROTECTED]) wrote:
>
>
>A few suggestions...
>
[...]
>4. Nice-to-have: break up mail headers into a table
>---
>
>ie. parse the mail headers and store (a copy?) in a separate table. eg.
>
>Create Table message_headers(id, messa
My variation on mail headers - make this optional. It adds no value for
packaged mail clients; offers terrific value for purpose built dbmail
(probably web mail) clients. Since I'm writing a webmail client in Python
right now, its on my mind. Re-parsing the headers is a minor pain but a
major p
A few suggestions...
1. MAIL_PORT & AUTH_PORT
We use multiple PostgreSQL instances on different ports; this is not
uncommon and insulates one PostgreSQL instance from others. I am happy to
submit (trivial) patches for this.
2. Support for choosing DB, Password, Port
Hi all,
indeed, as Marc pointed out, some structure and work is needed right now. My
idea of the previous TODO-list question was to be able to gather the essential
points to include for the final first release. New plan: I will scan all
replies to this message every day for requests. Just one l
13 matches
Mail list logo
