Viktor Dukhovni wrote on 06/08/2015 09:08:
Recent updates to the supported Postfix releases have updated the
default settings of the OpenSSL ciphers used for opportunistic TLS
from "export" to "medium.
Viktor,
thank you so much for this mini-howto.
As an added security I rotate DH parameters
Hi,
This Postfix 3.0.2.
I see this in maillog:
Aug 7 09:43:12 pfxp001 postfix/smtpd[18610]: warning: unknown macro name
"myhostname_ext" in expansion request
Aug 7 09:43:34 pfxp001 postfix/postscreen[12699]: warning: unknown
macro name "myhostname_ext" in expansion request
However:
# p
On 07 Aug 2015, at 06:14, Viktor Dukhovni wrote:
> On Fri, Aug 07, 2015 at 02:55:42AM +0200, DTNX Postmaster wrote:
>
>> For most systems, monitoring the status of their encryption just isn't
>> done at all; they use the defaults their device or server came with at
>> the time they purchased i
Rob Sterenborg (Lists):
> Hi,
>
> This Postfix 3.0.2.
>
> I see this in maillog:
>
> Aug 7 09:43:12 pfxp001 postfix/smtpd[18610]: warning: unknown macro name
> "myhostname_ext" in expansion request
>
> Aug 7 09:43:34 pfxp001 postfix/postscreen[12699]: warning: unknown
> macro name "myhostnam
Hello,
I have a Mailman + postfix setup (old versions: mailman 2.1.11,
postfix 2.5.5), and the mail server of one of subscribers' domain
started rejecting mails when "From" header domain is its own domain
(foo.com MX rejecting incoming @foo.com mails). This of course happens
when a @foo.com member
Hi,
maybe this, from postfix doc, will help you:
http://www.postfix.org/ADDRESS_REWRITING_README.html#generic
Willi
Am 07.08.2015 um 13:51 schrieb Vincent Pelletier:
> Hello,
>
> I have a Mailman + postfix setup (old versions: mailman 2.1.11,
> postfix 2.5.5), and the mail server of one of
On Fri, Aug 07, 2015 at 10:24:34AM +0200, Luigi Rosa wrote:
> >Recent updates to the supported Postfix releases have updated the
> >default settings of the OpenSSL ciphers used for opportunistic TLS
> >from "export" to "medium.
>
> Viktor,
> thank you so much for this mini-howto.
>
> As an added
On Thu, Aug 6, 2015, at 10:22 AM, Chris Adams wrote:
> Those are dbl response codes, not zen. You are mixing the two up
And you'd be correct! pebkac.
thanks.
Thank you Viktor.
On Fri, 07 Aug 2015 17:10:11 +0200,
"wilfried.es...@essignetz.de" wrote :
> maybe this, from postfix doc, will help you:
>
> http://www.postfix.org/ADDRESS_REWRITING_README.html#generic
The problem with this is that it will rewrite "To:" field too, so
sending to ...@foo.com pushes to their SMTP
Am 07.08.2015 um 18:24 schrieb Vincent Pelletier:
> On Fri, 07 Aug 2015 17:10:11 +0200,
> "wilfried.es...@essignetz.de" wrote :
>> maybe this, from postfix doc, will help you:
>>
>> http://www.postfix.org/ADDRESS_REWRITING_README.html#generic
>
> The problem with this is that it will rewrite "To:
On Fri, 07 Aug 2015 18:53:49 +0200,
"wilfried.es...@essignetz.de" wrote :
> That makes me wonder. Do they know the difference between "envelope-to"
> and "to"-field, or "envelope-from" and "from"-field? (This makes me
> remember to the beginning of my fechmail era - they do not use fetchmail
> or
On Fri, Aug 07, 2015 at 01:51:34PM +0200, Vincent Pelletier wrote:
> foo.com mangle_from:
>
> master.cf:
> mangle_from unix - - - - - smtpd
> -o header_checks=pcre:/etc/postfix/mangle_from.pcre
Don't confuse "smtp" with "smtpd".
$ postconf -Mf smtp/unix
smtp unix - -
Vincent Pelletier:
> Hello,
>
> I have a Mailman + postfix setup (old versions: mailman 2.1.11,
> postfix 2.5.5), and the mail server of one of subscribers' domain
> started rejecting mails when "From" header domain is its own domain
> (foo.com MX rejecting incoming @foo.com mails). This of course
14 matches
Mail list logo