Hello,
I am a newbie here to dbmail. My issue thus far is only with
DBMailAdministrator. I have installed all the modules it depends on with
cpan and changed the DBMA.cgi shebang to point to /usr/bin/perl where perl
is at. When I point my browser to /domain/dbmailadministrator/DBMA.cgi I am
Okay, forget my first post. I needed to compile apache -with-cgi. I am in
now and starting to play.
_
From: Nathan Zabaldo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 15, 2004 11:13 PM
To: 'dbmail@dbmail.org'
Subject: DBMailAdministrator
Hello,
I am a newb
>Nathan, it sounds like you need to add Options ExecCGI.
Thanks for the reply. Compiling apache --with-cgi and adding the ExecCGI
Option was the key. I don't have any problems now with dbmailadministrator
it is working perfectly.
My issue now is sending mail to a [EMAIL PROTECTED] or using my s
>Personally, I use a MySQL table for both destinations and transport,
>so that I can add and remove domains without restarting postfix.
I was under the impression that this was what has happening. How do I tell
postfix to just use mysql and not mydestination? I am a novice here so
please dummy i
I have recently installed the following debian woody packages:
Mysql-server: 4.x
Postfix: 2.1.4-5
Postfix-mysql: 2.1.4-5
Dbmail-mysql: 1.2.11-1
I inserted the following lines into /etc/postfix/main.cf
mailbox_transport = dbmail_smtp:
local_recipient_maps = mysql:/etc/postfix/sql-recipients.cf
sq
>have you checked the location of your mysql socket?!
/var/run/mysqld/mysqld.sock
>what about posix?
Total novice here on linux. Not sure what that means?
>has dbmail/postfix the right to reach that socket file if it exists?
/var/run/mysqld is owned by mysql:mysql and the permissions are d
>comment out 'skip-networking' in /etc/mysql/my.cnf
Should this not be commented out?
>Otherwise the daemons wouldn't start, and you wouldn't be able to
>list users with dbmail-adduser.
I did not install debian's packages because it is the 1.x version of dbmail.
I compiled dbmail 2.x with the p
>Does the /var/run/mysqld/mysqld.sock exist?
Yes, yes, yes.
>Try that and then look at the logs again.
I tried adding the -v's to master.cf and I did get a lot more information,
but the problem is still postfix cannot connect to
/var/run/mysqld/mysqld.sock and then I get a temporary lookup failure and it
bounces the message. What is really, really odd is
Paul Stevens wrote:
>Boyohboy. So you build your own 2.x binaries and installed 1.2 right on top
>of them. Messy :-)
I suck. I am coming from the windoze world, but am trying to convert to
Linux. Pretty steep learning curve thus far, but I am getting there.
>Try adding to your sources.list:
>de
I turned up verbose logging in Postfix and now I can see postfix trying to
read sql-recipients. In mail.log I can see that it gets the user, password,
hosts, dbname, table, select_field, and where_field. Everything seems fine
there and then immediately below that there is a line that says...
"po
Paul,
Postfix's problem with delivering was by default the apt-get'd postfix
program smtp runs chrooted. I just had to change the "-" to an "n" and now
everything is working.
Thanks for all your help. I am going to start working on the pop before
smtp and other features so I may need more help,
If a user from a client like Thunderbird or Microsoft Outlook for example
connect via pop3, can dbmail be configured to delete the messages they
downloaded? Right now it seems that the messages just stay in the database.
Regards,
Nate
Steven Lynn wrote:
>Configure POP3 to remove messages from server upon download...
It is setup that way. I have cron job for dbmail-util to delete messages,
but I guess this doesn't happen immediately. The cron job was created by
the debian package.
dbmail-util is not working. I have my cron job setup, but I tried it
manually as well and it doesn't work. It semi-works.
>From /usr/sbin I ran dbmail-util -p, which is supposed to purge messages
with the delete status. The connection to the database opens. The
authentication works and I ge
Steven Lynn wrote:
>I always forget that the messages do not get deleted, they get marked for
deletion and will be deleted when dbmail-util >runs
dbmail-util doesn't seem to be working. I tried to run it manually to purge
messages marked for deletion. It says it connects and authenticates.
Leonel Nunez wrote:
>run dbmail-maintenance -cfpd so they get deleted from the database
I am running v2.0 for dbmail so I am using dbmail-util in place of
dbmail-maintenance, which has been renamed in v2.0. In any event, it does
the same thing, but the emails never get deleted. It says it found
Hi All,
I have dbmail, spamassassin, postfix up and running no problems whatsoever
for about a year now.
My question is regarding how I can spamassassin 3.03 to sa-learn spam
messages. Obviously I can't point it to the database to the offending spam,
but how do I get a message out of the d
Robert Claeson wrote:
>I'm sure there's a good way, but I tend to export the offending mail(s)
from my mail client (Apple Mail, which can export in Mbox format), scp it to
the server and run sa-learn on it there. Clumsy, but it works.
>I do it a few times a week so I can export a bunch of s
Thomas Mueller wrote:
>This can easily be done with a cron job:
>http://wiki.apache.org/spamassassin/RemoteImapFolder
I'm pretty sure I understand how fetchmail can help here with automation,
but I need a little clarification.
Do I still need to export emails from dbmail into an Mbox format in
Robert Claeson wrote:
>I'm sure there's a good way, but I tend to export the offending mail(s)
from my mail client (Apple Mail, which can export in Mbox format), scp it to
the server and run sa-learn on it there. Clumsy, but it works.
>I do it a few times a week so I can export a bunch of s
Paul J Stevens wrote:
>Sure: shared public folders.
>http://www.dbmail.org/dokuwiki/doku.php?id=shared-mbox
>Setup the acl so anyone can write to these boxes, but only a single
>dedicated user can read/update them. Use this dedicated user in your
>fetchmailrc to read the mailboxes and dump them
Paul J Stevens wrote:
>That is not correct. It should look like '#Public/Spam'. But it may well be
>sm's namespace handling is broken.
>I prefer fetchmailrc syntax:
>poll localhost with protocol imap
> user spamadmin mda "/usr/bin/sa-learn --spam --single"
> password secretpassword;
> folder
Paul J Stevens wrote:
>try: man fetchmailrc
Okay, I read through it this time. I understand what a fetchmailrc file is
now and how to construct it.
>Indeed. Quite idiotic.
Yes, extremely idiotic after reading the man.
>try putting this into a separate file like /etc/fetchmailrc
My file is co
Paul J Stevens wrote:
>-- first make sure the fetchmailrc file is not world readable.
>adduser fetchmail
>chown fetchmail /etc/fetchmailrc
>chmod 600 /etc/fetchmailrc
>-- the debian way of running in debug mode:
>su -c "/usr/bin/fetchmail --nosyslog --nodetach -v -v -f
>/etc/fetchmailrc" fetchm
I'm running dbmail v1.x with postfix on Debian Woody.
Situation:
Need to forward / alias an entire domain to another domain.
e.g.
[EMAIL PROTECTED] -> [EMAIL PROTECTED]
[EMAIL PROTECTED] -> [EMAIL PROTECTED]
Can this be done by the group_idnr?
I've been down for 24 hours all my users are dead in the water.
Installation:
os: debian
mysql 5.0x
dbmail 2.2.4
Used apt-get to install dbmail. Until upgrade I have had dbmail working for
several years on the 2.0 version. I ran the dbmail migration from
2.0-2.2script with no problems. When I
It's seem impossible to shut down imapd. When I run /etc/init.d/dbmail stop
everything fails to stop, but dbmail is still taking up all the processes.
On 3/13/07, Paul J Stevens <[EMAIL PROTECTED]> wrote:
Nathan Zabaldo wrote:
> I've been down for 24 hours all my users ar
On 3/13/07, Alexander Benaguev <[EMAIL PROTECTED]> wrote:
use "killall -KILL dbmail-imapd" and so on for other dbmail-* daemons
I had been trying killall with no success. I ended up rebooting the server
and now I have dbmail-util -by running no problems. When it is finished
running I will t
On 3/13/07, Paul J Stevens <[EMAIL PROTECTED]> wrote:
>sysadmin 101: killall -9 dbmail-imapd
Noted for future reference. Had just been trying killall dbmail-imapd and
then killall dbmail-lmtpd.
dbmail-util -by is still running. Hoping everything will start once it is
finished.
I run /etc/init.d/dbmail restart on each
daemon it states "failed". Can I no longer use init.d dbmail to restart or
do was not replaced during the debian apt-get install?
On 3/13/07, Nathan Zabaldo <[EMAIL PROTECTED]> wrote:
On 3/13/07, Paul J Stevens <[EMAIL PROTECTED]>
After getting dbmail 2.2.4 up and running dbmail cannot connect if there is
a password for the mysql dbmail user.
If I remove the password everything works great. I have tried using SET
PASSWORD to OLD PASSWORD, but it won't work.
I can connect using phpMyAdmin with passwords for the dbmail acc
On 3/13/07, Leander Koornneef <[EMAIL PROTECTED]> wrote:
>Could one of you (or both) send the output of "sh -x /etc/init.d/
dbmail- "?
mail:/var/log/dbmail# sh -x /etc/init.d/dbmail stop
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ IMAPD=/usr/sbin/dbmail-imapd
+ POP3D=/usr/sbin/dbmail-pop3d
+ LMTP
On 3/13/07, Paul J Stevens <[EMAIL PROTECTED]> wrote:
> Stop dbmail
I'll do this midnight. I copied the dbmail.conf pre-package that was in the
/etc/dbmail/ directory after apt-get install, which contained the new
settings not in the previous dbmail v2.0 conf.
What other settings would be
34 matches
Mail list logo
