On 04/11/2021 21:51, Gionatan Danti wrote:
Dear all,
I was tasked to mark all messages coming from unauthenticated clients
(ie: incoming emails) with a specific subject line.
While subject rewrite is trivial per-se (via header_checks), I am having
big issues rewriting only selected messages. I f
Hi
I need disallow for just one client IP
I have two servers:
1)for outgoing (smtp)
2)for incomming (MX)
W dniu 04.11.2021 o 20:28, Viktor Dukhovni pisze:
> On Thu, Nov 04, 2021 at 09:35:22AM +0100, natan wrote:
>
>> Is available restrict any DSN sending to one IP for my MX ?
>>
>>smtp_disc
Il 2021-11-05 09:36 Dominic Raferd ha scritto:
Why permit auth connections on port 25? Restrict them to 587 and/or
465 then you can specify subject rewriting for (all) mails arriving
via port 25. (And you can use postscreen on port 25.)
Yeah, it would be a very clean solution. However, we have
On 05/11/2021 10:20, Gionatan Danti wrote:
Il 2021-11-05 09:36 Dominic Raferd ha scritto:
Why permit auth connections on port 25? Restrict them to 587 and/or
465 then you can specify subject rewriting for (all) mails arriving
via port 25. (And you can use postscreen on port 25.)
Yeah, it would
Il 2021-11-05 11:37 Dominic Raferd ha scritto:
I think you need to ensure that the rule runs only for Subject:
headers, escape square brackets in the if clause, and cover the
possibility of no space after 'Subject:' (note: all untested):
if /^Subject:/i
if !/^Subject: \[EXTERNAL\]/i
/^Subject: ?
Hi there,
I'm running postfix on containers and have set logging to stdout.
I notice that just the qmgr logs are sent to stdout, smtp logs are ignored.
I don't have syslog installed on this container...
Any idea how to fix this?
Also, is it possible to use milliseconds in the stdout logging?
I'm running postfix on containers and have set logging to stdout.
I notice that just the qmgr logs are sent to stdout, smtp logs are
ignored.
Any idea how to fix this?
http://www.postfix.org/postconf.5.html#maillog_file
http://www.postfix.org/postconf.5.html#syslog_facility
...might be what
Thanks for the reply.
I've set the maillog_file to stdout but I don't get other logs (mainly the
delivery log comming from smtp process). It just shows qmgr logs in the
output.
Thanks
Em sex., 5 de nov. de 2021 às 11:28, escreveu:
> > I'm running postfix on containers and have set logging to s
I've set the maillog_file to stdout but I don't get other logs (mainly
the delivery log comming from smtp process). It just shows qmgr logs in
the output.
Did you see in the docs about the start up requirement?
Stdout logging requires that Postfix is started with "postfix
start-fg".
If y
Yes I did.
Thanks a lot for the help here.
As you can see, this is exactly the subject of this message: postfix-fg and
stdout. :)
But the output shows only qmgr logs. All others are suppressed.
Any ideas?
Thanks
Em sex., 5 de nov. de 2021 às 11:39, escreveu:
> > I've set the maillog_file to stdo
Rafael Azevedo:
> Yes I did.
> Thanks a lot for the help here.
> As you can see, this is exactly the subject of this message: postfix-fg and
> stdout. :)
> But the output shows only qmgr logs. All others are suppressed.
> Any ideas?
Let's stop further guessing games. What is the output from:
post
root@smtp21:/# ps aux
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 2612 608 pts/0Ss+ 10:50 0:00 sh -c
service syslog-ng start ; /root/start.sh ; tail -f /var/log/mail.log
root33 0.0 0.0 3980 3084 pts/0S+ 10:50 0:00
There is no maillog file setting. I need to see the configuration that
reproduces the problem, not a verbal description from faulty memmory.
That said, I see that your chroot settings differ for qmgr and smtp
delivery agents. This should not matter because Postfix opens socket
pathnames relative t
Sorry about that, I was testing the timestamp withing mail.log.
root@smtp21:/# postconf -nf
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
compatibility_level = 2
inet_interfaces = all
inet_protocols = all
mailbox_size_limit = 0
maillog_file =
This is the maillog_file=/dev/stdout output:
Nov 05 11:07:15 smtp21 postfix/qmgr[421]: 8A78016204F: from=,
size=598, nrcpt=1 (queue active)
Nov 05 11:07:15 smtp21 postfix/qmgr[421]: 8A78016204F: removed
Nov 05 11:07:16 smtp21 postfix/qmgr[421]: DD37C16204F: from=,
size=588, nrcpt=1 (queue active)
After disabling chroot, it worked!
Any clue about how can I have milliseconds in this output?
Huge thanks.
Em sex., 5 de nov. de 2021 às 12:34, Rafael Azevedo
escreveu:
> This is the maillog_file=/dev/stdout output:
>
> Nov 05 11:07:15 smtp21 postfix/qmgr[421]: 8A78016204F: from=<
> raf...@xxx
Rafael Azevedo:
> After disabling chroot, it worked!
LINUX bites, if chroot breaks relative pathnames for UNIX-domain
DGRAM sockets.
(If chroot broke relative pathnames for UNIX-domain STREAM sockets,
there should have been lots of bug reports already).
> Any clue about how can I have millisecon
Thanks Wietse,
After disabling chroot, everything worked just as expected.
Thanks a lot guys.
BR,
R
Em sex., 5 de nov. de 2021 às 13:01, Wietse Venema
escreveu:
> Rafael Azevedo:
> > After disabling chroot, it worked!
>
> LINUX bites, if chroot breaks relative pathnames for UNIX-domain
> DGRA
One last thing, is it possible to change the date format of the output?
Current format:
Nov 05 13:20:06 smtp21 postfix/smtp[136]: 9D86C60BBE
I'd like to use ISO format:
2021-10-29T19:37:52.017684-03:00 smtp21 postfix/smtp
Could that be possible?
Thanks
Em sex., 5 de nov. de 2021 às 13:10, Rafa
Rafael Azevedo:
> One last thing, is it possible to change the date format of the output?
>
> Current format:
> Nov 05 13:20:06 smtp21 postfix/smtp[136]: 9D86C60BBE
>
> I'd like to use ISO format:
> 2021-10-29T19:37:52.017684-03:00 smtp21 postfix/smtp
See my reply in the quoted message below.
W
Linux docker-1 4.15.0-161-generic #169-Ubuntu SMP Fri Oct 15 13:41:54 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
Em sex., 5 de nov. de 2021 às 14:09, Wietse Venema
escreveu:
> Rafael Azevedo:
> > One last thing, is it possible to change the date format of the output?
> >
> > Current format:
> > Nov
Rafael Azevedo:
> Linux docker-1 4.15.0-161-generic #169-Ubuntu SMP Fri Oct 15 13:41:54 UTC
> 2021 x86_64 x86_64 x86_64 GNU/Linux
Is there an ISO download site? I don't have Kernel 4.15 but
I could byukld a VM for it.
Wietse
On Fri, Nov 05, 2021 at 12:00:56PM -0400, Wietse Venema wrote:
> Rafael Azevedo:
> > After disabling chroot, it worked!
>
> LINUX bites, if chroot breaks relative pathnames for UNIX-domain
> DGRAM sockets.
As a test, I'd suggest instead of disabling chroot for the delivery
agents, to also enable
Wietse,
I truly appreciate your effort and help here.
But please, don't worry. I've got it working and was able to sort data
using meta_sequenceId from syslog.
Don't know why syslog is not showing milliseconds correctly, it shows
.00 (using frac-digits(6)) on docker pods.
I have no idea where t
Hi Viktor,
Thanks for the reply!
SELinux is off, but AppArmor on.
Any further suggestions?
Thanks
Em sex., 5 de nov. de 2021 às 17:20, Viktor Dukhovni <
postfix-us...@dukhovni.org> escreveu:
> On Fri, Nov 05, 2021 at 12:00:56PM -0400, Wietse Venema wrote:
> > Rafael Azevedo:
> > > After disabl
> On 5 Nov 2021, at 4:37 pm, Rafael Azevedo wrote:
>
> Thanks for the reply!
>
> SELinux is off, but AppArmor on.
>
> Any further suggestions?
Since we want to understand the handling of unix-domain sockets
in container + chroot setups beyond just the immediate question
of logging to stdout, i
Viktor,
I was able to use ISO-DATE format through SYSLOG-NG, but lost the
milliseconds.
This is a non-chroot smtp log using syslog-ng
2021-11-05T17:51:25.00-03:00 smtp21 postfix/smtp 251 - [meta
sequenceId="77"] 8323E60BE3: to=, relay=
hotmail-com.olc.protection.outlook.com[104.47.57.161]:25
Viktor,
Sure, you may count on me for this!
POSTFIX logs using DOCKER non-chrooted and message_file=/dev/sdtout
Output extracted using "docker logs container-name"
Nov 05 18:09:53 smtp41 postfix/smtpd[390]: connect from smtp41.myisp.com
[A.B.C.D]
Nov 05 18:09:53 smtp41 postfix/smtpd[390]: 294FC
On Fri, 29 Oct 2021 00:24:36 -0400
Viktor Dukhovni wrote:
> On Thu, Oct 28, 2021 at 10:14:15PM -0400, Viktor Dukhovni wrote:
>
> > postqueue -j | jq -nr --argjson $days '
>
> Correction, that first line should be:
>
> postqueue -j | jq -nr --argjson days $days '
>
> Setting the "jq"
On Sat, Nov 06, 2021 at 12:32:14AM +0100, richard lucassen wrote:
> > > postqueue -j | jq -nr --argjson days $days '
> > > ...
>
> I have run the jq script for a week or so ($days = 5) and it works like
> a charm :-)
You're welcome. Of course if the number of days will never v
On 11/5/21 21:49, Viktor Dukhovni wrote:
Therefore, I would like to see reports of what you find:
[..]
* With AppArmor on or off
[..]
If auditd is installed and running AppArmor logs to audit logs.
So examining these logs might help to check whether AppArmor is blocking
something:
grep
sendmail -f m...@junc.eu -bv us...@lists.roundcube.net
: delivery via
mx.kolabsys.com[212.103.80.150]:25:
Server certificate not verified
how can i solve it ?
On Sat, Nov 06, 2021 at 03:28:35AM +0100, Benny Pedersen wrote:
> : delivery via mx.kolabsys.com[212.103.80.150]:25:
> Server certificate not verified
Your mail logs have more details.
> how can i solve it ?
Their TLSA records have been broken since ~May 12th 2021:
https://stats.dnsse
33 matches
Mail list logo
