In the future I will try to learn a bit more about amavis and what you
can do with it.
I read that you could add a disclaimer using amavis.
Le 06/02/2022 à 13:17, Matus UHLAR - fantomas a écrit :
On 06.02.22 11:07, Forums wrote:
From what I had been told and what I could read, port 465 is
de
On 06.02.22 11:07, Forums wrote:
From what I had been told and what I could read, port 465 is
deprecated and I had to use port 587. So for outgoing emails I use
port 587.
it was "deprecated" (not really standardised) for ~20 years, since RFC 2476
(December 1998) was introduced, but last 4 year
When I wanted to secure my mail server, I got help from people on forums
and on this mailing list.
So I followed their explanations and advice (DKIM, SPF, DMARC, spams,...).
From what I had been told and what I could read, port 465 is deprecated
and I had to use port 587. So for outgoing email
On 05.02.22 11:55, Forums wrote:
Before starting I checked configuration (main.cf & master.cf). In
main.cf I see that:
content_filter = smtp-amavis:[127.0.0.1]:10024 ==> It seems that this
filter directive override disclaimer filter directive if I put it in
master.cf.
correct. the content_f
After a lot of tests I've found how to do and it works.
I put disclaimer filter directive under "submission" line in master.cf
and keep "postscreen":
smtp inet n - y - 1 postscreen
[...]
submission inet n - y - - smtpd
-o c
I reconfigured everything by default (using "smtp = postscreen") in
order to start from the beginning. I would like to keep this spambots
protection or change it to "smtp = smtpd" with another spambots
protection (if possible).
Before starting I checked configuration (main.cf & master.cf). In
On 4 Feb 2022, at 9:05 am, Forums wrote:
Using "smtpd" instead of "postscreen" doesn't change issue.
On 04.02.22 09:09, Viktor Dukhovni wrote:
You'll have to back up that claim with:
# postfix reload
... submission of a new message via TCP port 25 ...
... logs showing t
> On 4 Feb 2022, at 9:05 am, Forums wrote:
>
> Using "smtpd" instead of "postscreen" doesn't change issue.
You'll have to back up that claim with:
# postfix reload
... submission of a new message via TCP port 25 ...
... logs showing that message entering and leaving the
Using "smtpd" instead of "postscreen" doesn't change issue.
Le 04/02/2022 à 14:59, Viktor Dukhovni a écrit :
=On 4 Feb 2022, at 8:39 am, Forums wrote:
smtp inet n - y - 1 postscreen
-o content_filter=disclaimer:
The postscreen(8) program does not
> =On 4 Feb 2022, at 8:39 am, Forums wrote:
>
> smtp inet n - y - 1 postscreen
> -o content_filter=disclaimer:
The postscreen(8) program does not implement content filters.
That setting should be for smtpd(8).
--
Viktor.
I checked the logs again and I can't see any error message "warning"
"error" "fatal" "panic".
For testing, my disclaimer script just write something in /tmp/file.
On master.cf I have this:
smtp inet n - y - 1 postscreen
-o content_filter=disclaimer:
[...]
Wietse Venema:
> Look in your LOGS.
>
> http://www.postfix.org/DEBUG_README.html#logging
In particular, logs that the message is handled by your filter,
to eliiminate basic mistakes.
Wietse
> Look for obvious signs of trouble
> =
> Postfix logs all failed
Look in your LOGS.
http://www.postfix.org/DEBUG_README.html#logging
Wietse
Look for obvious signs of trouble
=
Postfix logs all failed and successful deliveries to a logfile.
When Postfix uses syslog logging (the default), the file is usually
called /var/
Hello,
I try to add a disclaimer for all of my email accounts using altermime
but that doesn't work.
I did the following:
- created the user "filter": useradd -r -c "Postfix Filters" -d
/var/spool/filter filter
- created the directory /var/spool/filter
- changed directory permissions: ch
14 matches
Mail list logo
