On Tue, 3 Apr 2018 14:58:39 +0200
Michael Brunnbauer wrote:
> Hello Giovanni,
>
> On Tue, Apr 03, 2018 at 11:04:46AM +0200, Giovanni Bechis wrote:
> > if you start spamd from /root and you use a perl module that is
> > using "use lib 'lib';" or similar piece of code the relevant code
> > will not
Hello Giovanni,
On Tue, Apr 03, 2018 at 11:04:46AM +0200, Giovanni Bechis wrote:
> if you start spamd from /root and you use a perl module that is using "use
> lib 'lib';" or similar piece of code the relevant code will not load because
> the user spamd is running on (spamd or whichever you hav
On Mon, Apr 02, 2018 at 03:09:34AM +0200, Michael Brunnbauer wrote:
[...]
> So being in /root when started changes the behavior of spamd. Is it possible
> that this is a timing issue? Could "\# 4 7f03" be some unprocessed
> response that would be converted to 127.0.0.3 a moment later? Or is the
On 01.04.18 18:26, Michael Brunnbauer wrote:
I'd like to start to improve things by getting DNS blacklist in Spamassassin
to work again. I think it would improve things drastically. So let's look at
my problem again: running my example spam through spamassassin gets it
marked as spam while using
Hello Bill,
On Mon, Apr 02, 2018 at 02:33:08AM -0400, Bill Cole wrote:
> So I guess I was right?
I don't think so.
> Is there a tree of Perl modules under /root?
No. I actually just reproduced the problem with a completely empty /root:
cd /
mkdir root1
chmod go= root1
mv root root.old ; mv ro
On 1 Apr 2018, at 21:09 (-0400), Michael Brunnbauer wrote:
[...]
Figuring out what spamd is using is less simple (and system-specific)
but
since you've been maintaining a system by hand for a long time I
expect
you'll be able to figure out how to do so safely.
This does not sound very helpf
Hello Bill,
On Sun, Apr 01, 2018 at 03:55:48PM -0400, Bill Cole wrote:
> This is a critical fact. It indicates that your spamd and the spamassassin
> script you are running are definitely using different SpamAssassin
> configurations, possibly different versions of the SpamAssassin
> distribution
On 1 Apr 2018, at 12:26 (-0400), Michael Brunnbauer wrote:
So let's look at
my problem again: running my example spam through spamassassin gets it
marked as spam while using spamc+spamd does not.
This is a critical fact. It indicates that your spamd and the
spamassassin script you are running
Hello Amir,
On Sun, Apr 01, 2018 at 01:17:03PM -0600, Amir Caspi wrote:
> On Apr 1, 2018, at 10:26 AM, Michael Brunnbauer wrote:
> >
> > running my example spam through spamassassin gets it marked as spam while
> > using spamc+spamd does not.
>
> I know this is the equivalent of ???did you pl
On Apr 1, 2018, at 10:26 AM, Michael Brunnbauer wrote:
>
> running my example spam through spamassassin gets it marked as spam while
> using spamc+spamd does not.
I know this is the equivalent of “did you plug it in” but... did you restart
spamd after rebuilding Net::DNS?
Just making sure. So
hi
On Sun, Apr 01, 2018 at 12:55:33PM -0500, David Jones wrote:
> Can you provide an example message lightly redacted via pastebin.com?
I use this message for testing: https://pastebin.com/9h9d62UW
The relay IP 185.207.8.210 is in several blacklists but spamd won't notice.
spamassassin does.
>
On 04/01/2018 11:26 AM, Michael Brunnbauer wrote:
hi all,
Reindl Harald wrote:
but your distribution sucks too when you need to "So I downgraded to
Net-DNS-0.83 today and got spamassassin working but not spamd"
I don't use a distribution and build everything myself (since I bootstrapped
my s
hi all,
Reindl Harald wrote:
> but your distribution sucks too when you need to "So I downgraded to
> Net-DNS-0.83 today and got spamassassin working but not spamd"
I don't use a distribution and build everything myself (since I bootstrapped
my system in the 1990ies). I seldom have problems to g
On 04/01/2018 09:25 AM, Michael Brunnbauer wrote:
hi
I think I lost quite a few customers in the last months because DNS-lookups
are fucked up with Spamassassin so all DNSBL tests won't trigger while not
reporting errors. A problem with newer versions of Net::DNS that has been
known for months
Michael Brunnbauer skrev den 2018-04-01 16:25:
hi
I think I lost quite a few customers in the last months because
DNS-lookups
are fucked up with Spamassassin so all DNSBL tests won't trigger while
not
reporting errors. A problem with newer versions of Net::DNS that has
been
known for months w
15 matches
Mail list logo
