Re: Updating the "Mailscanner" port
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 success. 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 response after about 2 weeks, the port is yours. -- Peter Jeremy pgpfDxkGmF9EY.pgp Description: PGP signature
Re: Updating the "Mailscanner" port
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 response after about 2 weeks, the port is yours. Actually, there is a 2-week timeout on updates, but a 3-month timeout on maintainer inactivity for transferring maintainership. Vacations can last more than 2 weeks :-) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating the "Mailscanner" port
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 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 maintainer inactivity for transferring maintainership. Vacations > can last more than 2 weeks :-) I've just submitted a patch that updates this port to the latest version, perhaps we can squeeze it in before the freeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating the "Mailscanner" port
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 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 maintainer inactivity for transferring maintainership. Vacations can last more than 2 weeks :-) I've just submitted a patch that updates this port to the latest version, perhaps we can squeeze it in before the freeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" I noticed a couple of things here. The 4.78.9 version is still listed as Beta according to the MailScanner site, though the site may just not have updated yet. Second, the patch submitted forces perl 5.10+ as a requirement. I've seen nothing on the MailScanner site that says that this is a requirement, and have had no problems myself using any of the Beta versions with perl 5.8.9_3. Given that upgrading perl is not something to be done lightly, I was wondering what issues people were seeing that 5.10 fixed. Thanks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
RE: Updating the "Mailscanner" port
>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 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 maintainer inactivity for transferring maintainership. Vacations >>> can last more than 2 weeks :-) >>> >> >> I've just submitted a patch that updates this port to the latest version, >> perhaps we can squeeze it in before the freeze. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 >> >> Thanks. >> >> ___ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" >> >I noticed a couple of things here. The 4.78.9 version is still listed as >Beta according to the MailScanner site, though the site may just not >have updated yet. Second, the patch submitted forces perl 5.10+ as a >requirement. I've seen nothing on the MailScanner site that says that >this is a requirement, and have had no problems myself using any of the >Beta versions with perl 5.8.9_3. Given that upgrading perl is not >something to be done lightly, I was wondering what issues people were >seeing that 5.10 fixed. > >Thanks I am running quit a few Mailscanner servers, and they all failed under perl 5.8.9 This was on FreeBSD 6.x, 7.x and 8-Current that time, when i switched to 5.10.x or back to 5.8.8 my problems went away. if you google on FreeBSD perl 5.8.9 and mailscanner there are a lot of people reporting issues. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.55/2301 - Release Date: 08/13/09 18:16:00 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating the "Mailscanner" port
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 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 maintainer inactivity for transferring maintainership. Vacations can last more than 2 weeks :-) I've just submitted a patch that updates this port to the latest version, perhaps we can squeeze it in before the freeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" I noticed a couple of things here. The 4.78.9 version is still listed as Beta according to the MailScanner site, though the site may just not have updated yet. Second, the patch submitted forces perl 5.10+ as a requirement. I've seen nothing on the MailScanner site that says that this is a requirement, and have had no problems myself using any of the Beta versions with perl 5.8.9_3. Given that upgrading perl is not something to be done lightly, I was wondering what issues people were seeing that 5.10 fixed. Thanks I am running quit a few Mailscanner servers, and they all failed under perl 5.8.9 This was on FreeBSD 6.x, 7.x and 8-Current that time, when i switched to 5.10.x or back to 5.8.8 my problems went away. if you google on FreeBSD perl 5.8.9 and mailscanner there are a lot of people reporting issues. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.55/2301 - Release Date: 08/13/09 18:16:00 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" 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.10 on that and see how things go. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating the "Mailscanner" port
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: > > > > 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 response after about 2 weeks, the port is > > > > yours. > > > > > > > Actually, there is a 2-week timeout on updates, but a 3-month > > > timeout > > > on maintainer inactivity for transferring maintainership. Vacations > can last more than 2 weeks :-) > > > >>> I've just submitted a patch that updates this port to the latest > >>> > > version, > > > >>> perhaps we can squeeze it in before the freeze. > >>> > >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 > >>> > >>> Thanks. > >>> > >>> ___ > >>> freebsd-ports@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports > >>> To unsubscribe, send any mail to > >>> > > "freebsd-ports-unsubscr...@freebsd.org" > > > >>> > >>> > >> I noticed a couple of things here. The 4.78.9 version is still listed > >> > > as > > > >> Beta according to the MailScanner site, though the site may just not > >> have updated yet. Second, the patch submitted forces perl 5.10+ as a > >> requirement. I've seen nothing on the MailScanner site that says that > >> this is a requirement, and have had no problems myself using any of the > >> > > > > > >> Beta versions with perl 5.8.9_3. Given that upgrading perl is not > >> something to be done lightly, I was wondering what issues people were > >> seeing that 5.10 fixed. > >> > >> Thanks > >> > > > > I am running quit a few Mailscanner servers, and they all failed under > > perl 5.8.9 > > This was on FreeBSD 6.x, 7.x and 8-Current that time, when i switched to > > 5.10.x or back to 5.8.8 my problems went away. > > > > if you google on FreeBSD perl 5.8.9 and mailscanner there are a lot of > > people reporting issues. > > > > Regards, > > Johan Hendriks > > > > > > > > > > > > No virus found in this outgoing message. > > Checked by AVG - www.avg.com > > Version: 8.5.392 / Virus Database: 270.13.55/2301 - Release Date: > > 08/13/09 18:16:00 > > ___ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > > 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.10 on that and see how things go. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" This is most likely the common problem. ports/UPDATING states: 20090113: AFFECTS: users of lang/perl5.8 AUTHOR: s...@freebsd.org lang/perl5.8 has been updated to 5.8.9. You should update everything that depends on perl. The easiest way to do that is to use perl-after-upgrade script supplied with lang/perl5.8. Please see its manual page for details. Please check UPDATING after to follow up on any other updates for perl that you might have to perform. This explains why going back to 5.8.8 works for you. Best regards. -- Jason J. Hellenthal +1.616.403.8065 jas...@dataix.net I pledge Allegiance to the Flag of the United States of America, and to the Republic for which it stands; one Nation under God, Indivisible, with Liberty and Justice for all. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating the "Mailscanner" port
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.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 of my systems with perl 5.8.9, which version are you using? http://www.mail-archive.com/freebsd-ports@freebsd.org/msg18581.html Upgrading perl can indeed be a pain, as this problem shows, however i am not a perl programmer and i don't know how to address this issue. Perl 5.10 seems to work great. Since no one has addressed this and Jan does not seem to maintain this anymore, i took the initiative to update the port, as i needed a new version. This is the latest version, which is labeled as beta. It seems to be running just fine here, but it would be nice if more people could test it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating the "Mailscanner" port
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, 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 mailscanner on any of my systems with perl 5.8.9, which version are you using? http://www.mail-archive.com/freebsd-ports@freebsd.org/msg18581.html Upgrading perl can indeed be a pain, as this problem shows, however i am not a perl programmer and i don't know how to address this issue. Perl 5.10 seems to work great. Since no one has addressed this and Jan does not seem to maintain this anymore, i took the initiative to update the port, as i needed a new version. This is the latest version, which is labeled as beta. It seems to be running just fine here, but it would be nice if more people could test it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" In production, I am using the official 4.75 FreeBSD port, which I submitted the patches for so if it is messed up it is probably my fault ;) I've also used 4.77 without problem, and very briefly tested 4.78. If people are having trouble and the port could strongly recommend using 5.10 that might be better. Doing a quick scan of /usr/ports, I didn't find any ports that specifically required 5.10+. I am not a perl programmer either, but if you want to take this port and upgrade it, I would be happy to help or test. I'm not sure what the status is of the listed maintainer. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
RE: Updating the "Mailscanner" port
>> 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 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 maintainer inactivity for transferring maintainership. Vacations >> can last more than 2 weeks :-) >> >> >> >>> I've just submitted a patch that updates this port to the latest >> >>> >> > version, >> > >> >>> perhaps we can squeeze it in before the freeze. >> >>> >> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 >> >>> >> >>> Thanks. >> >>> >> >>> ___ >> >>> freebsd-ports@freebsd.org mailing list >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> >>> To unsubscribe, send any mail to >> >>> >> > "freebsd-ports-unsubscr...@freebsd.org" > > > >>> > >>> > >> I noticed a couple of things here. The 4.78.9 version is still listed >> >> >> > as >> > >> >> Beta according to the MailScanner site, though the site may just not >> >> have updated yet. Second, the patch submitted forces perl 5.10+ as a >> >> requirement. I've seen nothing on the MailScanner site that says that >> >> this is a requirement, and have had no problems myself using any of the >> >> >> > >> > >> >> Beta versions with perl 5.8.9_3. Given that upgrading perl is not >> >> something to be done lightly, I was wondering what issues people were >> >> seeing that 5.10 fixed. >> >> >> >> Thanks >> >> >> > >> > I am running quit a few Mailscanner servers, and they all failed under >> > perl 5.8.9 >> > This was on FreeBSD 6.x, 7.x and 8-Current that time, when i switched to >> > 5.10.x or back to 5.8.8 my problems went away. >> > >> > if you google on FreeBSD perl 5.8.9 and mailscanner there are a lot of >> > people reporting issues. >> > >> > Regards, >> > Johan Hendriks >> > >> 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.10 on that and see how things go. >> ___ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" >This is most likely the common problem. ports/UPDATING states: >20090113: > AFFECTS: users of lang/perl5.8 > AUTHOR: s...@freebsd.org > lang/perl5.8 has been updated to 5.8.9. You should update everything > that depends on perl. The easiest way to do that is to use > perl-after-upgrade script supplied with lang/perl5.8. Please see its > manual page for details. >Please check UPDATING after to follow up on any other updates for perl that >you might have to perform. >This explains why going back to 5.8.8 works for you. >Best regards. -- >Jason J. Hellenthal >+1.616.403.8065 j>as...@dataix.net 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 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.html I got an answer from someone who also had the same issue on a clean install. So let MailScanner depend on 5.10.x is not a so bad in my opinion. And if it is just a mailscanner server the update from 5.8.x to 5.10.x is not so bad to do. I did it on all my systems and not one did fail. approx 20 with FreeBSD 6.x, 7.x and 8-CURRENT at that time ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
RE: Updating the "Mailscanner" port
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 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.html > I got an answer from someone who also had the same issue on a clean > install. > > So let MailScanner depend on 5.10.x is not a so bad in my opinion. > And if it is just a mailscanner server the update from 5.8.x to 5.10.x is > not so bad to do. > I did it on all my systems and not one did fail. approx 20 with FreeBSD > 6.x, 7.x and 8-CURRENT at that time I have managed to install and run this port on a fresh install of FreeBSD and Perl 5.9. However i am still unable to use it on some of my production servers. Some condition seems to trigger this problem when upgrading Perl 5.8.8 to 5.8.9. I am not sure what it is at this time. Since it works for someone people i have taken out the explicit dependency on Perl 5.10 and have instead added an note on this problem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
