Dear All,
I have a top rule as:
X-SPAM-STATUS contains TRUE -> Move message to Folder -> Continue processing.
Then comes another rules to process the message that I want to be processed even it is SPAM.
It happens that if the message is detected as SPAM it does not do the next rules. (I suppose).
In the next rules I forward the message to other emails and they did not receive.
It already worked (forward email) when the email was not SPAM. (this is a montly received email).
Despite the message flaged as SPAM it is wrong flaged but this is another thing.
Perhaps this can have workarrounds (you can sugest, I changed the order of the rules) but I think that it is an anomally.
Thanks,
Luís Gonçalves.
I put the SPAM rule downwards. Will this work?
I've got a newish setup doing email for a few domains that I host, and am seeing messages that someone on an IP that whois reports as Stellar Group AS - apparently in France - is creating users on my board
The accounts being created are backup, mail, news, and blog, which strike me as useful usernames for sending spam from. If I delete the accounts, they are recreated shortly afterwards.
For the moment, I have set up these accounts manually, with Problem User rank and randomised passwords, which will hopefully stop anyone using them, but what seems problematic is that someone is able to create them in the first place.
Does anybody have any idea what's going on?
Phil
Sounds to me more nefarious than just spam. Why not just delete them, recreate them with a huge random password? Then they cant get in and create/use them.
wow sorry about that.. your last bit of manually creating somehow didn't show up until after i submitted.
Sounds to me more nefarious than just spam. Why not just delete them, recreate them with a huge random password? Then they cant get in and create/use them.
The accounts being created are backup, mail, news, and blog, which
strike me as useful usernames for sending spam from. If I delete the
accounts, they are recreated shortly afterwards.
Folks like that don't quite understand, do they. :)
So, you've basically got a few options.
1. If your system is intended to be private, simply turn off self-service user account creation.
2. If your system is intended to be public, make sure you configure it so that accounts cannot send outbound Internet email by default.
Both options are found in your system configuration screen.
Hello All,
I hope I am posting this question in the right place.
We are using the latest "Citadel Hardened-ol8arm-5.0.0-prod" and we would like to launch the instance as r8g.xlarge however it gives the following error "The instance configuration for this AWS Marketplace product is not supported"
is it possible to allow r8g.xlarge ?
thanks,
007Ray
I just wanted to share, I've attempted to install Citadel on non-systemd systems a number of times now and I just cannot get it to function properly without systemd. This may not be important to the Citadel community, but I wanted share my findings. I have a handful of clients that have taken a stance against systemd and am looking for a groupware solution for them. Outside of this specific issue, Citadel seems fantastic. I've had no issue building and/or installing on Debian or Ubuntu systems as long as they have systemd.
Kudos to them.
While LG or one of the others can chime in, and will, i suspect you will have to create your own start up script, using the systemD service definition as a guideline.
I have a handful of clients that have taken a stance against systemd
We are using the latest "Citadel Hardened-ol8arm-5.0.0-prod" and
we would like to launch the instance as r8g.xlarge however it
gives the following error "The instance configuration for this
AWS Marketplace product is not supported"
I didn't even know there was an AWS image for Citadel. If there is, it isn't maintained by us. Would love to hear more, though. In any case that would be a question for the image maintainer.
I've had no issue building and/or installing on Debian or Ubuntu
systems as long as they have systemd.
Well, you've got a couple of options. Citadel itself doesn't require systemd, but the build script delivered by Easy Install assumes that systemd is in place. So if you're attempting to run Citadel under sysvinit, you can do one of two things:
1. Before running Easy Install, do this command:
export EASYINSTALL_NOCONFIGURE=yes
This will make it install (or upgrade) the software, but no attempt will be made to create or modify the startup scripts. Then you can put your own startup scripts in place. If you need the commands to execute we can supply those.
2. Or you could just run the container (Docker) version of Citadel, which doesn't care what init system you're using. When you start it with a policy such as "restart=always" or "restart=unless-stopped" then the system takes care of that for you.
There are a number of people running Citadel on FreeBSD so it's definitely not a hard and fast requirement to have systemd.
Subject: RE: [Citadel Support] Re: Citadel On Non-SystemD Systems
how do I unsubscribe?
-----Original Message-----
From: IGnatius T Foobar <room_Citadel_Support@uncensored.citadel.org>
Sent: Wednesday, August 21, 2024 2:40 PM
To: Citadel Support <room_Citadel_Support@uncensored.citadel.org>
Subject: [Citadel Support] Re: Citadel On Non-SystemD Systems
I've had no issue building and/or installing on Debian or Ubuntu >systemsas long as they have systemd.Â
Well, you've got a couple of options. Citadel itself doesn't require
systemd, but the build script delivered by Easy Install assumes that systemd
is in place. So if you're attempting to run Citadel under sysvinit, you can
do one of two things:
1. Before running Easy Install, do this command:
export EASYINSTALL_NOCONFIGURE=yes
This will make it install (or upgrade) the software, but no attempt will
be made to create or modify the startup scripts. Then you can put your own
startup scripts in place. If you need the commands to execute we can supply
those.
2. Or you could just run the container (Docker) version of Citadel, which
doesn't care what init system you're using. When you start it with a
policy such as "restart=always" or "restart=unless-stopped"
then the system takes care of that for you.
There are a number of people running Citadel on FreeBSD so it's definitely
not a hard and fast requirement to have systemd.
Subject: RE: [Citadel Support] Re: Citadel On Non-SystemD Systems
I had unsubscribed from this mail list, but now I'm getting emails again,
how do I unsubscribe?
https://uncensored.citadel.org/listsub
But I'll take you off manually.
Subject: Automatic forward from my server to an gmail address.
Dear All,
I am getting problems giving the following message:
xxxxxx@gmail.com 550 (550-5.7.26 Your email has been blocked because the sender is unauthenticated. )
I have an automatic forward (through a rule) from my server (from an email address) to an gmail address.
Here explains the problem:
https://proton.me/blog/what-is-authenticated-received-chain-arc#what-problem-does-arc-solve
I did not read completely these sites.
With present Citadel features, can it solve the problem? Or will the features be included in a future release?
I suppose that the Citadel maintainers are more aware of this than me. That is why I am looking help.
Thanks,
Luís Gonçalves.
Subject: Re: Automatic forward from my server to an gmail address.
Notice that I have DKIM, SPD, DMARC.
Sat Aug 31 2024 14:31:23 EDT from luisgo Subject: Automatic forward from my server to an gmail address.Dear All,
I am getting problems giving the following message:
xxxxxx@gmail.com 550 (550-5.7.26 Your email has been blocked because the sender is unauthenticated. )I have an automatic forward (through a rule) from my server (from an email address) to an gmail address.
Here explains the problem:
https://proton.me/blog/what-is-authenticated-received-chain-arc#what-problem-does-arc-solve
I did not read completely these sites.
With present Citadel features, can it solve the problem? Or will the features be included in a future release?
I suppose that the Citadel maintainers are more aware of this than me. That is why I am looking help.
Thanks,
Luís Gonçalves.
Subject: Re: Automatic forward from my server to an gmail address.
Dear All,
Before I had Citadel I had Communigate (sorry to talk of foes). I leaved Communigate because they ended the Community Version and perhaps because they are Russians. (sorry if I damage someone feelings).
In Communigate they have 3 types of automated (with rules) forwards. Each one changes the header of the forward email differently. I can provide to the Citadel maintainers a version of Communigate that supports Community for testing. Or you can obtain an old version in Communigate western site. I have a version for Centos.
You can contact me though the email in the rules of https://uncensored.citadel.org/.
Thanks,
Luís Gonçalves.
Sat Aug 31 2024 14:31:23 EDT from luisgo Subject: Automatic forward from my server to an gmail address.Dear All,
I am getting problems giving the following message:
xxxxxx@gmail.com 550 (550-5.7.26 Your email has been blocked because the sender is unauthenticated. )I have an automatic forward (through a rule) from my server (from an email address) to an gmail address.
Here explains the problem:
https://proton.me/blog/what-is-authenticated-received-chain-arc#what-problem-does-arc-solve
I did not read completely these sites.
With present Citadel features, can it solve the problem? Or will the features be included in a future release?
I suppose that the Citadel maintainers are more aware of this than me. That is why I am looking help.
Thanks,
Luís Gonçalves.
Subject: Re: Automatic forward from my server to an gmail address.
Sorry my bad English. Not foes but competitors. Not leaved but left. Not though but through.
Mon Sep 02 2024 07:38:08 EDT from luisgo Subject: Re: Automatic forward from my server to an gmail address.Dear All,
Before I had Citadel I had Communigate (sorry to talk of foes). I leaved Communigate because they ended the Community Version and perhaps because they are Russians. (sorry if I damage someone feelings).
In Communigate they have 3 types of automated (with rules) forwards. Each one changes the header of the forward email differently. I can provide to the Citadel maintainers a version of Communigate that supports Community for testing. Or you can obtain an old version in Communigate western site. I have a version for Centos.
You can contact me though the email in the rules of https://uncensored.citadel.org/.
Thanks,
Luís Gonçalves.
Sat Aug 31 2024 14:31:23 EDT from luisgo Subject: Automatic forward from my server to an gmail address.Dear All,
I am getting problems giving the following message:
xxxxxx@gmail.com 550 (550-5.7.26 Your email has been blocked because the sender is unauthenticated. )I have an automatic forward (through a rule) from my server (from an email address) to an gmail address.
Here explains the problem:
https://proton.me/blog/what-is-authenticated-received-chain-arc#what-problem-does-arc-solve
I did not read completely these sites.
With present Citadel features, can it solve the problem? Or will the features be included in a future release?
I suppose that the Citadel maintainers are more aware of this than me. That is why I am looking help.
Thanks,
Luís Gonçalves.
The accounts being created are backup, mail, news, and blog, which
strike me as useful usernames for sending spam from. If I delete the
accounts, they are recreated shortly afterwards.
Folks like that don't quite understand, do they. :)
So, you've basically got a few options.
1. If your system is intended to be private, simply turn off self-service user account creation.
2. If your system is intended to be public, make sure you configure it so that accounts cannot send outbound Internet email by default.
Both options are found in your system configuration screen.
Agreed - switching off self-service user account creation was the first thing that I did, even before they started appearing, along with setting new accounts as Problem User and disabling email - this latter being, I suspect the reason for the new users.
However, another new account has been created since then.
Is there a setting somewhere to block IP numbers or ranges? Not a complete solution, but it might at least slow repeat offenders down.
Hi there I installed Citadel today. My group is weak in English. Requires installing the native language, in my case Polish. Is this possible? if so, how to do it?
if there is no such option, maybe there is a language file in this system that I can manually edit