It can be done in a "per recipient basis" with a content filter running with
filter_destination_recipient_limit = 1 and reinjecting the message to the
selected outgoing mailserver.
15 de Agosto de 2016 às 16:17, wie...@porcupine.org escreveu:
> Ian R. Justman:
>
>> Is the
Ian R. Justman:
> Is the "smtpd_check_recipient_mx_access" more for incoming connections
> rather than outgoing mails?
These lookups happen while receiving mail. You could specify a
FILTER action to force mail to go out in a particular direction,
but FILTER affects all recipients of the message,
Pat Suwalski:
> On 2016-08-15 12:46 PM, Robert Schetterer wrote:
> > i am not sure what your problem is ( do you mean sending reports with
> > strict spf ? ) however have a look on this too in your concept
>
> Not quite. I'm trying to satisfy DMARC policy for SPF that does not
> match mail-from
Hi, all.
I'm having a devil of a time dealing with various e-mail filtering
services as well as service providers wanting to block mail from my
servers, whether it's because I happen to have a VPS IP or
what-have-you. I try to run a clean ship and pounce on any bad stuff as
I see it.
On 2016-08-15 12:46 PM, Robert Schetterer wrote:
i am not sure what your problem is ( do you mean sending reports with
strict spf ? ) however have a look on this too in your concept
Not quite. I'm trying to satisfy DMARC policy for SPF that does not
match mail-from and envelope-from. I'd
Am 15.08.2016 um 18:12 schrieb Pat Suwalski:
> Hello,
>
> I'm looked in every corner of the internet for a solution to this
> seemingly simple problem I'm having.
>
> Last week, I started signing mail with opendkim, and hope to have DMARC
> fully implemented for all of my domains.
>
> I host
On 2016-08-15 12:22 PM, Wietse Venema wrote:
The solution is to require that the hosted domains provide the correct
envelope sender address. With submissions that use the Postfix sendmail
command, that's done with the "-f" command-line option.
I'm struggling with this concept.
I tried it on
Pat Suwalski:
> Hello,
>
> I'm looked in every corner of the internet for a solution to this
> seemingly simple problem I'm having.
>
> Last week, I started signing mail with opendkim, and hope to have DMARC
> fully implemented for all of my domains.
>
> I host dozens of domains, and send all
Hello,
I'm looked in every corner of the internet for a solution to this
seemingly simple problem I'm having.
Last week, I started signing mail with opendkim, and hope to have DMARC
fully implemented for all of my domains.
I host dozens of domains, and send all of their mail through a
Thomas Keller:
> In my logs, I have thousands of:
>
> postfix/smtpd: connect from unknown [186.225.115.62]
> postfix/smtpd: disconnect from unknown [186.225.115.62]
>
> when I watch the traffic on port 25, I see that the client tried AUTH
> LOGIN and was rejected:
>
> 220 mail..com ESMTP
On 8/15/2016 8:29 AM, Thomas Keller wrote:
> In my logs, I have thousands of:
>
> postfix/smtpd: connect from unknown [186.225.115.62]
> postfix/smtpd: disconnect from unknown [186.225.115.62]
>
> when I watch the traffic on port 25, I see that the client tried AUTH
> LOGIN and was rejected:
In my logs, I have thousands of:
postfix/smtpd: connect from unknown [186.225.115.62]
postfix/smtpd: disconnect from unknown [186.225.115.62]
when I watch the traffic on port 25, I see that the client tried AUTH
LOGIN and was rejected:
220 mail..com ESMTP
HELO mail..com
250 mail..com
12 matches
Mail list logo
