RE: Updating the "Mailscanner" port

2009-08-17 Thread Mike Jakubik
On Fri, August 14, 2009 2:53 pm, Johan Hendriks wrote: > Well i can assure you that that was not the case. > I did test it by going to 5.10, which worked, do all the things in > /usr/ports/UPDATING. > Then going back to 5.8.9, it did not work. > Going back to 5.8.8 it did work. > > I also did fre

RE: Updating the "Mailscanner" port

2009-08-14 Thread Johan Hendriks
>> Johan Hendriks wrote: >> >> 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

Re: Updating the "Mailscanner" port

2009-08-14 Thread Kevin Kobb
Mike Jakubik wrote: On Fri, August 14, 2009 11:18 am, Kevin Kobb wrote: I do remember seeing these problems reported, but for the life of me, I can not reproduce them. I use 5.8.9 in production, and get 20 to 40 thousand messages a day scanned without a problem. I am setting up a new server,

Re: Updating the "Mailscanner" port

2009-08-14 Thread Mike Jakubik
On Fri, August 14, 2009 11:18 am, Kevin Kobb wrote: > I do remember seeing these problems reported, but for the life of me, I > can not reproduce them. I use 5.8.9 in production, and get 20 to 40 > thousand messages a day scanned without a problem. I am setting up a new > server, and I will try 5.

Re: Updating the "Mailscanner" port

2009-08-14 Thread Jason J. Hellenthal
On Fri, 14 Aug 2009 11:18:13 -0400 Kevin Kobb wrote: > Johan Hendriks wrote: > >> 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: > > > >

Re: Updating the "Mailscanner" port

2009-08-14 Thread Kevin Kobb
Johan Hendriks wrote: 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

RE: Updating the "Mailscanner" port

2009-08-14 Thread Johan Hendriks
>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 a

Re: Updating the "Mailscanner" port

2009-08-14 Thread Kevin Kobb
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

Re: Updating the "Mailscanner" port

2009-08-13 Thread Mike Jakubik
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 as a PR that also tra

Re: Updating the "Mailscanner" port

2009-03-30 Thread Mark Linimon
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. If there's no respon

Re: Updating the "Mailscanner" port

2009-03-26 Thread Peter Jeremy
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...@seceidos.de" without

Updating the "Mailscanner" port

2009-03-25 Thread Jerry
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 guru, n: A