On 23 August 2017 at 07:11, sreeranj s wrote:
> I am trying to change smtp_helo_name in our email server(postfix 2.6.6) to
> match with the one in mx record.
>
> I have specified the value as the one given below in main.cf, and
> reloaded the postfix. However telnet still shows the hostname as he
Hi,
I am trying to change smtp_helo_name in our email server(postfix 2.6.6) to
match with the one in mx record.
I have specified the value as the one given below in main.cf, and reloaded
the postfix. However telnet still shows the hostname as helo name. I could
change the smtp_banner, but not smt
On 23/08/17 00:15, Alef Veld wrote:
Does anyone know how to setup postfix in such a way so that clients can "auto
configure" (you just fill in the email address and password and it guesses the
settings)
I apologise if this is not a postfix thing perse.
This is not a postfix thing at all. Moreo
This is a long shot, but does anyone have any experience with setting up the
postman smtp plugin with postfix?
I can only send mails through without smtps or starttls (none). It seems to
login with UNKNOWN and I get a "cannot open socket message" in the postman
output when sending a test email
Does anyone know how to setup postfix in such a way so that clients can "auto
configure" (you just fill in the email address and password and it guesses the
settings)
I apologise if this is not a postfix thing perse.
Sent from my iPhone
On Tue, Aug 22, 2017, at 10:19 AM, Viktor Dukhovni wrote:
> > So that looks like it should work.
>
> Yes, but what security goal does this achieve?
Just what I said above. To help working with specific senders if only to
debug, etc.
I'm not looking for a policy or a philosphy, I'm just look
> On Aug 22, 2017, at 12:52 PM, yodel...@yepmail.net wrote:
>
> Based on your comment I found
>
>
> http://postfix.1071664.n5.nabble.com/Server-equivilent-of-smtp-tls-policy-maps-td26112.html
>
> that provides the concrete example
>
> smtpd_client_restrictions =
>check_client_access lmdb
On Tue, Aug 22, 2017, at 09:36 AM, /dev/rob0 wrote:
> See reject_plaintext_session, and in the case as you described,
> check_client_access:
>
> http://www.postfix.org/postconf.5.html#reject_plaintext_session
> http://www.postfix.org/postconf.5.html#check_client_access
> http://www.postfix.org/ac
On Tue, Aug 22, 2017 at 09:21:33AM -0700, yodel...@yepmail.net wrote:
> The reason that I'm asking is that I'd like to set my inbound
> policy =may by default, but for specific servers (that I may
> be working or warring with) sending email to me I want to
> force policy =encrypt.
>
> For infrequ
On Tue, Aug 22, 2017, at 09:13 AM, Viktor Dukhovni wrote:
> > Is there an inbound per-domain TLS policy map?
>
> http://www.postfix.org/TLS_README.html#client_tls_limits
Thanks. Okay I get that. But that reads like policy to me. It doesn't sound
like it's impossible.
The reason that I'm aski
> On Aug 22, 2017, at 12:08 PM, yodel...@yepmail.net wrote:
>
> Is there an inbound per-domain TLS policy map?
http://www.postfix.org/TLS_README.html#client_tls_limits
One may be tempted to try enforcing TLS for mail from specific sending
organizations, but this, too, runs into obstacles. One
On Tue, Aug 22, 2017, at 09:00 AM, Viktor Dukhovni wrote:
> The global security level set via "smtp_tls_security_level" is
> optionally preëmpted by the per-destination policy table (which
> can also override selected additional TLS settings).
Yeah I see the option to set the additional TLS para
> On Aug 22, 2017, at 11:52 AM, yodel...@yepmail.net wrote:
>
> I just want to make sure I understand per-site domain policy maps' priority.
>
> If I set up an outbound postfix instance with
>
> -o smtp_tls_security_level=may
> -o smtp_tls_policy_maps=lmdb:/etc/postfix/tls_policy_outbound
>
Hi
I just want to make sure I understand per-site domain policy maps' priority.
If I set up an outbound postfix instance with
-o smtp_tls_security_level=may
-o smtp_tls_policy_maps=lmdb:/etc/postfix/tls_policy_outbound
the way that works is that both are used, right?
In other words, the DE
On Tue, 22 Aug 2017 10:14:11 +, Alef Veld stated:
Now which clarifies things a lot. I'll probably keep 465 with wrapper mode to
support outlook expresss or other clients which want it and put 587 without.
On 22.08.17 07:23, Postfix User wrote:
MS Outlook Express was depreciated in Windows
On Tue, 22 Aug 2017 10:14:11 +, Alef Veld stated:
>Now which clarifies things a lot. I'll probably keep 465 with wrapper mode to
>support outlook expresss or other clients which want it and put 587 without.
MS Outlook Express was depreciated in Windows 7, way back on Oct 2009. It has
been yea
Reading http://www.postfix.org/TLS_README.html
Now which clarifies things a lot. I'll probably keep 465 with wrapper mode to
support outlook expresss or other clients which want it and put 587 without.
Thanks for the answer, I can now telnet to the port and get a greeting. I
didn't understand i
Hi Peter and Noel,
What is wrappermode ?
I see i have it enabled both for submission and smtps. Is it enabled by default
?
I can still send and receive email although some clients seem to have problems
with it.
These are my master.cf entries:
smtp inet n - n - -
Hi there again,
maybe this question got lost somehow or maybe it's not considered valid
but if someone out there could at least in some direction that I could
check to find a solution?
Regards
Markus
Am 15.08.2017 um 09:42 schrieb Markus Rosjat:
Hi there,
Im new to the whole postix, dkim
19 matches
Mail list logo
