Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
On Fri, Sep 05, 2014 at 03:33:36PM +0200, Andreas Schulze wrote: > Am 05.09.2014 09:22 schrieb Joel Esler: > > I just tested the whole site with elinks and it worked fine. Which parts > > are you referring to? > > OK, my fault too. The site *is* usable without javascript. > Exeption I'm currently aware: > http://www.clamav.net/download.html#otherversions What's wrong with it? Elinks handles it fine. > > Anyway: good job! Thank you goes to our fantastic webteam that worked on the site. -- Joel Esler Open Source Manager Threat Intelligence Team Lead Talos ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
Am 05.09.2014 09:22 schrieb Joel Esler: > I just tested the whole site with elinks and it worked fine. Which parts are > you referring to? OK, my fault too. The site *is* usable without javascript. Exeption I'm currently aware: http://www.clamav.net/download.html#otherversions Anyway: good job! Andreas -- Andreas Schulze Internetdienste | P252 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail i...@datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dr. Robert Mayr (stellv. Vorsitzender) Eckhard Schwarzer (stellv. Vorsitzender) Dr. Peter Krug Jörg Rabe von Pappenheim Vorsitzender des Aufsichtsrates: Dirk Schmale ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
On Fri, Sep 05, 2014 at 09:09:59AM +0200, Matus UHLAR - fantomas wrote: > On 04.09.14 07:53, Andreas Schulze wrote: > >Am 26.08.2014 20:56, schrieb Joel Esler (jesler): > >> * Simple Navigation > >> > >"Thanks" for the next site only usable with mainstream browsers and > >JavaScript enabled :-/ > > ohh, which parts? I just tested the whole site with elinks and it worked fine. Which parts are you referring to? -- Joel Esler Open Source Manager Threat Intelligence Team Lead Talos ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
On 04.09.14 07:53, Andreas Schulze wrote: Am 26.08.2014 20:56, schrieb Joel Esler (jesler): * Simple Navigation "Thanks" for the next site only usable with mainstream browsers and JavaScript enabled :-/ ohh, which parts? -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Nothing is fool-proof to a talented fool. ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
On 4. sep. 2014 07.54.34 Andreas Schulze wrote: It's handy to point a user to the official Website to proof that he's running outdated viresscanner. Freshclam gives a warning of outdates here just fine, does not need external tools to tell me that, are admins so dump todays ? ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
On Thu, Sep 04, 2014 at 07:53:30AM +0200, Andreas Schulze wrote: > Am 26.08.2014 20:56, schrieb Joel Esler (jesler): > > * Elimination of dead links and pages > > > I was told the old website contained the current patternversion > somewhere. That function is also gone away. > It's handy to point a user to the official Website to proof that he's > running outdated viresscanner. We're looking at putting the dates for the downloads back on the site. -- Joel Esler Open Source Manager Threat Intelligence Team Lead Talos pgp06bPcPdDtt.pgp Description: PGP signature ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
Am 26.08.2014 20:56, schrieb Joel Esler (jesler): > * Simple Navigation > "Thanks" for the next site only usable with mainstream browsers and JavaScript enabled :-/ > * Elimination of dead links and pages > I was told the old website contained the current patternversion somewhere. That function is also gone away. It's handy to point a user to the official Website to proof that he's running outdated viresscanner. Andreas ___ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
Ed,
Thanks, we’ll have a look.
> On Sep 2, 2014, at 2:18 PM, Ed Christiansen MS wrote:
>
> You might want to fix the website.
>
> When I click on the red text "source code" on download page and then the big
> red "download source" button I still get the clamav-0.98.4-win32.msi which
> isn't very useful for an of my unix flavors.
>
> On 8/31/2014 6:35 AM, Alessandro Vesely wrote:
>> On Tue 26/Aug/2014 20:56:27 +0200 Joel Esler (jesler) wrote:
>>>
>>> http://blog.clamav.net/2014/08/the-new-clamavnet-is-here.html
>>
>> Thanks for that web site refurbishing. But let me note a couple of
>> points about the mailing list:
>>
>> *No DKIM signature*. In some cases there is an author DKIM signature,
>> which is broken by the mailing list massaging, as usual. Adding DKIM
>> signatures might help deliverability, but watch out for senders with
>> "strong" DMARC policies.
>>
>> *Broken SPF record*. The relevant records are
>>
>> lists.clamav.net. IN TXT "v=spf1 mx a -all"
>> IN A 198.148.79.53
>>
>> There is no MX record, which causes SPF verifications to fail; given
>> how the "mx" mechanism works, I'd suggest to just remove it from the
>> SPF record. The A suffices if the list sends out from that address
>> only. To tolerate relaying from different 198.148.79.53/32 addresses
>> as well as some 3rd party forwarders, you may want to consider
>> something like:
>>
>> lists.clamav.net. IN TXT "v=spf1 a ~exists:%{ir}.list.dnswl.org -all"
>>
>> Last and least, I understand your stance toward top-posting, Joel, but
>> would appreciate if you can manage to configure your own mailer to
>> apply Internet style quoting ('> ') so as to improve your replies'
>> readability.
>>
>> Thank you for your commitment and dedication
>> Ale
>> ___
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>> http://www.clamav.net/support/ml
>>
> ___
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> http://www.clamav.net/support/ml
___
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
You might want to fix the website.
When I click on the red text "source code" on download page and then the
big red "download source" button I still get the
clamav-0.98.4-win32.msi which isn't very useful for an of my unix flavors.
On 8/31/2014 6:35 AM, Alessandro Vesely wrote:
On Tue 26/Aug/2014 20:56:27 +0200 Joel Esler (jesler) wrote:
http://blog.clamav.net/2014/08/the-new-clamavnet-is-here.html
Thanks for that web site refurbishing. But let me note a couple of
points about the mailing list:
*No DKIM signature*. In some cases there is an author DKIM signature,
which is broken by the mailing list massaging, as usual. Adding DKIM
signatures might help deliverability, but watch out for senders with
"strong" DMARC policies.
*Broken SPF record*. The relevant records are
lists.clamav.net. IN TXT "v=spf1 mx a -all"
IN A 198.148.79.53
There is no MX record, which causes SPF verifications to fail; given
how the "mx" mechanism works, I'd suggest to just remove it from the
SPF record. The A suffices if the list sends out from that address
only. To tolerate relaying from different 198.148.79.53/32 addresses
as well as some 3rd party forwarders, you may want to consider
something like:
lists.clamav.net. IN TXT "v=spf1 a ~exists:%{ir}.list.dnswl.org -all"
Last and least, I understand your stance toward top-posting, Joel, but
would appreciate if you can manage to configure your own mailer to
apply Internet style quoting ('> ') so as to improve your replies'
readability.
Thank you for your commitment and dedication
Ale
___
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/support/ml
___
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/support/ml
Re: [clamav-users] ClamAV®: The new ClamAV.net is here!
On Tue 26/Aug/2014 20:56:27 +0200 Joel Esler (jesler) wrote:
>
> http://blog.clamav.net/2014/08/the-new-clamavnet-is-here.html
Thanks for that web site refurbishing. But let me note a couple of
points about the mailing list:
*No DKIM signature*. In some cases there is an author DKIM signature,
which is broken by the mailing list massaging, as usual. Adding DKIM
signatures might help deliverability, but watch out for senders with
"strong" DMARC policies.
*Broken SPF record*. The relevant records are
lists.clamav.net. IN TXT "v=spf1 mx a -all"
IN A 198.148.79.53
There is no MX record, which causes SPF verifications to fail; given
how the "mx" mechanism works, I'd suggest to just remove it from the
SPF record. The A suffices if the list sends out from that address
only. To tolerate relaying from different 198.148.79.53/32 addresses
as well as some 3rd party forwarders, you may want to consider
something like:
lists.clamav.net. IN TXT "v=spf1 a ~exists:%{ir}.list.dnswl.org -all"
Last and least, I understand your stance toward top-posting, Joel, but
would appreciate if you can manage to configure your own mailer to
apply Internet style quoting ('> ') so as to improve your replies'
readability.
Thank you for your commitment and dedication
Ale
___
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/support/ml
