Language:
switch to room list switch to menu My folders
Go to page: 1 2 3 4 [5] 6 7 8 9 ... Last
[#] Sun Mar 31 2019 15:14:57 EDT from st.briest @ Uncensored

Subject: also a segfault in citadel

[Reply] [ReplyQuoted] [Headers] [Print]

Hi,

I have also a segfault probelm on devuan-testing (debian w/o systemd), kernel 4.19.28-2, 4.19.0-4-amd64. I have tested with the original packages, I have recompiled a actual snapshot and also tested with recompiled berkeley db lib and on different computers. It's always the same.

Output in syslog:

2019-03-31T20:18:52.493767+02:00 devuan kernel: [1244305.133712] citserver[16668]: segfault at 10000014c ip 00007fe4b8bac198 sp 00007ffe6a6ca2f0 error 4 in libdb-5.3.so[7fe4b8ada000+142000]
2019-03-31T20:34:19.085748+02:00 devuan kernel: [1245231.741368] Code: a5 4d 85 e4 74 bc 4c 39 f0 74 a0 31 c0 48 8d 35 96 31 08 00 48 89 ef e8 46 e6 f2 ff b8 16 00 00 00 eb a1 0f 1f 80 00 00 00 00 <41> 8b 94 24 4c 01 00 00 e9 d4 fe ff ff 0f 1f 00 f6 83 ac 05 00 00


Cmd-line error:

citserver[16668]: 
citserver[16668]: 
citserver[16668]: *** Citadel server engine ***
citserver[16668]: Version 925 (build (unknown)) ***
citserver[16668]: Copyright (C) 1987-2019 by the Citadel development team.
citserver[16668]: 
citserver[16668]: This program is open source software: you can redistribute it and/or
citserver[16668]: modify it under the terms of the GNU General Public License, version 3.
citserver[16668]: 
citserver[16668]: This program is distributed in the hope that it will be useful,
citserver[16668]: but WITHOUT ANY WARRANTY; without even the implied warranty of
citserver[16668]: MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
citserver[16668]: GNU General Public License for more details.
citserver[16668]: 
citserver[16668]: libcitadel(unnumbered)
citserver[16668]: main: creating lockfile
citserver[16668]: extensions: registered server command STLS (Start SSL/TLS session)
citserver[16668]: extensions: registered server command GTLS (Get SSL/TLS session status)
citserver[16668]: extensions: registered a new session function (type 0 Priority 30010)
citserver[16668]: master_startup() started
citserver[16668]: Checking directory access
citserver[16668]: Opening databases
citserver[16668]: db: open_databases() starting
citserver[16668]: db: Compiled libdb: Berkeley DB 5.3.28: (September  9, 2013)
citserver[16668]: db:   Linked libdb: Berkeley DB 5.3.28: (September  9, 2013)
citserver[16668]: db:    Linked zlib: 1.2.11
citserver[16668]: db: Setting up DB environment
citserver[16668]: db: dbenv->open(dbenv, /var/lib/citadel/data/, 75553, 0)
citserver[16668]: db: BDB2526 Finding last valid log LSN: file: 2 offset 2526541
citserver[16668]: db: mounting databases
citserver[16668]: Initializing configuration system
Speicherzugriffsfehler

 

It's possibile that the probelm is since the kernels build with LKMM feature.
The problem comes from CtdlGetDataStr called cdb_fetch in database.c, and there ret = dbp[cdb]->get(dbp[cdb], TSD->tid, &dkey, &dret, 0);

best regards, stb

 



[#] Mon Apr 01 2019 16:52:44 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: also a segfault in citadel

[Reply] [ReplyQuoted] [Headers] [Print]

citserver[16668]: Initializing configuration system
Speicherzugriffsfehler

 

It's possibile that the probelm is since the kernels build with LKMM
feature.

I don't know what a Speicherzugriffsfehler is, or why it would choose to collapse on Betelgeuse Seven, but if you did something to corrupt your database you might try running the database_cleanup.sh script to dump and load it.
Take a backup first.

[#] Wed Apr 03 2019 19:37:56 EDT from frank.occidentale @ Uncensored

Subject: Installing a current Citadel over an old one.

[Reply] [ReplyQuoted] [Headers] [Print]

Hi to All!

So I inherited this UBUNTU Server with Citadel Loaded and I must fix Citadel as it was hacked and will not send email.

I am VERY RUSTY at Unix/Linux so I'm taking a stab at it with the help of this forum and all you smart folks.

I opened a shell via PuTTY and, after becoming ROOT, entered the command suggested on the Install page.

It compiled for at least 5 minutes then I received:

 

checking libical/ical.h usability... no

checking libical/ical.h presence... no

checking for libical/ical.h... no

configure: error: libical/ical.h was not found and is required.  More info: http

://www.citadel.org/doku.php/installation:start

 Citadel Easy Install is aborting.

 The last few lines above this message may indicate what went wrong.

 Linux Debian jessie/sid( 3.13.0-32-generic x86_64)

 

So, at this point, I need help as I don't know how to find/do this.

Any volunteers?

-Frank

 


[#] Thu Apr 04 2019 13:50:37 EDT from Haven @ Uncensored

Subject: Re: Installing a current Citadel over an old one.

[Reply] [ReplyQuoted] [Headers] [Print]

 

Wed Apr 03 2019 19:37:56 EDT from frank.occidentale @ Uncensored Subject: Installing a current Citadel over an old one.

Hi to All!

So I inherited this UBUNTU Server with Citadel Loaded and I must fix Citadel as it was hacked and will not send email.

I am VERY RUSTY at Unix/Linux so I'm taking a stab at it with the help of this forum and all you smart folks.

I opened a shell via PuTTY and, after becoming ROOT, entered the command suggested on the Install page.

It compiled for at least 5 minutes then I received:

 

checking libical/ical.h usability... no

checking libical/ical.h presence... no

checking for libical/ical.h... no

configure: error: libical/ical.h was not found and is required.  More info: http

://www.citadel.org/doku.php/installation:start

 Citadel Easy Install is aborting.

 The last few lines above this message may indicate what went wrong.

 Linux Debian jessie/sid( 3.13.0-32-generic x86_64)

 

So, at this point, I need help as I don't know how to find/do this.

Any volunteers?

-Frank

 


 

Since ical wasn't found, I would start with installing the package libical-dev (apt-get install libical-dev) and go from there.   

Or from / try the command "find . -name ical.h -print" to see if the file ical.h is on the system.  If it is, then check your path to make sure it is in the path.  

 



[#] Thu Apr 04 2019 21:31:58 EDT from frank.occidentale @ Uncensored

Subject: Trying to load Citadel

[Reply] [ReplyQuoted] [Headers] [Print]

OK That worked and moved me along until I got this error:

checking ldap.h usability... no

checking ldap.h presence... no

checking for ldap.h... no

configure: error: OpenLDAP development headers were not found and are required.  More info: http://www.citadel.org/doku.php/installation:start

 Citadel Easy Install is aborting.

 The last few lines above this message may indicate what went wrong.

 Linux Debian jessie/sid( 3.13.0-32-generic x86_64)

 

Looks like the LDAP Development Headers are missing.... Now what?

 

Thanks!

-Frank

 


[#] Fri Apr 05 2019 14:46:35 EDT from st.briest @ Uncensored

Subject: Re: also a segfault in citadel

[Reply] [ReplyQuoted] [Headers] [Print]

Hi,

Speicherzugriffsfehler is the german translation for segmentation fault.

If I delete the database, then the new database was created and then comes the segmentaion fault.

A stratce is in the attachement

 

regards, stb



citserver.strace.txt (text/plain, 175550 bytes) [View| Download]
[#] Fri Apr 05 2019 16:24:48 EDT from Haven @ Uncensored

Subject: Re: Trying to load Citadel

[Reply] [ReplyQuoted] [Headers] [Print]

 

Thu Apr 04 2019 21:31:58 EDT from frank.occidentale @ Uncensored Subject: Trying to load Citadel

OK That worked and moved me along until I got this error:

checking ldap.h usability... no

checking ldap.h presence... no

checking for ldap.h... no

configure: error: OpenLDAP development headers were not found and are required.  More info: http://www.citadel.org/doku.php/installation:start

 Citadel Easy Install is aborting.

 The last few lines above this message may indicate what went wrong.

 Linux Debian jessie/sid( 3.13.0-32-generic x86_64)

 

Looks like the LDAP Development Headers are missing.... Now what?

 

Thanks!

-Frank

 


 

You know what I wrote last time. Same thing this time, but now you need the LDAP package instead.  You might have aptitude on the box, if so you can use that to search the packages.  

 

Also this page might offer some help as well:  https://www.cyberciti.biz/faq/equivalent-of-rpm-qf-command/

 



[#] Sat Apr 06 2019 12:26:34 EDT from frank.occidentale @ Uncensored

Subject: INSTALLED!!

[Reply] [ReplyQuoted] [Headers] [Print]

GREAT it now installed successfully.. Thank You so Much!!!

Now, when I enter the info into my browser as usual I get:


This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
Read More...

 

Seems like this is the last hurdle...

Ideas?

-Frank



[#] Sat Apr 06 2019 13:00:25 EDT from jdw @ Uncensored

Subject: Cal/CarDav on iOS?

[Reply] [ReplyQuoted] [Headers] [Print]

Anyone got this working? I can't seem to set it up. The logs on my system look fine - I can see the request come in when I add a CalDav account to my iPhone and it loads what looks like the right page:

HTTP: 200 [0.001890] GET /calendar/dav/jdw/user//landing?go=calendar?failvisibly=1

But I get the error "Cannot use SSL" and when I try without SSL, I get an authorization error.

Admittedly, I am not really up to speed on where Citadel or iOS is with respect to Cal/Card/GroupDav so maybe this just won't work at the moment but I can't get it working in Evolution either so I think something is borked on my end. This is a new install, it has never worked.

Thanks,

- jon





[#] Sat Apr 06 2019 13:07:07 EDT from jdw @ Uncensored

Subject: Re: Cal/CarDav on iOS?

[Reply] [ReplyQuoted] [Headers] [Print]

In a moment of clarity, I tested against uncensored and got the same result. So I guess it is just not something I can do from an iPhone now?

- jon

 

Sat Apr 06 2019 13:00:25 EDT from jdw @ Uncensored Subject: Cal/CarDav on iOS?

Anyone got this working? I can't seem to set it up. The logs on my system look fine - I can see the request come in when I add a CalDav account to my iPhone and it loads what looks like the right page:

HTTP: 200 [0.001890] GET /calendar/dav/jdw/user//landing?go=calendar?failvisibly=1

But I get the error "Cannot use SSL" and when I try without SSL, I get an authorization error.

Admittedly, I am not really up to speed on where Citadel or iOS is with respect to Cal/Card/GroupDav so maybe this just won't work at the moment but I can't get it working in Evolution either so I think something is borked on my end. This is a new install, it has never worked.

Thanks,

- jon





 



[#] Sun Apr 07 2019 05:56:11 EDT from Wurm0815 @ Uncensored

Subject: SMTP Error 421

[Reply] [ReplyQuoted] [Headers] [Print]

Hallo my Englisch is not so good but i Have by 2 Citadel Server the Error 421 (Domain service not available, closing transmission

 

channel) when i send a e-mail to any User what can i do to fix this Error



[#] Sun Apr 07 2019 05:59:15 EDT from Wurm0815 @ Uncensored

Subject: Re: SMTP Error 421

[Reply] [ReplyQuoted] [Headers] [Print]

 

I have the same error with 2 Citadel Server all mails come in but when raussenden comes the error 421 (Domain service not available, closing transmission channel) no matter to which address
Sun Apr 07 2019 05:56:11 EDT from Wurm0815 @ Uncensored Subject: SMTP Error 421

Hallo my Englisch is not so good but i Have by 2 Citadel Server the Error 421 (Domain service not available, closing transmission

 

channel) when i send a e-mail to any User what can i do to fix this Error



 



[#] Mon Apr 08 2019 13:06:50 EDT from jdw @ Uncensored

Subject: Spamassass won't rewrite subject

[Reply] [ReplyQuoted] [Headers] [Print]

Does anyone know why SA can't/wron't rewrite the subject? I'm using this, but it has no effect:

rewrite_header subject Subject *****SPAM(_LEVEL_)****"

Thanks,

 



[#] Tue Apr 09 2019 12:26:35 EDT from "s3cr3to" <s3cr3to@uncensored.citadel.org> to Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: Spamassass won't rewrite subject

[Reply] [ReplyQuoted] [Headers] [Print]

You have twice the word "subject", it's right?

Don't know if this works for you, mine has this:

# Add *****SPAM***** to the Subject header of spam e-mails
rewrite_header Subject *****SPAM _SCORE_*****

I don't remember seeing a detected spam with the subject rewrited.
Because we reject the mail with more other rules.

BTW, After many weeks searching, I find a correct rule filter but that
works for some kind of spam we get:

....
header LOCAL_RULE_SUBJ_190104 Subject =~ /\bTHE_STRING_OF_SPAM\b/i
score LOCAL_RULE_SUBJ_190104 8
....
# Set the threshold at which a message is considered spam (default: 5.0)
required_score 8

After writing rules, reload spamd:
# /etc/init.d/spamassassin reload
Check the spamd log to be sure that not error disable spamassassin:
# less /var/log/spamd.log

Regards


On 4/8/19 11:06 AM, jdw wrote:
Does anyone know why SA can't/wron't rewrite the subject? I'm using
this, but it has no effect:

rewrite_header subject Subject *****SPAM(_LEVEL_)****"

Thanks,

[#] Tue Apr 09 2019 14:04:03 EDT from jdw @ Uncensored

Subject: Re: Spamassass won't rewrite subject

[Reply] [ReplyQuoted] [Headers] [Print]

Good catch about the subject, thanks. But still no go.

There's no errors anywhere. And other changes to the local.cf file work, For example, I lowered the spam score and that takes effect, just not the subject rewrite. It's a weird problem.

 

Tue Apr 09 2019 12:26:35 EDT from "s3cr3to" <s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't rewrite subject
You have twice the word "subject", it's right?

Don't know if this works for you, mine has this:

# Add *****SPAM***** to the Subject header of spam e-mails
rewrite_header Subject *****SPAM _SCORE_*****

I don't remember seeing a detected spam with the subject rewrited.
Because we reject the mail with more other rules.

BTW, After many weeks searching, I find a correct rule filter but that
works for some kind of spam we get:

....
header LOCAL_RULE_SUBJ_190104 Subject =~ /\bTHE_STRING_OF_SPAM\b/i
score LOCAL_RULE_SUBJ_190104 8
....
# Set the threshold at which a message is considered spam (default: 5.0)
required_score 8

After writing rules, reload spamd:
# /etc/init.d/spamassassin reload
Check the spamd log to be sure that not error disable spamassassin:
# less /var/log/spamd.log

Regards


On 4/8/19 11:06 AM, jdw wrote:
Does anyone know why SA can't/wron't rewrite the subject? I'm using
this, but it has no effect:

rewrite_header subject Subject *****SPAM(_LEVEL_)****"

Thanks,

 



[#] Tue Apr 09 2019 14:56:20 EDT from "s3cr3to" <s3cr3to@uncensored.citadel.org> to undisclosed-recipients: ;

Subject: Re: Spamassass won't rewrite subject

[Reply] [ReplyQuoted] [Headers] [Print]

I found this same question in SO
https://stackoverflow.com/questions/26065798/spamassassin-not-rewriting-subject-line

The answer was (quoted):
"I figured it out. The rewrite_header won't happen unless the email's
score is more than required_score. Apparently the test emails I was
using was only adding up to 2.4 (I needed at least 5.0 to trigger the
rewrite_header.

As a test, I modifed the required score to 2.0 and sent my test email
through again. This time, it was rewritten!"




On 4/9/19 12:04 PM, jdw wrote:
Good catch about the subject, thanks. But still no go.

There's no errors anywhere. And other changes to the local.cf file work,
For example, I lowered the spam score and that takes effect, just not
the subject rewrite. It's a weird problem.

Tue Apr 09 2019 12:26:35 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
You have twice the word "subject", it's right?

Don't know if this works for you, mine has this:

# Add *****SPAM***** to the Subject header of spam e-mails
rewrite_header Subject *****SPAM _SCORE_*****

I don't remember seeing a detected spam with the subject rewrited.
Because we reject the mail with more other rules.

BTW, After many weeks searching, I find a correct rule filter but that
works for some kind of spam we get:

....
header LOCAL_RULE_SUBJ_190104 Subject =~ /\bTHE_STRING_OF_SPAM\b/i
score LOCAL_RULE_SUBJ_190104 8
....
# Set the threshold at which a message is considered spam (default: 5.0)
required_score 8

After writing rules, reload spamd:
# /etc/init.d/spamassassin reload
Check the spamd log to be sure that not error disable spamassassin:
# less /var/log/spamd.log

Regards


On 4/8/19 11:06 AM, jdw wrote:

Does anyone know why SA can't/wron't rewrite the subject? I'm using
this, but it has no effect:

rewrite_header subject Subject *****SPAM(_LEVEL_)****"

Thanks,

[#] Tue Apr 09 2019 15:10:26 EDT from jdw @ Uncensored

Subject: Re: Spamassass won't rewrite subject

[Reply] [ReplyQuoted] [Headers] [Print]

Yep, I saw that too (although I thought it was painfully obvious the rewrite should only occur if the email scores as spam). My installation won't even rewrite the subject of the GTUBE test with a score of 1000 :)

Tue Apr 09 2019 14:56:20 EDT from "s3cr3to" <s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't rewrite subject
I found this same question in SO
https://stackoverflow.com/questions/26065798/spamassassin-not-rewriting-subject-line

The answer was (quoted):
"I figured it out. The rewrite_header won't happen unless the email's
score is more than required_score. Apparently the test emails I was
using was only adding up to 2.4 (I needed at least 5.0 to trigger the
rewrite_header.

As a test, I modifed the required score to 2.0 and sent my test email
through again. This time, it was rewritten!"




On 4/9/19 12:04 PM, jdw wrote:
Good catch about the subject, thanks. But still no go.

There's no errors anywhere. And other changes to the local.cf file work,
For example, I lowered the spam score and that takes effect, just not
the subject rewrite. It's a weird problem.

Tue Apr 09 2019 12:26:35 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
You have twice the word "subject", it's right?

Don't know if this works for you, mine has this:

# Add *****SPAM***** to the Subject header of spam e-mails
rewrite_header Subject *****SPAM _SCORE_*****

I don't remember seeing a detected spam with the subject rewrited.
Because we reject the mail with more other rules.

BTW, After many weeks searching, I find a correct rule filter but that
works for some kind of spam we get:

....
header LOCAL_RULE_SUBJ_190104 Subject =~ /\bTHE_STRING_OF_SPAM\b/i
score LOCAL_RULE_SUBJ_190104 8
....
# Set the threshold at which a message is considered spam (default: 5.0)
required_score 8

After writing rules, reload spamd:
# /etc/init.d/spamassassin reload
Check the spamd log to be sure that not error disable spamassassin:
# less /var/log/spamd.log

Regards


On 4/8/19 11:06 AM, jdw wrote:

Does anyone know why SA can't/wron't rewrite the subject? I'm using
this, but it has no effect:

rewrite_header subject Subject *****SPAM(_LEVEL_)****"

Thanks,

 



[#] Tue Apr 09 2019 15:55:31 EDT from "s3cr3to" <s3cr3to@uncensored.citadel.org> to undisclosed-recipients: ;

Subject: Re: Spamassass won't rewrite subject

[Reply] [ReplyQuoted] [Headers] [Print]

Wow! good tip.

From here:
https://spamassassin.apache.org/gtube/

I put the string on the body and using an external account It was
detected and filtered (rejected).

On the external account I just got this Failure email:

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.
(edited@mail.ok)


On 4/9/19 1:10 PM, jdw wrote:
Yep, I saw that too (although I thought it was painfully obvious the
rewrite should only occur if the email scores as spam). My installation
won't even rewrite the subject of the GTUBE test with a score of 1000 :)

Tue Apr 09 2019 14:56:20 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
I found this same question in SO
https://stackoverflow.com/questions/26065798/spamassassin-not-rewriting-subject-line

The answer was (quoted):
"I figured it out. The rewrite_header won't happen unless the email's
score is more than required_score. Apparently the test emails I was
using was only adding up to 2.4 (I needed at least 5.0 to trigger the
rewrite_header.

As a test, I modifed the required score to 2.0 and sent my test email
through again. This time, it was rewritten!"




On 4/9/19 12:04 PM, jdw wrote:

Good catch about the subject, thanks. But still no go.

There's no errors anywhere. And other changes to the local.cf
file work,
For example, I lowered the spam score and that takes effect,
just not
the subject rewrite. It's a weird problem.

Tue Apr 09 2019 12:26:35 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
You have twice the word "subject", it's right?

Don't know if this works for you, mine has this:

# Add *****SPAM***** to the Subject header of spam e-mails
rewrite_header Subject *****SPAM _SCORE_*****

I don't remember seeing a detected spam with the subject rewrited.
Because we reject the mail with more other rules.

BTW, After many weeks searching, I find a correct rule filter
but that
works for some kind of spam we get:

....
header LOCAL_RULE_SUBJ_190104 Subject =~ /\bTHE_STRING_OF_SPAM\b/i
score LOCAL_RULE_SUBJ_190104 8
....
# Set the threshold at which a message is considered spam
(default: 5.0)
required_score 8

After writing rules, reload spamd:
# /etc/init.d/spamassassin reload
Check the spamd log to be sure that not error disable spamassassin:
# less /var/log/spamd.log

Regards


On 4/8/19 11:06 AM, jdw wrote:

Does anyone know why SA can't/wron't rewrite the subject? I'm using
this, but it has no effect:

rewrite_header subject Subject *****SPAM(_LEVEL_)****"

Thanks,

[#] Tue Apr 09 2019 16:20:48 EDT from jdw @ Uncensored

Subject: Re: Spamassass won't rewrite subject

[Reply] [ReplyQuoted] [Headers] [Print]

I an hesitant to reject. SA is good, but it's not infalliable. A few times I week I have to rescue some ham that ended up in my spam folder.

That's the main reason I want to rewrite the subject. Basically, I want the "star score" somewhere that I can filter on so I can reject spam over 5, but just mark spam under 5 so I can review it. But the star score is in a header named x-spam-level and the built-in sieve interface in Citadel doesn't offer that header to me. I can only use x-spam-score or x-spam-status. The status header has a numerical score which I could, in theory, use, but the sieve regex is escaping me. So, as work around I thought I would put the star score in the subject so I can filter on "******" stars.

But, the more I mess with this, the more I realize I just need to shut up and learn the sieve language and write a custom filter instead of trying to bend Citadel's UI to my will.

 

Tue Apr 09 2019 15:55:31 EDT from "s3cr3to" <s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't rewrite subject
Wow! good tip.

From here:
https://spamassassin.apache.org/gtube/

I put the string on the body and using an external account It was
detected and filtered (rejected).

On the external account I just got this Failure email:

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.
(edited@mail.ok)

On 4/9/19 1:10 PM, jdw wrote:
Yep, I saw that too (although I thought it was painfully obvious the
rewrite should only occur if the email scores as spam). My installation
won't even rewrite the subject of the GTUBE test with a score of 1000 :)

Tue Apr 09 2019 14:56:20 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
I found this same question in SO
https://stackoverflow.com/questions/26065798/spamassassin-not-rewriting-subject-line

The answer was (quoted):
"I figured it out. The rewrite_header won't happen unless the email's
score is more than required_score. Apparently the test emails I was
using was only adding up to 2.4 (I needed at least 5.0 to trigger the
rewrite_header.

As a test, I modifed the required score to 2.0 and sent my test email
through again. This time, it was rewritten!"




On 4/9/19 12:04 PM, jdw wrote:

Good catch about the subject, thanks. But still no go.

There's no errors anywhere. And other changes to the local.cf
file work,
For example, I lowered the spam score and that takes effect,
just not
the subject rewrite. It's a weird problem.

Tue Apr 09 2019 12:26:35 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
You have twice the word "subject", it's right?

Don't know if this works for you, mine has this:

# Add *****SPAM***** to the Subject header of spam e-mails
rewrite_header Subject *****SPAM _SCORE_*****

I don't remember seeing a detected spam with the subject rewrited.
Because we reject the mail with more other rules.

BTW, After many weeks searching, I find a correct rule filter
but that
works for some kind of spam we get:

....
header LOCAL_RULE_SUBJ_190104 Subject =~ /\bTHE_STRING_OF_SPAM\b/i
score LOCAL_RULE_SUBJ_190104 8
....
# Set the threshold at which a message is considered spam
(default: 5.0)
required_score 8

After writing rules, reload spamd:
# /etc/init.d/spamassassin reload
Check the spamd log to be sure that not error disable spamassassin:
# less /var/log/spamd.log

Regards


On 4/8/19 11:06 AM, jdw wrote:

Does anyone know why SA can't/wron't rewrite the subject? I'm using
this, but it has no effect:

rewrite_header subject Subject *****SPAM(_LEVEL_)****"

Thanks,

 



[#] Tue Apr 09 2019 16:50:52 EDT from "s3cr3to" <s3cr3to@uncensored.citadel.org> to Citadel_Support <room_Citadel_Support@uncensored.citadel.org>

Subject: Re: Spamassass won't rewrite subject

[Reply] [ReplyQuoted] [Headers] [Print]

I'm trying to setup this solution for our citadel server, this looks
like the right tool to protect a citadel server:

https://www.proxmox.com/en/proxmox-mail-gateway

"Proxmox Mail Gateway is the leading open-source email security solution
helping you to protect your mail server against all email threats the
moment they emerge. The flexible architecture combined with the
userfriendly, web-based management interface allows IT professionals and
businesses to control all incoming and outgoing emails with ease and to
protect their users from spam, viruses, phishing and trojans."

Right now I just have the ISO; years before, by some obscure setting
that I don't know how to use my previous attemps failed, but today are
new videos (youtube) that explain how to setup PMG with more detail.


On 4/9/19 2:20 PM, jdw wrote:
I an hesitant to reject. SA is good, but it's not infalliable. A few
times I week I have to rescue some ham that ended up in my spam folder.

That's the main reason I want to rewrite the subject. Basically, I want
the "star score" somewhere that I can filter on so I can reject spam
over 5, but just mark spam under 5 so I can review it. But the star
score is in a header named x-spam-level and the built-in sieve interface
in Citadel doesn't offer that header to me. I can only use x-spam-score
or x-spam-status. The status header has a numerical score which I could,
in theory, use, but the sieve regex is escaping me. So, as work around I
thought I would put the star score in the subject so I can filter on
"******" stars.

But, the more I mess with this, the more I realize I just need to shut
up and learn the sieve language and write a custom filter instead of
trying to bend Citadel's UI to my will.

Tue Apr 09 2019 15:55:31 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
Wow! good tip.

From here:
https://spamassassin.apache.org/gtube/

I put the string on the body and using an external account It was
detected and filtered (rejected).

On the external account I just got this Failure email:

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.
(edited@mail.ok)

On 4/9/19 1:10 PM, jdw wrote:

Yep, I saw that too (although I thought it was painfully obvious
the
rewrite should only occur if the email scores as spam). My
installation
won't even rewrite the subject of the GTUBE test with a score of
1000 :)

Tue Apr 09 2019 14:56:20 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
I found this same question in SO
https://stackoverflow.com/questions/26065798/spamassassin-not-rewriting-subject-line

The answer was (quoted):
"I figured it out. The rewrite_header won't happen unless the
email's
score is more than required_score. Apparently the test emails I was
using was only adding up to 2.4 (I needed at least 5.0 to
trigger the
rewrite_header.

As a test, I modifed the required score to 2.0 and sent my test
email
through again. This time, it was rewritten!"




On 4/9/19 12:04 PM, jdw wrote:

Good catch about the subject, thanks. But still no go.

There's no errors anywhere. And other changes to the local.cf
file work,
For example, I lowered the spam score and that takes effect,
just not
the subject rewrite. It's a weird problem.

Tue Apr 09 2019 12:26:35 EDT from "s3cr3to"
<s3cr3to@uncensored.citadel.org> Subject: Re: Spamassass won't
rewrite subject
You have twice the word "subject", it's right?

Don't know if this works for you, mine has this:

# Add *****SPAM***** to the Subject header of spam e-mails
rewrite_header Subject *****SPAM _SCORE_*****

I don't remember seeing a detected spam with the subject rewrited.
Because we reject the mail with more other rules.

BTW, After many weeks searching, I find a correct rule filter
but that
works for some kind of spam we get:

....
header LOCAL_RULE_SUBJ_190104 Subject =~ /\bTHE_STRING_OF_SPAM\b/i
score LOCAL_RULE_SUBJ_190104 8
....
# Set the threshold at which a message is considered spam
(default: 5.0)
required_score 8

After writing rules, reload spamd:
# /etc/init.d/spamassassin reload
Check the spamd log to be sure that not error disable spamassassin:
# less /var/log/spamd.log

Regards


On 4/8/19 11:06 AM, jdw wrote:

Does anyone know why SA can't/wron't rewrite the subject? I'm using
this, but it has no effect:

rewrite_header subject Subject *****SPAM(_LEVEL_)****"

Thanks,

Go to page: 1 2 3 4 [5] 6 7 8 9 ... Last