Hi,
http://mailscannermrtg.sourceforge.net/
Setting up a new mail gateway. It comes to me as a 'nice to have'.
Thank you,
P.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
After your commit, I now get an error during staging:
(00:00:54)
===
(00:00:54) ===
(00:00:54) ===> Staging for MailScanner-5.0.3_1
(00:00:54) ** Missing /usr/ports/m
On 28-7-2017 22:48, Chris Rees wrote:
> I've committed a fix using @sample for the config files, and fixed the
> regexes for paths. @sample keyword was made for ports like this...
>
> The port will no longer destroy your configuration.
>
> Cheers,
>
> Chris
Good news, Chris. Thanks for your e
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
t has
worked well.
I've marked it IGNORE and will fix it as quickly as I can.
Cheers,
Crhis
DutchDaemon - FreeBSD Forums Administrator wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19-6-2017 07:18, Jeff Sickel wrote:
The MailScanner-5.0.3 update didn’t keep the /usr/local
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19-6-2017 07:18, Jeff Sickel wrote:
> The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD
> standard namespace in place. I spent quite a bit of time correcting the perl
> scripts to pick up the /usr/loca
Would you have a look of this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219938
or file a patch to fix it ?
Thanks !
wen
2017-06-19 13:18 GMT+08:00 Jeff Sickel :
> The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD
> standard namespace in place. I
The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD
standard namespace in place. I spent quite a bit of time correcting the perl
scripts to pick up the /usr/local install locations after the upgrade. The
configuration files and other core pieces of MailScanner seem to
Hi!
> Thank you for maintaining!
> I'm wondering if there are any plans to update mailscanner to 4.86.1-1 or v5.
If you submit a patch via bugs.freebsd.org, that would be very helpful.
--
p...@opsec.eu+49 171 3101372 4
Hi,
Thank you for maintaining!
I’m wondering if there are any plans to update mailscanner to 4.86.1-1 or v5.
Best,
Ruud
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Hi Adam,
Unfortunately, I no longer have regular access to a FreeBSD or
MailScanner system. I'd love to be able to keep this up to date, but I
moved to a new position and just can't give it the attention it needs.
It would be great if somebody would like to take over maintainer stat
On Fri, 18 Dec 2015 00:31:48 +0100,
Adam Bernstein wrote:
>
> Howdy. We've noticed the MailScanner port has fallen way behind the
> latest MS release, as 4.84.6 is > 2.5 years old - is this port no
> longer being maintained? I can't find any info on the lists.
>
Howdy. We've noticed the MailScanner port has fallen way behind the
latest MS release, as 4.84.6 is > 2.5 years old - is this port no longer
being maintained? I can't find any info on the lists.
There's lots of bug fixes, including one to get rid of the slew of "use
IO
Dear Mr. Kobb,
A new version of MailScanner, version 4.85.2-3, has been released some time ago.
See also https://www.mailscanner.info/downloads/.
Are there any plans in the near future to also update the FreeBSD port?
Best regards,
Adri Koppes
On 5/15/2011 6:38 AM, Chris Rees wrote:
Hi all,
I've just finished working on the update for MailScanner, and I've
changed a few things that have annoyed me loads-- perhaps it's been
irritating for you too!
I've removed the extra targets for initial configuration etc, a
Hi all,
I've just finished working on the update for MailScanner, and I've
changed a few things that have annoyed me loads-- perhaps it's been
irritating for you too!
I've removed the extra targets for initial configuration etc, and
moved them into a pkg-install script, whic
Whooo! That's awesome!
Big thanks to Julian, Mike and everyone else who helped with *finally*
getting this sorted out.
Kind regards,
mog.
Mike Jakubik wrote:
Just wanted to mention to all the frustrated mailscanner users that have
been having issues when updating perl, the proble
Just wanted to mention to all the frustrated mailscanner users that have
been having issues when updating perl, the problem has finally been fixed.
I have submitted a pr to update the port, you will see this fix in version
4.79.4.
The problem was caused by the way mailscanner code behaved when it
Hi all,
I need some help with this one please, MailScanner and Perl are really
starting to tick me off :(
I upgraded MailScanner a little while along with a number of other
ports, which unfortunately included a micro update to Perl. On FreeBSD
it went from perl-5.10.0 to perl-5.10.1, and
On Wed, 04 Nov 2009, andrea crisanti wrote:
> Dear Maintainers of MailScanner port,
> I updated the Sophos virus scan engine to version 4.47 on a
> computer running FreeBSD 7.2-STABLE amd64.
>
> The new engine uses, besides the old virus databases files, new
> file
Dear Maintainers of MailScanner port,
I updated the Sophos virus scan engine to version 4.47 on a computer
running FreeBSD 7.2-STABLE amd64.
The new engine uses, besides the old virus databases files, new files
called xvd??.vdb
To have it working I had to modify the script sophos
On Thu, September 17, 2009 11:08 am, Johan Hendriks wrote:
> Mike Jakubik schreef:
>> On Thu, September 17, 2009 6:43 am, Johan Hendriks wrote:
>>
>>> Hello First off all, sorry to bother you this way.
>>> Secondly thanks for your time on creating the Ma
On Fri, August 28, 2009 9:11 am, Jerry wrote:
> On Fri, 28 Aug 2009 10:37:29 +0100
> "Richard Mealing" wrote:
>
>> I am trying to download the latest beta for mailscanner, which on the
>> mailscanner site it suggests is - Version 4.78.14-1 for Solaris /
>> BS
On Fri, 28 Aug 2009 10:37:29 +0100
"Richard Mealing" wrote:
> I am trying to download the latest beta for mailscanner, which on the
> mailscanner site it suggests is - Version 4.78.14-1 for Solaris /
> BSD / Other Linux / Other Unix
> <http://mailscanner.info/files/
Hello,
I am trying to download the latest beta for mailscanner, which on the
mailscanner site it suggests is - Version 4.78.14-1 for Solaris / BSD /
Other Linux / Other Unix
<http://mailscanner.info/files/4/tar/MailScanner-install-4.78.14-1.tar.g
z>
When I search the port tree I on
>
> I also did fresh installs on FreeBSD 6.x and 7.x with the new perl 5.8.9
> at that time and MailScanner refused to work.
> 5.8.9. just did not work!
>
> here is the thread off that on the ports list
> http://lists.freebsd.org/pipermail/freebsd-ports/2009-February/052959.htm
Jeremy wrote:
>> >>>>
>> >>>>
>> >>>>> If the existing maintainer has disappeared, one option would be for
>> >>>>> you to take over maintainership: Upgrade mailscanner yourself and
>>
, and I will try 5.10 on that and see how things go.
There seems to be some kind of include problem with this version of perl
on freebsd and mailscanner. I am not sure what exact condition triggers
the issue, but enough people have complained about this. As of now I am
unable to run
d I will try 5.10 on that and see how things go.
There seems to be some kind of include problem with this version of perl
on freebsd and mailscanner. I am not sure what exact condition triggers
the issue, but enough people have complained about this. As of now I am
unable to run mailscanner on any o
gt;>> On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote:
> >>>>
> >>>>
> >>>>> If the existing maintainer has disappeared, one option would be for
> >>>>> you to take over maintainership: Upgrade mailscanner yourself and
> >
mailscanner yourself and
submit the upgrade as a PR that also transfers maintainership to
youself. If there's no response after about 2 weeks, the port is
yours.
Actually, there is a 2-week timeout on updates, but a 3-month
timeout
on maint
>Mike Jakubik wrote:
>> On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote:
>>
>>> On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote:
>>>
>>>> If the existing maintainer has disappeared, one option would be for
>>>> you
Mike Jakubik wrote:
On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote:
On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote:
If the existing maintainer has disappeared, one option would be for
you to take over maintainership: Upgrade mailscanner yourself and
submit the upgrade
On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote:
> On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote:
>> If the existing maintainer has disappeared, one option would be for
>> you to take over maintainership: Upgrade mailscanner yourself and
>> submit the upgr
I created a MailScanner port based on MailScanner-4.75.11,1
Could someone please test it!!!
It runs on my 7.1 stable AMD64 and 8.0 AMD64 systems and it looks likei t all
works.
My systems run perl 5.10.0 , i can not test it with earlier version of perl
My programming skills are very poor so
I am trying to get sendmail and MailScanner running on a 7.2-PRERELEASE
system and can't figure out how to get sendmail (or any other program)
to listen on port 25. If I remove MailScanner from the setup and just
run sendmail alone it works as expected but adding MailScanner into the
mix an
On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote:
> If the existing maintainer has disappeared, one option would be for
> you to take over maintainership: Upgrade mailscanner yourself and
> submit the upgrade as a PR that also transfers maintainership to
> youself. I
On 2009-Mar-25 09:07:58 -0400, Jerry wrote:
>Is the Mailscanner port still being maintained? The last version in
>ports is 4.67.6_3 while version 4.74 has been available from the
>Mailscanner site since the beginning of January. I tried contacting the
>maintainer, "j.koopm...@sec
Is the Mailscanner port still being maintained? The last version in
ports is 4.67.6_3 while version 4.74 has been available from the
Mailscanner site since the beginning of January. I tried contacting the
maintainer, "j.koopm...@seceidos.de" without success.
--
Jerry
ges...@yahoo.com
Is somebody working on a new Mailscanner port, i remember reading somewhere
that there was a new port for mailscanner but i can not find it.
I also ask this because the current MailScanner port does not work with the
latest perl (5.8.9).
Regards,
Johan Hendriks
5.8.9 on some mailscanner machines,
> and now mailscanner is not working anymore.
>
> I did run the perl-after-upgrade script.
>
>
>
> I also did a clean install on a spare machine of Mailscanner with a recent
> ports tree which sucked in perl 5.8.9 so it is not in the upgrad
Hello all.
I have updated my perl from 5.8.8 to 5.8.9 on some mailscanner machines, and
now mailscanner is not working anymore.
I did run the perl-after-upgrade script.
I also did a clean install on a spare machine of Mailscanner with a recent
ports tree which sucked in perl 5.8.9 so it is
>On Mon, 2 Feb 2009 22:19:27 +0100
>Anders Troback wrote:
>>Hi,
>>
>>sorry to bother you but I have a question!
>>
>>Are there any plans of upgrading the MailScanner port?
>You should probably be directing that question to the port maintainer:
>
On Mon, 2 Feb 2009 22:19:27 +0100
Anders Troback wrote:
>Hi,
>
>sorry to bother you but I have a question!
>
>Are there any plans of upgrading the MailScanner port?
You should probably be directing that question to the port maintainer:
j.koopm...@seceidos.de
--
Jerry
g
Hi,
sorry to bother you but I have a question!
Are there any plans of upgrading the MailScanner port?
Thanks for you time and effort!
Cheers,
Anders Troback
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean
Hi there,
I'm just wondering if there is a port for a more recent version of MailScanner
forthcoming? 4.67 is quite old now.
Thanks,
Warren
signature.asc
Description: OpenPGP digital signature
>> I have updated my Mailscanner server to the new perl
>> I did a perl-after-upgrade and it shows no errors then did the same with –f
>> All looked fine but now my mail scanner is not working anymore.
>> I get the following error
>>
>> Jan 16 11:46:03 mailsca
Johan Hendriks wrote:
I have updated my Mailscanner server to the new perl
I did a perl-after-upgrade and it shows no errors then did the same with –f
All looked fine but now my mail scanner is not working anymore.
I get the following error
Jan 16 11:46:03 mailscanner MailScanner[37117
I have updated my Mailscanner server to the new perl
I did a perl-after-upgrade and it shows no errors then did the same with –f
All looked fine but now my mail scanner is not working anymore.
I get the following error
Jan 16 11:46:03 mailscanner MailScanner[37117]: MailScanner E
Thanks. I actually did a ports_glob to find it. I found an old article
about it showing it in sysutils, so I had originally assumed it was
yanked...
-Clint
On Jan 02, Johan Hendriks wrote:
> There is a port called portdowngrade if I recall correct.
> You can use this to downgrade ports.
___
># /usr/local/sbin/mailscanner -debug
>In Debugging mode, not forking...
>Trying to setlogsock(unix)
>SpamAssassin temp dir = /var/spool/MailScanner/incoming/SpamAssassin-Temp
>Fatal error 'Recurse on a private mutex.' at line 986 in file
>/usr/src/lib/libpthread/t
# /usr/local/sbin/mailscanner -debug
In Debugging mode, not forking...
Trying to setlogsock(unix)
SpamAssassin temp dir = /var/spool/MailScanner/incoming/SpamAssassin-Temp
Fatal error 'Recurse on a private mutex.' at line 986 in file
/usr/src/lib/libpthread/thread/thr_mutex.c (errno
Whats about security news from Secunia?
http://secunia.com/Advisories/33117/
MailScanner Multiple Insecure Temporary Files
Will Mailscanner be updatet?
Kind Regards
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Problem with Mailscanner setup on FreeBSD 6.2/6.3
After doing some updates on my ports collection (clamav, Sqlite,
P5-IO-Net, and some others), mailscanner stopped working..
# mailscanner -debug
Fatal error 'Recurse on a private mutex.' at line 986 in file
/usr/src/lib/libpthr
># mailscanner -debug
>Fatal error 'Recurse on a private mutex.' at line 986 in file
/usr/src/lib/libpthread/thread/thr_mutex.c (errno = 0)
Not the slightest clue... perl with pthread enabled? I remember some
problems with
me of the machines in my house to 7.0.
Thanks again to all!
Paul Pathiakis
-Original Message-
From: Johan Hendriks [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2008 10:16 AM
To: Paul Pathiakis
Cc: freebsd-ports@freebsd.org
Subject: RE: FreeBSD Port: MailScanner-4.67.6
>Hi,
&
PROTECTED]
Subject: FreeBSD Port: MailScanner-4.67.6
Hi,
It seems that the latest p5-Mail-Tools in the ports tree causes a problem with
MailScanner. This has, apparently, been documented in many Linux distros as
well. I'm not sure if it's a problem with MailScanner or with the p
>Hi,
>It seems that the latest p5-Mail-Tools in the ports tree causes a
>problem with MailScanner. This has, apparently, been documented in
many
>Linux distros as well. I'm not sure if it's a problem with MailScanner
>or with the perl module. However, I couldn't
Port: MailScanner-4.67.6
New version was committed today. Update your port tree please.
Mit freundlichen Grüßen
Jan-Peter Koopmann
Dipl.-Wirtschaftsinformatiker
Geschäftsführer
From: Paul Pathiakis [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2008 2:44 PM
To: Koopmann, Jan
Hi,
It seems that the latest p5-Mail-Tools in the ports tree causes a
problem with MailScanner. This has, apparently, been documented in many
Linux distros as well. I'm not sure if it's a problem with MailScanner
or with the perl module. However, I couldn't get it to run unti
: MailScanner-4.64.3
Von: "Kai Heitkamp"<[EMAIL PROTECTED]>
Datum: 08.03.2008 16:23
Hi,
why is the last update of port "/mail/mailscanner" so old? Many new versions
are released in the meantime. Current is 4.67.6!
Thx!
Chris
-
Hi,
why is the last update of port "/mail/mailscanner" so old? Many new versions
are released in the meantime. Current is 4.67.6!
Thx!
Chris
-
Lesen Sie Ihre E-Mails auf dem Handy..
___
fre
I updated my mailscanner machine and after restarting mailscanner i get
the following error
/usr/local/etc/rc.d/mailscanner start
Starting mailscanner.
Variable "$FIELD_NAME" is not imported at
/usr/local/lib/MailScanner/MailScanner/Message.pm line 6906.
Variable "$FIE
Error on freshly built box, as a MailScanner dependency.
I'm not much of a coder-- I have a number of these boxes running
perfectly. Not sure if something changed or not, but this happens on
mailscanner install.
Any advice would be appreciated.
*** Error code 1
Stop in
/usr/ports/ma
Koopmann, Jan-Peter wrote:
I hope next week. I was on vacation until last week and currently I am very
sick and in bed. :-(
Doh! Feel better soon :) and thanks for the port...
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/ma
I hope next week. I was on vacation until last week and currently I am very
sick and in bed. :-(
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Any idea when we can expect the next update?
Thanks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Koopmann, Jan-Peter wrote:
Problem is fixed and new version is committed... Thanks for the hint!
Thanks for the update, just in time for freebsd 6.2 too!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
Problem is fixed and new version is committed... Thanks for the hint!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 23 Nov 2006 20:56:40 +0100
"Koopmann, Jan-Peter" <[EMAIL PROTECTED]> wrote:
> On Donnerstag, 23. November 2006 4:57 Chuck Rock wrote:
>
> > # Upgrading MailScanner.conf file... Please wait
> >
> > *** Error code 126
>
> The tarball changed
On Donnerstag, 23. November 2006 4:57 Chuck Rock wrote:
> # Upgrading MailScanner.conf file... Please wait
>
> *** Error code 126
The tarball changed and the upgrade_MailScanner_conf was/is missing the
exec flag. I adjusted the Makefile. However I do not see a gnats-entry
for my submission and
point,
running the work/MailScanner-install-4.56.8/bin/upgrade_MailScanner_conf
cd /usr/ports/mail/mailscanner/files && install -o root -g wheel -m 444
MailScanner.8 /usr/local/man/man8
/usr/local/bin/perl -pi -e 's,%%LOCALBASE%%,/usr/local,g;
s,%%PREFIX%%,/usr/local,g;
Koopmann, Jan-Peter wrote:
> I am extremly busy at the moment. It might well take more than a week. Sorry.
>
>
>
>
> Mit freundlichen Grüßen
>
> Jan-Peter Koopmann
> Dipl.-Wirtschaftsinformatiker
> Geschäftsführer
>
> --
> Seceidos GmbH&Co. KG | Tel: +49 6151 66843-43
> Robert-Bosch-St
eeBSD Port: MailScanner-4.55.10
I need to upgrade MailScanner as this current version of the port has some
problems.
The latest stable according to their site is 4.56.8-1.
Can you please push out an update for the FreeBSD port to this?
Thank so much for your work with this.
I need to upgrade MailScanner as this current version of the port has some
problems.
The latest stable according to their site is 4.56.8-1.
Can you please push out an update for the FreeBSD port to this?
Thank so much for your work with this.
Chuck
Hi,
I have a thing in my /var/log/messages:
MailScanner-MRTG[50361]: Could not read thresholds
file /etc/MailScanner/mailscanner-mrtg.thresholds No such file or
directory
1. Shouldn't this file live in ${LOCALBASE}/etc/MailScanner?
2. Do I need it?
Thanks!!!
--
Anders Trobäck
On Saturday, July 08, 2006 11:23 PM Anders Troback wrote:
> after the upgrade to 0.11.00 I have some stuff in my /var/log/maillog:
>
> Jul 8 23:10:02 mail MailScanner-MRTG[21476]: Could not read
> thresholds file /etc/MailScanner/mailscanner-mrtg.thresholds No such
> file or dire
Hi,
after the upgrade to 0.11.00 I have some stuff in my /var/log/maillog:
Jul 8 23:10:02 mail MailScanner-MRTG[21476]: Could not read thresholds
file /etc/MailScanner/mailscanner-mrtg.thresholds No such file or
directory
Running on FreeBSD-5.4-RELEASE-p15!
Thanks!
\\troback
On Saturday, July 01, 2006 11:08 PM James L. Day wrote:
> partition running out of space during scans of large messages. I
> recommend that it be changed to "/var/tmp".
First of all thanks for your suggestion. I have to agree with the others though
and will leave it pointing to /tmp. If y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 01 Jul 2006 16:07:31 -0500
"James L. Day" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'd like to recommend a change to your "patch-lib-clamav-wrapper" file
> in your FreeBSD MailScanner port. You
James L. Day wrote:
Hello,
I'd like to recommend a change to your "patch-lib-clamav-wrapper" file
in your FreeBSD MailScanner port. You have the temporary directory path
set to "/tmp". I'm having trouble with my "/tmp" partition running out
of
rote:
> James L. Day wrote:
>> Hello,
>>
>> I'd like to recommend a change to your "patch-lib-clamav-wrapper" file
>> in your FreeBSD MailScanner port. You have the temporary directory path
>> set to "/tmp". I'm having trouble with
Hello,
I'd like to recommend a change to your "patch-lib-clamav-wrapper" file
in your FreeBSD MailScanner port. You have the temporary directory path
set to "/tmp". I'm having trouble with my "/tmp" partition running out
of space during scans of large m
84 matches
Mail list logo
