Re: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread David Jones
On 01/10/2018 12:40 PM, Alex wrote: Hi, On Wed, Jan 10, 2018 at 12:21 PM, Kevin A. McGrail wrote: On 1/10/2018 11:23 AM, David Jones wrote: I need to see the debug verbose output of one that fails to troubleshoot further. Agreed. We need someone to run with -D and log it and IDEALLY run

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread Alex
Hi, On Wed, Jan 10, 2018 at 12:21 PM, Kevin A. McGrail wrote: > On 1/10/2018 11:23 AM, David Jones wrote: >> >> I need to see the debug verbose output of one that fails to troubleshoot >> further. > > > Agreed. We need someone to run with -D and log it and IDEALLY run a few > right after to see

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread Kevin A. McGrail
On 1/10/2018 11:23 AM, David Jones wrote: I need to see the debug verbose output of one that fails to troubleshoot further. Agreed.  We need someone to run with -D and log it and IDEALLY run a few right after to see if it resolves.  I'm guessing one mirror is blocking or something. Regard

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread Martin Gregorie
On Wed, 2018-01-10 at 15:23 +, RW wrote: > On Wed, 10 Jan 2018 15:10:52 + > Martin Gregorie wrote: > > > > The update defaults to being run from /etc/cron.weekly/sa-update, > > which runs /usr/bin/sa-update without any other parameters and does > > nothing else except for decoding the exi

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread Alex
Hi, > Update: If the downloads are successful but the GPG verification is > failing, then this would not be a routing issue. > > The rsync'ing by the mirrors should happen quickly and the .sha1 and .asc > files should sync quickly since they are very small files. If the downloads > are successfu

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread David Jones
On 01/10/2018 10:08 AM, David Jones wrote: On 01/10/2018 09:23 AM, RW wrote: On Wed, 10 Jan 2018 15:10:52 + Martin Gregorie wrote: The update defaults to being run from /etc/cron.weekly/sa-update, which runs /usr/bin/sa-update without any other parameters and does nothing else except for

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread David Jones
On 01/10/2018 09:23 AM, RW wrote: On Wed, 10 Jan 2018 15:10:52 + Martin Gregorie wrote: The update defaults to being run from /etc/cron.weekly/sa-update, which runs /usr/bin/sa-update without any other parameters and does nothing else except for decoding the exit code and mailing all outpu

Re: Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread Alex Woick
Kevin A. McGrail schrieb am 10.01.2018 um 15:09: > > Anyone having issues with Sha1 failures on their machines on sa-updates? > > Anyone familiar with sa-update.cron so we can try and get more data on this bug below? I'm using sa-update.cron from CentoOS 7. Here it failed once on 09-Jan-2018 0

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread RW
On Wed, 10 Jan 2018 15:10:52 + Martin Gregorie wrote: > The update defaults to being run from /etc/cron.weekly/sa-update, > which runs /usr/bin/sa-update without any other parameters and does > nothing else except for decoding the exit code and mailing all output > to root: I think its the st

Re: Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread Larry Rosenman
On Wed, Jan 10, 2018 at 03:10:52PM +, Martin Gregorie wrote: > On Wed, 2018-01-10 at 09:09 -0500, Kevin A. McGrail wrote: > > Anyone having issues with Sha1 failures on their machines on sa- > > updates? > > > No problems are being reported. The log just shows a single 'Update > completed' lin

Re: Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread Martin Gregorie
On Wed, 2018-01-10 at 09:09 -0500, Kevin A. McGrail wrote: > Anyone having issues with Sha1 failures on their machines on sa- > updates? > No problems are being reported. The log just shows a single 'Update completed' line for each weekly update. > Anyone familiar with sa-update.cron so we can tr

Re: Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread David Jones
On 01/10/2018 08:09 AM, Kevin A. McGrail wrote: Anyone having issues with Sha1 failures on their machines on sa-updates? Anyone familiar with sa-update.cron so we can try and get more data on this bug below? Generically, cron is going to email the output of the command so adjust the sa-upd

Re: srs with spamassassin SPF check

2018-01-10 Thread Benny Pedersen
David Jones skrev den 2018-01-10 15:37: actually being forwarded externally back out to the Internet. Filtered being delivered internally does not need SRS. fail in spf can be solved to not need srs at all, he imho use srs custom plugin in amavisd, so not spamassassin error, so to solve that

Re: srs with spamassassin SPF check

2018-01-10 Thread David Jones
On 01/10/2018 07:57 AM, Kacper Guzik wrote: here is complete log: https://pastebin.com/szVnTXXA Yep. You need to setup your mail flow where the SRS is done on clean mail after SA has scored it. Disable SRS in your Postfix config, setup a second instance of Postfix with SRS enabled for

Re: srs with spamassassin SPF check

2018-01-10 Thread Benny Pedersen
Kacper Guzik skrev den 2018-01-10 14:57: https://pastebin.com/szVnTXXA not spamassassin, so not usefull to get help test with same msg with "spamassassin -t msg" and show output on pastebin https://dmarcian.com/spf-survey/ type mail3.zenbox.pl into into Survey Domain: it shows some real

Re: srs with spamassassin SPF check

2018-01-10 Thread Kacper Guzik
here is complete log: https://pastebin.com/szVnTXXA srs rewrite e-mail fisher006 at gmail.com to SRS format Jan 10 09:29:43 mail3 amavis[14933]: (14933-03-2) SA dbg: FreeMail: all from-addresses: fisher...@gmail.com, srs0=2eq9=ef=gmail.com=fisher0 0...@mail3.zenbox.pl and spamassassin check'

Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

2018-01-10 Thread Kevin A. McGrail
Anyone having issues with Sha1 failures on their machines on sa-updates? Anyone familiar with sa-update.cron so we can try and get more data on this bug below? Forwarded Message Subject:[Bug 7331] channel: SHA1 verification failed, channel failed Date: Tue, 09 Jan

Re: srs with spamassassin SPF check

2018-01-10 Thread Benny Pedersen
Kacper Guzik skrev den 2018-01-10 14:40: I change real domain name to fake ;) why do you ask maillists then ? This case is related to David Jones. All emails is rewrited and spamassassin can't check spf record. I wondering maybe some feature exist to resolve this problem. you already know y

Re: srs with spamassassin SPF check

2018-01-10 Thread Matus UHLAR - fantomas
On 10.01.18 11:45, Kacper Guzik wrote: Hello, when I'm using postsrsd with spamassassin SPF checks all e-mail have SPF_FAIL=0.001 I'm trying with use_newest_received_spf_header 1 but this same issue spamassassin have problem with reconize SPF for mail's with SRS headers Jan 10 09:15:24 mail3 a

Re: srs with spamassassin SPF check

2018-01-10 Thread Benny Pedersen
Kacper Guzik skrev den 2018-01-10 11:45: Jan 10 09:15:24 mail3 amavis[5068]: (05068-01-3) SA dbg: spf: checking EnvelopeFrom (helo=mx45-71.futurehost.pl [1], ip=91.244.71.45, envfrom=srs0=pqle=ef=networkmasters.pl [2]=piotr.rosciszew...@mail3.pl) mail3.pl have no spf sorry cant help srs faili

Re: srs with spamassassin SPF check

2018-01-10 Thread David Jones
On 01/10/2018 04:45 AM, Kacper Guzik wrote: Hello, when I'm using postsrsd with spamassassin SPF checks all e-mail have SPF_FAIL=0.001 I'm trying with use_newest_received_spf_header 1 but this same issue spamassassin have problem with reconize SPF for mail's with SRS headers Jan 10 09:15:24 m

postsrs and SPF check problem

2018-01-10 Thread Kacper Guzik
hello i have problem like this: https://pastebin.com/L6F9HLvT sory for paste but outlook drop my emails for spam :)

[no subject]

2018-01-10 Thread Kacper Guzik
Hello, when I'm using postsrsd with spamassassin SPF checks all e-mail have SPF_FAIL=0.001 I'm trying with use_newest_received_spf_header 1 but this same issue spamassassin have problem with reconize SPF for mail's with SRS headers Jan 10 09:15:24 mail3 amavis[5068]: (05068-01-3) SA dbg: spf: ch

test

2018-01-10 Thread Kacper Guzik
test

SPF

2018-01-10 Thread Kacper Guzik
Hello, when I'm using postsrsd with spamassassin SPF checks all e-mail have SPF_FAIL=0.001 I'm trying with use_newest_received_spf_header 1 but this same issue spamassassin have problem with reconize SPF for mail's with SRS headers Jan 10 09:15:24 mail3 amavis[5068]: (05068-01-3) SA dbg: spf: ch

srs with spamassassin SPF check

2018-01-10 Thread Kacper Guzik
Hello, when I'm using postsrsd with spamassassin SPF checks all e-mail have SPF_FAIL=0.001 I'm trying with use_newest_received_spf_header 1 but this same issue spamassassin have problem with reconize SPF for mail's with SRS headers Jan 10 09:15:24 mail3 amavis[5068]: (05068-01-3) SA dbg: spf: ch