Hi,
This is the first time I have configured sender_access blacklisting -
although it works fine - i.e. the specific email address I have chosen to
blacklist get's their email blocked with /var/log/messages noting it as
"Sender address rejected:access denied". I notice that after an hour has
gon
On 30 August 2017 at 10:30, mbridgett wrote:
> Hi,
>
> This is the first time I have configured sender_access blacklisting -
> although it works fine - i.e. the specific email address I have chosen to
> blacklist get's their email blocked with /var/log/messages noting it as
> "Sender address reje
Thanks for the comprehensive explanation. What's strange is it's happening
for example to my gmail account (which I was using to test sender_access) as
well and I would have expected their mail servers to "behave". Theirs seems
to retry at random periods between 90 minutes and two hours. I sent
On 2017-08-30 12:45, mbridgett wrote:
Thanks for the comprehensive explanation. What's strange is it's
happening
for example to my gmail account (which I was using to test
sender_access) as
well and I would have expected their mail servers to "behave". Theirs
seems
to retry at random period
Wietse Venema:
> A. Schulze:
> > postqueue: panic: vbuf_print: output for '%s' exceeds space 0
>
> Unfortunately, there is no way that I can reproduce this in
> postfix-3.2.0, given the preconditions in this code. Does this
> machine have ECC meory? Does it have a history of programs crashing?
>
On 30.08.2017 03:24, Richard Damon wrote:
> I suggest you then talk the the legislators in the jurisdictions that
> MANDATE that many mailing list have clearly visible {munged, see P.S.}
> instructions.
Electronic mailing lists with a global reach which folks like myself
have been using since the
Wietse Venema:
> > The panic message says "%s" therefore this VBUF_SNPRINTF() call is
> > made while formatting a string with an fmt value of "%s".
>
> Unfortunately, the panic call overwrites the format string that was
> involved with the error, so the analysis for width and precision
> is wrong.
> soft_bounce = yes
^^ you have the soft_bounce safety net enabled. This changes all 5xx to
4xx replies, telling the sending server that it should try again later.
See http://www.postfix.org/postconf.5.html#soft_bounce
Doh, thanks. I put that in years ago for some reason that's long since gone
Hello,
I think that the description in this man page is confusing since cleanup
does not *always* insert missing headers (message-id etc).
The cleanup(8) daemon always performs the following transformations:
o Insert missing message headers: (Resent-) From:,
To:, Mes- sag
Hi, I'm getting such message logged after the warning: unknown smtpd
restriction: "milter_default_action"
All incoming mail is rejected.
What I'm trying to achieve is to get dkim validation working,
following this guide
https://wiki.debian.org/opendkim
regards in advance
On 2017-08-30 14:51, Daniel Armando Rodriguez wrote:
Hi, I'm getting such message logged after the warning: unknown smtpd
restriction: "milter_default_action"
Note that options in master.cf are without spaces around the "=".
All incoming mail is rejected.
What I'm trying to achieve is to ge
> On 2017-08-30 14:51, Daniel Armando Rodriguez wrote:
>>
>> Hi, I'm getting such message logged after the warning: unknown smtpd
>> restriction: "milter_default_action"
>
> Note that options in master.cf are without spaces around the "=".
yep
>> All incoming mail is rejected.
>>
>> What I'm tryi
On 2017-08-30 15:07, Daniel Armando Rodriguez wrote:
On 2017-08-30 14:51, Daniel Armando Rodriguez wrote:
Hi, I'm getting such message logged after the warning: unknown smtpd
restriction: "milter_default_action"
Note that options in master.cf are without spaces around the "=".
yep
All i
2017-08-30 10:16 GMT-03:00 Christian Kivalo :
>
>
> On 2017-08-30 15:07, Daniel Armando Rodriguez wrote:
>>>
>>> On 2017-08-30 14:51, Daniel Armando Rodriguez wrote:
Hi, I'm getting such message logged after the warning: unknown smtpd
restriction: "milter_default_action"
>>>
>>>
> On Aug 30, 2017, at 12:56 PM, Daniel Armando Rodriguez
> wrote:
>
> They are, look like this in main.cf
>
> # OpenDKIM
> milter_default_action = accept
> milter_protocol = 6
> smtpd_milters = local:/opendkim/opendkim.sock
> non_smtpd_milters = $smtpd_milters
Each parameter definitio
>> They are, look like this in main.cf
>>
>> # OpenDKIM
>> milter_default_action = accept
>> milter_protocol = 6
>> smtpd_milters = local:/opendkim/opendkim.sock
>> non_smtpd_milters = $smtpd_milters
>
> Each parameter definition must start in the *first*
> column of its text line. See
>
>
Has anyone done something like this for Postfix who is willing to share?
Rate limit outgoing mail based on the number of bad recipients as a more
intelligent rule that won't impact regular users (intended to stop abuse
of compromised accounts).
https://lists.exim.org/lurker/message/20100226.1
On Tue, 29 Aug 2017, Tom Browder wrote:
Gmail has a list of steps recommended to minimize spam identification,
particularly mail sent as bulk mail (as from mailing lists).
One of the recommendations is to use DKIM and that is clearly explained on the
postfix website.
The other steps are fair
*TL;DR* - my milter works, but I want it to operate /after/
smtpd_helo_restrictions, smtpd_recipient_restrictions, and
smtpd_client_restrictions have done their magic because it's logging
information from spam that gets filtered out by those guys (and also by
spamassassin).
Here's my config line:
Wietse Venema:
> Wietse Venema:
> > > The panic message says "%s" therefore this VBUF_SNPRINTF() call is
> > > made while formatting a string with an fmt value of "%s".
> >
> > Unfortunately, the panic call overwrites the format string that was
> > involved with the error, so the analysis for widt
20 matches
Mail list logo
