taint errors again -U not working anymore

[Glenn Steen]

On 26 October 2011 10:52, Rob Verduijn <rob.verduijn at gmail.com> wrote:
> duh not mailwatch but mailscanner ofcourse
> I am using baruwa as frontend not mailwatch, I migrated away from that one
> due to the lack of signs of life from that project.
>
> Rob

I'm sure that Andrew K wuold pipe up if Baruwa needs the same
permssion mods as Mailwatch did/does. If you can access the messages
from inside baruwa (I'm still trying to find enough time to actually
evaluate baruwa...:-), you're probably fine (look at the message
proper, release messages from quarantine etc... If Baruwa actually
suppirts that:-).

MailWatch may be rather dead as a project, but the code still hums
nicely on my boxes. Since the demise of Mandriva (yeah, a bit exotic,
I know) I'm in the very slow process of moving to CentOS 6 as a VA,
with MS based on the Baruwa/EPEL repos for pretty much the same
reasons though:-)... but initially, I plan on "dual logging", just to
evaluate things.

Cheers
-- 
-- Glenn

> 2011/10/26 Rob Verduijn <rob.verduijn at gmail.com>
>>
>> Mailwatch works fine now, mails get moved into quarantine and I'm still in
>> the process of checking the crontab scripts
>> (some of them are quite complex)
>>
>> No updates were done as far as I can tell (at that moment)
>>
>> Rob
>>
>> 2011/10/26 Glenn Steen <glenn.steen at gmail.com>
>>>
>>> Ah, but does your mailwatch (or similar) work now? Specifically the
>>> quarantine-related bits?
>>>
>>> Do you allow/do automatic updates? If so, what got updated? Or did you
>>> perform any recent updates, that only took effect at the given time?
>>>
>>> Cheers
>>> --
>>> -- Glenn
>>>
>>> Den 26 okt 2011 09:25 skrev "Rob Verduijn" <rob.verduijn at gmail.com>:
>>>>
>>>> Another email on this list with another problem gave me a clue, it seems
>>>> that mailscanner was unable since 23:53 to write in the quarantine folder.
>>>> How this all of a sudden changed is stil a mystery to me (checking
>>>> cronjobs now).
>>>>
>>>> But I changed the run as group of mailscanner to the apropriate one and
>>>> now it is working again. (from www-data to postfix)
>>>>
>>>> Regards
>>>> Rob
>>>>
>>>> 2011/10/25 --[ UxBoD ]-- <uxbod at splatnix.net>
>>>>>
>>>>> For reference I added the -U -X and so far have not seen another issue:
>>>>>
>>>>> Linux gateway.splatnix.net 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27
>>>>> 19:49:27 BST 2011 x86_64 x86_64 x86_64 GNU/Linux
>>>>> This is CentOS Linux release 6.0 (Final)
>>>>> This is Perl version 5.010001 (5.10.1)
>>>>> --
>>>>> Thanks, Phil
>>>>>
>>>>> ----- Original Message -----
>>>>> > Dave Jones wrote:
>>>>> > >> Hello all,
>>>>> > >>
>>>>> > >> I've got these bloody taint errors again since 23:56 last night.
>>>>> > >>
>>>>> > >> adding -U to the shebang of MailScanner does not help anymore.
>>>>> > >>
>>>>> > >> Anybody else who has these problems, and how knows a workaround.
>>>>> > >>
>>>>> > >> Rob
>>>>> > >
>>>>> > > I have to put "-U -X" to get MailScanner working with perl 5.10.
>>>>> > >
>>>>> > > # head -1 /usr/sbin/MailScanner
>>>>> > > #!/usr/bin/perl -U -X -I/usr/lib/MailScanner
>>>>> >
>>>>> > I ran "yum up" this morning and had a boat load of patches waiting to
>>>>> > install.  (I declined.)
>>>>> > Output from "MailScanner -V"
>>>>> > Linux smtp.ci.juneau.ak.us 2.6.18-238.19.1.el5 #1 SMP Fri Jul 15
>>>>> > 07:31:24 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
>>>>> > This is CentOS release 5.6 (Final)
>>>>> > This is Perl version 5.008008 (5.8.8)
>>>>> >
>>>>> > If I let it do the upgrades, am I going to run into this issue?  It
>>>>> > wasn't clear from the yum output if I'd end up on perl 5.10.
>>>>> >
>>>>> > TIA...
>>>>> >
>>>>> > ...Kevin
>>>>> > --
>>>>> > Kevin Miller                Registered Linux User No: 307357
>>>>> > CBJ MIS Dept.               Network Systems Admin., Mail Admin.
>>>>> > 155 South Seward Street     ph: (907) 586-0242
>>>>> > Juneau, Alaska 99801        fax: (907 586-4500--
>>>>> > MailScanner mailing list
>>>>> > mailscanner at lists.mailscanner.info
>>>>> > http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>>> >
>>>>> > Before posting, read http://wiki.mailscanner.info/posting
>>>>> >
>>>>> > Support MailScanner development - buy the book off the website!
>>>>> >
>>>>> --
>>>>> MailScanner mailing list
>>>>> mailscanner at lists.mailscanner.info
>>>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>>>
>>>>> Before posting, read http://wiki.mailscanner.info/posting
>>>>>
>>>>> Support MailScanner development - buy the book off the website!
>>>>
>>>>
>>>> --
>>>> MailScanner mailing list
>>>> mailscanner at lists.mailscanner.info
>>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>>
>>>> Before posting, read http://wiki.mailscanner.info/posting
>>>>
>>>> Support MailScanner development - buy the book off the website!
>>>>
>>>
>>> --
>>> MailScanner mailing list
>>> mailscanner at lists.mailscanner.info
>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>
>>> Before posting, read http://wiki.mailscanner.info/posting
>>>
>>> Support MailScanner development - buy the book off the website!
>>>
>>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>
>



-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se