I am trying to forward emails to multiple mailboxes using the command:
dbmail-users -c user at domain dot com -t 2nd at domain dot com.
Nothing is happening, I don't see any new entries in the alias table
and emails are being delivered. I am running dbmail 2.0.4 and using
qmail to deliver to dbm
just as if the user was just created. What shoud it
be displaying?
Jamie
On 8/25/05, Paul J Stevens <[EMAIL PROTECTED]> wrote:
> If you're trying to add a forward for 'user at domain dot com' what does
> the output of dbmail-users -l 'user at domain dot com'
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
rror).
>
> capice?
>
> Now what is *your* setup? I'm guessing you're confused because you're
> using addresses as userids. (which makes sense, in a way...).
>
> And pulleez, be done with the at dot com trip'n. Some clarity will help;
> 'someuser a
I am currently running with qmail 1.03 in production with postgresql DB,
replicating to backup db using slony. No idea regarding your mailbox
questions. The server dbmail is running on houses all components, qmail,
dbmail, postgres and it is 1 GB RAM w/ 3.4 Ghz processor. The backup server
is ex
zamri,
I wrote a .NET change password function for dbmail on postgres. Let
me know if you still need it.
Jamie
On 12/31/05, Matthew T. O'Connor wrote:
> zamri wrote:
> > Is there any (official) plugin to change password for dbmail ? I found
> > one written by Matthew O'Connor but apparently
I am having a few issues with the pop3 daemon on 2.0.4 that looks to
be fixed in 2.0.5+. My question is would it be wiser to move to
2.1.3? I have redundant servers, could I run 2.0.4 and 2.1.3
simultaneously (2 day testing period)? Should I apply the 2.0.5+ bug
fixes and wait for 2.2.0?
On a s
