I have a VPS, meowc.at, which was running Ubuntu 10.04. I upgraded to
12.04, but now whenevenr I try to do anything to the filing system, it says
"Read-only file system".
However, mount seems to think it is read-write:
$ mount
/dev/xvda1 on / type ext3 (rw,relatime)
proc on /proc type proc (rw,noexec,nosuid)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
as does /proc/mounts:
$ cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=230128k,nr_inodes=57532,mode=755 0 0
devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=94732k,mode=755 0 0
/dev/disk/by-label/root / ext3
ro,relatime,errors=continue,barrier=1,data=ordered 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
Does anyone have an idea what I've done wrong and how I can fix it?
--
Phil Hunt, <cabalamat(a)gmail.com>
Hi,
As you may know, we have supported UK Direct Debit payments for
quite some time:
https://tools.bitfolk.com/wiki/Direct_Debit
It works well.
At the moment it's only available to customers with a UK bank
account though.
GoCardless are trialling their SEPA Direct Debits platform at the
moment, which would allow customers in countries that use the Euro
to also use the same Direct Debit payment method.
In order to judge whether this is a priority to work on I would be
most grateful if anyone who would be interested in switching to this
payment method would:
1. Visit:
https://tools.bitfolk.com/redmine/issues/123
2. Log in to it (usual BitFolk account credentials)
3. Vote it up.
Thanks!
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"I'd be happy to buy all variations of sex to ensure I got what I wanted."
— Gary Coates (talking about cabling)
_______________________________________________
announce mailing list
announce(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/announce
FYI: This isn't for my Bitfolk server, but one I have hosted elsewhere.
My home server is unable to connect to my primary mail server currently:
"421 Too many concurrent SMTP connections".
This is due to spammers who are literally spamming my primary mail
server so hard I can't send mail to it (9,472 spam messages rejected by
my server so far today as at 15:10). I had similar issues towards the
end of January: http://www.solutium.net/images/jan2014_spam_rejects.png
I do have some basic rules in Exim to reject based on SMTP protocol
violations (no stats on that unfortunately), but most of my spam
rejection is based on Spamassassin processing the email. I have
increased --max-children to 10, but am still getting "prefork: server
reached --max-children setting, consider raising it" in the logs, but am
now also getting other errors, e.g.:
Feb 16 12:21:55 quartz spamd[4090]: check: exceeded time limit in Mail::SpamAssassin::Plugin::Check::_eval_tests_type11_prineg400_set3, skipping further tests
Feb 16 12:21:56 quartz spamd[4119]: rules: failed to run BAYES_99 test, skipping:
Feb 16 12:21:56 quartz spamd[4104]: rules: failed to run BAYES_99 test, skipping:
Feb 16 12:21:56 quartz spamd[4104]: (__alarm__ignore__(10480)
Feb 16 12:21:56 quartz spamd[4119]: (__alarm__ignore__(10493)
and
Feb 16 12:41:28 quartz spamd[4090]: Issuing rollback() due to DESTROY without explicit disconnect() of DBD::mysql::db handle sa_bayes:localhost at /usr/share/perl5/Mail/SpamAssassin/Plugin/Bayes.pm line 1516, <GEN4204> line 2.
Can any one provide some hints for IPTables rules or Exim config to rate
limit my SMTP ports without interfering too much with normal mail
operations? Alternatively, any suggestions to help Spamassassin process
quicker/better?
On the Spamassassin side, I have shortcircuiting turned on (see below).
The server has 4GB RAM (free output below).
# free
total used free shared buffers cached
Mem: 4127104 3537512 589592 0 161452 2253820
-/+ buffers/cache: 1122240 3004864
Swap: 3903784 143636 3760148
# Some shortcircuiting, if the plugin is enabled
#
ifplugin Mail::SpamAssassin::Plugin::Shortcircuit
#
# default: strongly-whitelisted mails are *really* whitelisted now, if the
# shortcircuiting plugin is active, causing early exit to save CPU load.
# Uncomment to turn this on
#
shortcircuit USER_IN_WHITELIST on
shortcircuit USER_IN_DEF_WHITELIST on
shortcircuit USER_IN_ALL_SPAM_TO on
shortcircuit SUBJECT_IN_WHITELIST on
# the opposite; blacklisted mails can also save CPU
#
shortcircuit USER_IN_BLACKLIST on
shortcircuit USER_IN_BLACKLIST_TO on
shortcircuit SUBJECT_IN_BLACKLIST on
# if you have taken the time to correctly specify your "trusted_networks",
# this is another good way to save CPU
#
# shortcircuit ALL_TRUSTED on
# and a well-trained bayes DB can save running rules, too
#
# shortcircuit BAYES_99 spam
shortcircuit BAYES_00 ham
Thanks
Gavin
Hi,
A fairly non-technical friend of mine is looking for Joomla hosting.
Here's what he requires:
- Ability to point three different domains at it and have three
different Joomla sites.
- Joomla side of things managed, so no need for him to worry about
upgrades or anything else aside from styling it and putting
content in it.
- Fairly cheap.
Does anything like that exist that anyone could personally
recommend?
Is the managed bit at low cost (like Wordpress) even possible with
Joomla?
If not then I would be tempted to install Joomla for him and host it
myself, but it is for business purposes so that doesn't seem
appropriate or cost effective for me.
He is willing to pay, but not a large amount, and I do think it
shouldn't be much more expensive than a Wordpress blog with custom
URL per site.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
I use a managed email filtering service (Symantec.cloud - formerly MessageLabs) which obviates the need for checking quite so much. My exim server only accepts SMTP connections from designated IP addresses and runs spamassassin to pick up some of the false negatives that they let through but all of the RBL stuff is done upstream. It works very well.
Andrew
<div>-------- Original message --------</div><div>From: Keith Williams <keithwilliamsnp(a)gmail.com> </div><div>Date:17/02/2014 07:46 (GMT+00:00) </div><div>To: BitFolk Users <users(a)lists.bitfolk.com> </div><div>Subject: Re: [bitfolk] Spam overwhelming my mail server </div><div>
</div>I use SpamCop and SpamHaus RBLs
I am using Postfix so am not 100% about Exim, but I use a range of checks and reject mail from non existent domains and unauthorised pipelining. Possibly more but sitting here eating breakfast I can't remember LOL. As for fail2ban look here http://www.zaphinath.com/custom-filter-for-exim-through-fail2ban/
On 17 February 2014 00:05, Gavin Westwood <bitfolk-lists(a)gavinwestwood.me.uk> wrote:
Thanks everyone for your suggestions. As at 23:15 it's reached 24,648
rejected spam emails.
On 16/02/2014 15:28, Andy Bennett wrote:
> Just firewall everything for 12 hours. If that's not enough to encourage
> the spammers to give up then you can probably extend it a little more
> without having any remote mailservers bounce messages.
> During this time, legitimate mail should queue on the sending host and
> be retried for anywhere between 24 and 72 hours.
Unfortunately this wouldn't be satisfactory for my clients and, as this
is the second time in 3 weeks that it's been hit by this level of
inbound spam (it's not relay attempts - my server gives that short
shrift), doing that once a month would be both a pain and cause me to
get phone calls. As long as my clients get their messages in a
reasonably timely manner they are generally happy (mail does appear to
be getting through despite my home mail server's issues connecting).
On 16/02/2014 20:52, ed wrote:
> Not for SpamAssassin, but have you thought about using one of the
> RBLs? Then you'd block potential junk before you start spending CPU
> time on bayes filtering.
Currently I only use RBLs as part of the Spamassassin checks and
scoring. I'm worried about applying stricter RBL checks due to various
issues such as the lag or difficulty in removing entries and the poor
configuration of some of my clients' regular contact's mail systems and
lack of understanding on both sides when mail is rejected.
> Alternatively, you could try greylising, 4xx the sending mail server
> IP for thirty minutes on the first mail seen from it, then allow it.
> Often this helps as most exploited spam sources don't queue.
(Thanks to Ian for your reply on this too)
I will have a look at greylisting, but I recall from when lug.org.uk
implemented it that there was significant impact and delay with emails
coming through and again this will lead to issues with clients calling
me about emails that they were expecting.
On 16/02/2014 21:53, Keith Williams wrote:
> I think the only answer is a good multilayered approach. Use a couple
> of good RBLs.
Ed, Keith (and anyone else) - what RBLs do you consider "good" (taking
into account my previously mentioned concerns)?
> Then make sure you are doing all the checks on headers etc.
I've got several checks, but am always open to additional suggestions.
> Then into spamassassin. The next step is to use fail2ban, so that any
> particular IP can only be used by them a couple of times before being
> blocked at the firewall. This has limited usefulness tbh, because they
> are not using their own machines. What I have done is to research
> addresses and found that there are certain ISPs that keep appearing in
> spam but not ham. I then log and block them.
I have Fail2ban installed, but I don't have it checking Exim logs. I've
not found a config to do that (my regex foo is not strong), but I do
block IPs that are regular offenders within my IPTables , however as you
note, spammers use many different compromised IPs so that is of limited
value. I've blocked one or two ranges (e.g. Proxad's IPs), but again as
my initial point, banning whole IP ranges could impact on some of my
clients getting legitimate emails.
An interesting thing I have just found from analysing todays logs is
that almost all are being sent to email addresses (mostly rubbish names,
e.g. message IDs) at a single client's domain name. Is there a quick
way in Exim to apply additional rules just to one domain (such as
greylisting or strict application of RBLs)?
Thanks
Gavin
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
--
Keith Williams
Keith's Place www.keiths-place.co.uk
Tailor Made English www.tmenglish.org
West Norfolk RSPCA www.westnorfolkrspca.org.uk
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
I'm stuck on the old disk layout which is hiding 0.5GB of disk away from
me, and I think I'm going to buy a 5GB upgrade, so I wondered about
fixing all this in one go.
I don't want to reinstall the OS though, so my plan is request/get the
disk upgrade, then to boot into the rescue environment and as root,
cd myvpsfilesystem
tar -c . | ssh somewhereelse "cat > filesystem.tar"
Then do the Xen disk reset, allocate the new space, then boot to rescue
again, mkfs with label "root", then:
ssh somewhereelse "cat filesystem.tar" | tar -x
I've thought about the disk block ID being different after this, but
it's not in fstab or anywhere else I can find.
As I understand it pyGrub will also just work.
The question is, am I heading for any pitfalls?
Thanks for any opinions.
Chris Tallon
So, since staying with Debian Stable is nice but not very shiny I've
just set up, from scratch, Debian Jessie with a btrfs-root.
(BTW, Andy, the net-install of jessie doesn't work, or at least didn't
work as of yesterday. It failed to set up the network.)
Anyway, my goal was to have some of the nice new stuff in Jessie and
being able to do btrfs snapshots and send/receive for incremental
backups (rsync is nice, but block-level incremental backup is nicer.)
I first installed Debian Wheezy, with /dev/xdva1 as a 250MB /boot
partition with ext3 and /dev/xvda2 as btrfs for / - fortunately the
Wheezy installer supports btrfs[1] so I didn't really have to do
anything special apart from using two partitions instead of one.
After this I did a dist-upgrade from a minimal Wheezy to Jessie. This
was absolutely painless (thanks for the XZ-kernel pygrub-stuff Andy!)
and I was left with a Jessie-based system with /boot on ext3 and / as btrfs.
I then proceeded to overengineer everything and created btrfs subvolumes
for $HOME as well as for /etc - what can I say, I _like_
being able to snapshot things! (I did this manually, but I suppose I
could have done this at install-time as well. Doing "mv /etc /etc_old"
felt _weird_!)
An unexpected, but in hindsigt obvious, sideffect of making subvolumes
of /etc and $HOME was that snapshots of / (and hence btrfs send
/.rootsnap) doesn't include /etc and $HOME. I suppose I'll have to
overengineer my new backup-regime as well - it'll be a nice exercise :-)
Anyway, it works and I really like being able snapshot /etc before
installing updates or fiddling with configuration. I'm sure snapshots of
$HOME will also prove convenient.
- OM
[1] Newer kernels & btrfs-tools are nicer, and at some point btrfs in
Wheezy didn't support btrfs send/receive which is one of the things I
really want.
Since around 05:00 today I've seen a great increase in attacks against
httpd. I've currently got 18 IP addresses blocked by fail2ban (compared
with the usual one or two per day). I'm matching as follows:
failregex = \[client <HOST>\] File does not exist:.*(?i)admin.*
\[client <HOST>\] File does not exist:.*(?i)manager.*
\[client <HOST>\] File does not exist:.*(?i)setup.*
\[client <HOST>\] File does not exist:.*(?i)mysql.*
\[client <HOST>\] File does not exist:.*(?i)sqlweb.*
\[client <HOST>\] File does not exist:.*(?i)webdb.*
\[client <HOST>\] File does not exist:.*(?i)pma.*
\[client <HOST>\] File does not exist:.*(?i)vtigercrm.*
\[client <HOST>\] File does not exist:.*(?i)w00tw00t.*
\[client <HOST>\] File does not exist:.*(?i)xampp.*
\[client <HOST>\] File does not exist:.*(?i)phpTest.*
Most of the attacks are against phpmyadmin and phpTest and are
far-eastern IP addresses.
I'm not particularly concerned, just curious whether it's me being
targeted or just a sweep of Bitfolk subnets.
Thanks,
Mike
Hi David,
On Tue, January 21, 2014 12:10 pm, David Stark wrote:
> Typically in postfix this would be a content_filter directive, I had to
nmap to find the open ports but I'm still at a loss on how this should
be accessed, could anyone advise?
I've been using Andy's spamd service for a few years now and am happy to
share my method. There are many ways to skin this cat though so don't
assume this is the 'best' way, however it has worked faultlessly for me so
I wouldn't hesitate to recommend it.
My mail routing/processing path is as follows:
MAIL -> Postfix (via smtpd/port 25) -> spamc/spamd -> Postfix (via
sendmail) -> Procmail -> User
Note, in my setup Postfix doesn't actually perform any spam filtering but
rather runs it via Andy's spamd service only for the purpose of adding
spamassassin headers. I then use Procmail to deliver it to the user or, in
the case of identified spam, handle it accordingly (see below).
So, to tell Postfix to send all incoming mail via the spam check I
modified /etc/postfix/master.cf to read:
smtp inet n - - - - smtpd
-o content_filter=spamcheck
spamcheck unix - n n - - pipe
flags=Rq user=spamcheck
argv=/etc/postfix/spamcheckscript.sh -f ${sender} ${recipient}
My /etc/postfix/spamcheckscript.sh looks like the following, the comments
of which hopefully explain it:
#!/bin/sh
# spamcheckscript.sh Mathew Newton v0.1 08/03/2010
#
# Script to submit mail for remote spam checking via spamc, handling #
errors and responses accordingly without letting unchecked mail through #
# Requires creation of 'spamcheck' system user and
/var/spool/spamchecktemp
# directory (owned by spamcheck:nogroup, permissions 0700)
#
# Intended to be called by Postfix's master.cf using the pipe command.
Test by
# by hand with /path/to/spamcheckscript.sh -f <sender> <recipient> <
message-file
# Set file locations and arguments
INSPECT_DIR=/var/spool/spamchecktemp
SPAMC="/usr/bin/spamc -x -d spamd.lon.bitfolk.com -u Debian-exim"
SENDMAIL="/usr/sbin/sendmail -oi -G"
LOGGER="/usr/bin/logger -s -p mail.warning -t spamcheckscript"
# Exit code(s) from /usr/include/sysexits.h
EX_TEMPFAIL=75
# Create a temporary file to store the spamc output (the scanned/modified
message)
cd $INSPECT_DIR || {
$LOGGER "$INSPECT_DIR does not exist - nowhere to create temporary
storage file"; exit $EX_TEMPFAIL; }
SPAMC_OUTPUT="`mktemp -p $INSPECT_DIR`" || {
$LOGGER "Cannot create temporary storage file"; exit $EX_TEMPFAIL; }
# Clean up temporary file however the script ends
trap "rm -f $SPAMC_OUTPUT" 0 1 2 3 15
# Submit mail for scanning, store the result (output) and assess response
(status code)
# Code will be 0 for a success (whether that be spam or ham)
# Non-zero code (failure of some sort) will return $EX_TEMPFAIL thus
causing Postfix to retry later
$SPAMC > $SPAMC_OUTPUT
RETURN="$?"
if [ "$RETURN" != 0 ]; then
$LOGGER "Temporary SpamAssassin execution failure (spamc returned
error code
$RETURN - see /usr/include/sysexits.h) - will retry later"
exit $EX_TEMPFAIL
fi
# Optional success logging statement (comment out if not required) $LOGGER
"Spamc returned code $RETURN (this does not reflect the level of spam
suspicion - the analysis and score will be added to the message headers).
Proceeding with mail delivery."
# Mail scanned; proceed with delivery (with the headers modified by
SpamAssassin)
$SENDMAIL "$@" < $SPAMC_OUTPUT
exit $?
The script finishes off by submitting the message back to Postfix, but via
sendmail and thus doesn't end getting checked again and stuck in a loop!
The final step for Postfix is to deliver it to procmail - this is achieved
with the following in /etc/postfix/main.cf:
mailbox_command = procmail -a "$EXTENSION"
I use procmail for final delivery so that I can perform whatever filtering
I require e.g. out of office replies, mailing list postings to a certain
folder, triggering SMS reports on selected e-mails etc. For the spam
filtering aspect the following system-wide configuration in
/etc/procmailrc directs mail accordingly (comments kept for guidance and
alternative options):
# /etc/procmailrc - System-wide procmail config file
# Used as an alternative to Postfix's 'local' delivery agent in order to move
# tagged spam (>5pts) into a user's Spam folder, and 'super spam' (>10pts)
# somewhere else (e.g. /dev/null, another mailbox, etc - see below) #
Recipes (rules) in here take precedence over per-user procmailrc files #
(the recipient user's recipes are effectively tagged on the end) #
Processing will stop after a receipe has 'fired' (e.g. delivered)
# Set the 'ORiGinal MAILbox' as this is where mail will be dropped if the
mail
# cannot be delivered (if the disk is full it won't help much so will bounce)
ORGMAIL=$HOME/Maildir/
# Default mailbox to use (set to be the same as above) if no recipes match
DEFAULT=$ORGMAIL
# Set system-wide logfile (intended only really to be used for testing) #
Needs to be world-writable if we've set DROPPRIVS=YES as Procmail runs as
# the recipient user? Root-only reads/writes are advised for privacy purposes
LOGFILE=/var/log/procmail.log
# Include an abstract of each delivered message to the logfile
# Shows From:, Subject:, folder/file it was delivered to and the size (bytes)
LOGABSTRACT=all
# Keep root privileges for now to allow 'super spam' to be stored outside of
# the original recipient's mailbox (particularly if we have a dedicated #
spam mailbox without it having to be world writable)
# Also good if performing detailed logging (in a root-read-only logfile) #
We will drop the privileges later (uncomment the line below to drop now)
#DROPPRIVS=YES
# Set default mask for message files to ugo=rw (the default is u=rw but I
# want to store system-wide 'super spam' in one of my mail folders hence I
# need to be able to read/delete it despite it being owned by root:mail) #
UMASK value will be subtracted from 777 to leave the mask to be used #
(e.g. 000 gives 777 i.e. rwxrwxrwx although I think Procmail uses the x
bits)
# Will return to the default (077 i.e. rw-------) later
UMASK=000
# Detect and handle all 'super spammy' (>10pts) mail to a central storage
area
# Option 1: Bin it permanently (in /dev/null)
# Option 2: Place in a dedicated spam mailbox (e.g. /var/spool/spambin/) #
Option 3: Forward to a dedicated spam address
# Option 4 (Chosen): Place in a dedicated folder in my mailbox
:0:
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*
/home/mathew/Maildir/.Spam-SystemTrashed/
# Option 1: Bin it permanently (in /dev/null)
#:0:
#* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*
#/dev/null
# Option 2: Place in a dedicated spam mailbox (e.g. /var/spool/spambin/) #:0:
#* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*
#/var/spool/spambin/
# Option 3: Forward to a dedicated spam address
#Don't use lockfile (i.e. no trailing : below)
#:0
#Detect 'super spam' but only if it hasn't already been through this recipe
#* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*
#* !^X-Loop: definitespam(a)newtonnet\.co\.uk
#Add a loop-detection header before forwarding it on (to avoid loops however
#it still seems to loop if the original recipient was me as that's where the
#'forwardee' will be redirected to)
#Note: Requires a recipe in my .procmailrc to filter this off to a specific
#folder based on the detection of the X-Loop header
#| formail -A "X-Loop: definitespam(a)newtonnet.co.uk" | /usr/sbin/sendmail
-oi definitespam(a)newtonnet\.co\.uk
# Return the mask to default (i.e. recipient user rw only) from here on
UMASK=077
# Drop any high(er)-level privileges from here on so as to store mail # as
the recipient user (and group)
DROPPRIVS=YES
# Detect and deliver tagged spam (>5pts) into the recipient's Spam folder
# If the folder doesn't exist it will be created, but not subscribed to -
# force a subscription by adding 'Spam' to the user's subscriptions file #
e.g. echo Spam >> ~<user>/Maildir/subscriptions or use a client
# Squirrelmail will automatically mark the 'Spam' folder as special hence
# carry it at the top of the folder list
# Note 1: Could look for ^X-Spam-Flag: YES (which defaults to 5 and above)
# but using stars allows me to tweak if necessary
# Note 2: Needs loop-detection activating if using Option 3 (forwarding) for
# the 'super spam' test above
:0:
* ^X-Spam-Level: \*\*\*\*\*
$HOME/Maildir/.Spam/
# Note: If processing gets this far (i.e. not spam) then the message is #
delivered to $DEFAULT (i.e. the user's mailbox) unless a recipient's #
.procmailrc instructs otherwise
And that's it! Ham gets delivered as normal, suspect spam (5-9 points)
gets put in the user's Spam folder and 'definite' spam (>10 points) gets
put into a Spam-SystemTrashed folder in my mailbox which gets
automatically pruned of old content. The reason I did this was so that
nothing got outright rejected and I would always be able to recover a
false positive for users even if it somehow failed the spam test
massively. In practice this hasn't been necessary but it doesn't cause any
issue other than having a message folder with 30k messages in it at any
one time!
Hope that helps, if only as food for thought. I'd be happy to provide
further details if required.
Mathew
Hey guys
I've deployed a simple deb box and iredmail and migrated my accounts in
happily now.
(iRedMail is a lazy script to deploy postfix, dovecot, clamd,
spamassasin, roundcube and so fourth)
Everything works ok but I'd like to stop swapping now and try and use
the shared spamassasin mentioned here:
http://www.bitfolk.com/customer_information.html#toc_2_SpamAssassin
Typically in postfix this would be a content_filter directive, I had to
nmap to find the open ports but I'm still at a loss on how this should
be accessed, could anyone advise?
I thought it would be something like this but I'm pretty sure not as
that port is closed and theres mention of usernames:
content_filter = smtp-amavis:[85.119.80.248]:10024
or: "content_filter = scan:[85.119.80.248]:XXX" ?
I have only done a basic google on this but was wondering if maybe I'm
barking up the wrong tree..
I'd really really love if we had shared amavis/clamd as thats a major
mem hog
Cheers
-David
