4) Using the Baruwa web-interface, I'm getting "Error connecting to server. check network!", when trying to perform a release, quarantine, delete, etc. on mails. I've browsed the web and suggestions are to disable Javascript, which seems to work. But is there any other workaround for this? It annoys me that I have to change Javascript setting all the time!

5) How do I setup my mailserver to work with this gateway/spamsnake?
5a) Are my clients still supposed to send mails via SMTP through my mailserver? Or should they now use the gateway/spamsnake to send mail from(SMTP)
5b) If I configure my mailserver to accept mails only from the gateway/spamsnake, how will my clients be able to connect via SMTP for sending email(if answer to 5a are yes).

6) I would love for someone (topdog), to check my server config and general setup via SSH, before throwing it into production, if this is by anyway possible.

Glad you got the snake up and running, although not completely 100% functional, I'm sure a few minor tweaks will fix your issues.

Add &> /dev/null at the end of all of your cronjobs, before the comment (#) statement to avoid the email messages.

The bayes user will be 1 because we specified root as the override user, who has access to the db, so that's normal.

Ok so you've figured out dcc and clamav, that's great. Give us a breakdown of your setup. What is it relaying to, are your clients internal, have you setup proper dns mx records for your mails to flow to the snake?

Once your mx records are setup properly, mails will start flowing to the snake. You'll have to setup the domains/transports in Baruwa for which you're relaying for and the destination smtp server, and after filtering, mails should flow to that server. A writeup can be found in the howto for the snake on how to do this.

Glad you got the snake up and running, although not completely 100% functional, I'm sure a few minor tweaks will fix your issues.

Add &> /dev/null at the end of all of your cronjobs, before the comment (#) statement to avoid the email messages.

The bayes user will be 1 because we specified root as the override user, who has access to the db, so that's normal.

Ok so you've figured out dcc and clamav, that's great. Give us a breakdown of your setup. What is it relaying to, are your clients internal, have you setup proper dns mx records for your mails to flow to the snake?

Once your mx records are setup properly, mails will start flowing to the snake. You'll have to setup the domains/transports in Baruwa for which you're relaying for and the destination smtp server, and after filtering, mails should flow to that server. A writeup can be found in the howto for the snake on how to do this.

Click to expand...

Thanks for your post Rocky!

I have 2 servers, the first server "node01" is running Debian with ISPConfig3 and acts as a LAMP basically. All my domains and mailboxes reside here.

The second server "mailgw" is running the spamsnake. Where I have setup "node01" as relay host in the Baruwa interface.

For now I have redirected only a test domains MX-record to the spamsnake. Mail seem to be relaying just fine.

But if I manually send mail through "node01" to the test domain, mails are also coming in. This is obvious, as I have not limited "node01" to recieve mail from the spamsnake only. This is what I'm trying to find out howto to do in a proper way.

Both server are "external", running as seperate machines with external global IP's.

I'm wondering if I need to specify anything special in this line in /usr/src/postfix.sh

Code:

postconf -e "mynetworks = 127.0.0.0/8, 192.168.0.0/24"

Obviously I'm not using 192.168.0.0/24 as my network, but I'm in doubt as what to enter here.

Your're having these issues because you've used the distributed deb package, which will install the distributed mailscanner version for ubuntu. Now, you have 2 instances of mailscanner, since you followed my guide. The distributed version will be an older version where as the tar version will be the latest version and is always installed in /opt. You can either remove the distributed version and create a symlink of /opt/MailScanner in /etc or get rid of both mailscanner and baruwa and reinstall them via the guide using my deb v102 package.

Your're having these issues because you've used the distributed deb package, which will install the distributed mailscanner version for ubuntu. Now, you have 2 instances of mailscanner, since you followed my guide. The distributed version will be an older version where as the tar version will be the latest version and is always installed in /opt. You can either remove the distributed version and create a symlink of /opt/MailScanner in /etc or get rid of both mailscanner and baruwa and reinstall them via the guide using my deb v102 package.

Rocky

Click to expand...

Ah, yes I see your point I'll stick to your upgrades!

I've uninstalled mailscanner and baruwa and installed from your guide 1.0.2. Everything seems to work as intended.

Thanks, all is working excellent, although a slight problem with the Altermime function.

ALL my mails have this message at the bottom, even the incoming ones:

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

I have double-checked the AlterMIME section of your guide, but without success. Any pointers here?