Sorry for the long delay, wanted to do more research before posting it.
I've replaced some real values, like myhostname, with generic ones.
postconf -nf
command_directory = /usr/sbin
compatibility_level = 3.6
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
d
li...@lazygranch.com:
> Reply-To: jm84450...@gmail.com
Use header_checks (not body_checks) if you want to block that.
Still, I would be concerned about rejecting legitimate email.
Wietse
Your comments on the regex are useful since I didn't consider email
addresses with delimiters though none of the spam does at the moment.
Note a few of the spammers put their email address in the subject line.
Maybe that should be my first attempt at discarding. I can't think of a
non-spammer doing
> My expectation is that dovecot is not involved in this issue, but I'm
> not sure, so I mention anyway that that I have set
>
> virtual_transport = dovecot
Dovecot has the same setting: recipient_delimiter = +
In the logs, is the mail being rejected by postfix or by dovecot after postfix
t
> On 6 Nov 2021, at 3:43 pm, Jeff Abrahamson wrote:
>
> In main.cf I have set
>
> recipient_delimiter = +
>
> Reading the docs, I don't see anything else I ought to set for this to
> work: postfix should first try delivery to jeff+post...@p27.eu, then
> j...@p27.eu, and this second is known
> On 6 Nov 2021, at 5:33 pm, Gionatan Danti wrote:
>
>> I think that the default setting:
>>nested_header_checks = $header_checks
>> is unfortunate, perhaps we should change it to empty at compatibility
>> level >= 3.7.
>
> On current test setup, I do not define nested_headers_check at all.
Il 2021-11-06 19:04 Viktor Dukhovni ha scritto:
Though I don't recommend complex all-in-one configurations, you
use the "-o cleanup_service_name" option to configure separate
cleanup(8) services for separate smtpd(8) instances:
Yes, in my initial testing, I was missing -o cleanup_service_name
I used to be able to receive mail at, for example,
jeff+post...@p27.eu. Such mail is now refused. I suspect this
behaviour changed when I upgraded postfix version some months back.
In main.cf I have set
recipient_delimiter = +
Reading the docs, I don't see anything else I ought to set for
On Sat, Nov 06, 2021 at 06:51:03PM +0100, Gionatan Danti wrote:
> But I was also interested in a single server solution, not least to
> better understand postfix itself.
Though I don't recommend complex all-in-one configurations, you
use the "-o cleanup_service_name" option to configure separate
Il 2021-11-06 16:47 Viktor Dukhovni ha scritto:
On Thu, Nov 04, 2021 at 10:51:06PM +0100, Gionatan Danti wrote:
I was tasked to mark all messages coming from unauthenticated clients
(ie: incoming emails) with a specific subject line.
Best practice when requirements get complicated is to divid
On 2021-11-06 06:15, li...@lazygranch.com wrote:
Most of my spam contains a gmail address to reply to the spammer. I
would like to discard email whose body contains a gmail address. Since
discarding mail could get ugly, I would hope someone on the list can
eyeball my plan.
Indeed it is ugly. Y
On Thu, Nov 04, 2021 at 10:51:06PM +0100, Gionatan Danti wrote:
> I was tasked to mark all messages coming from unauthenticated clients
> (ie: incoming emails) with a specific subject line.
Best practice when requirements get complicated is to divide and
conquer. Use a separate dedicated machin
> On 27 Oct 2021, at 4:10 am, Walt CH wrote:
>
> For our company's global design, we have the MX servers (postfix) on both the
> US and the EU.
> When the two MX servers receive the messages, how to store the messages into
> a separated area such as the AU?
My standard recommendation is to per
> On 5 Nov 2021, at 5:14 pm, Rafael Azevedo wrote:
>
> POSTFIX logs using DOCKER non-chrooted and message_file=/dev/sdtout
Do you think you'll be able to report results for all the combinations?
* AppArmor on/off
* Chroot on/off for qmgr
* Chroot on/off for delivery agents
--
Viktor.
Walt,
Some questions before answering yours.
1. Is the MX record for "one mail domain" pointed to two different server
that’s located at US and EU ?
2. What you're wanting to do is, storing the same data on two different
areas?(Like US and AU?)
I once did store same data on two different areas
Perfect. That was the other solution I had been looking at.
==C
On Sat, 2021-11-06 at 10:25 -0300, Rafael Azevedo wrote:
> Since it was a container, I was not running any syslog, just using
> the log modules from docker.This is a sample output from postfix
> stdout.
> I fixed it using syslog-ng
Since it was a container, I was not running any syslog, just using the log
modules from docker.
This is a sample output from postfix stdout.
I fixed it using syslog-ng within the container.
Em sáb., 6 de nov. de 2021 às 09:56, Curtis Maurand
escreveu:
> On Fri, 2021-11-05 at 13:34 -0300, Rafael
> Their TLSA records have been broken since ~May 12th 2021:
>
> https://stats.dnssec-tools.org/explore/?kolabsys.com
>
> but they ignored the notification sent on the 13th. If you know a
> responsive contact there, let them know to not neglect their systems:
The roundcube / kolabsys team t
On Fri, 2021-11-05 at 13:34 -0300, Rafael Azevedo wrote:
> 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
>
>
Most of my spam contains a gmail address to reply to the spammer. I
would like to discard email whose body contains a gmail address. Since
discarding mail could get ugly, I would hope someone on the list can
eyeball my plan.
I added
body_checks = pcre:/etc/postfix/body_checks
to main.cf. I made
20 matches
Mail list logo
