On 15 Aug 2019, at 22:20, Andrew Bernard wrote:
Now am I further confused. What is $myorigin used for then?
It is used to qualify bare sender usernames for mail generated locally.
The nuances of when that applies can be found in 'man 5 postconf' in the
local_header_rewrite_clients and
Now am I further confused. What is $myorigin used for then?
Andrew
On 16/8/19 12:04 pm, Ralph Seichter wrote:
The "From" header is usually provided by the MUA. According to your
message headers, you are using Thunderbird, so that's where you define
your desired sender address(es). Postfix
* Andrew Bernard:
> Does this cover the case where each domain has its own header showing
> origin from each distinct domain?
The "From" header is usually provided by the MUA. According to your
message headers, you are using Thunderbird, so that's where you define
your desired sender
HI Raplh,
Does this cover the case where each domain has its own header showing
origin from each distinct domain? When I tried your suggestion they all
come out from $myorigin. What am I missing? Inbound works fine to any
number of virtual domains for me. It's outbound that has me perplexed.
These info are really helpful. thanks.
On 2019/8/15 星期四 下午 11:29, Viktor Dukhovni wrote:
On Thu, Aug 15, 2019 at 02:52:12PM +0800, Eliza wrote:
My MTA (postfix) has both 25 (non-SSL) and 465 (SSL) ports enabled.
Don't confuse port 25 used for (MTA-to-MTA) SMTP (inter-domain email
relay),
* Andrew Bernard:
> is there any way to configure Postfix to act for three separate
> domains without the necessity of separate IP's?
Yes, a single Postfix instance with one IP address can easily handle
multiple domains. http://www.postfix.org/VIRTUAL_README.html should get
you started.
-Ralph
I want to use my single VPS for three distinct domains. Simple for
webservers. I would also want to be able to send and receive email on
the three domains using Postfix. I understand there is postfix-multi.
Everything I have read so far uses separate IP addresses for this
scenario. Most VPS
On Thu, Aug 15, 2019 at 02:52:12PM +0800, Eliza wrote:
> My MTA (postfix) has both 25 (non-SSL) and 465 (SSL) ports enabled.
Don't confuse port 25 used for (MTA-to-MTA) SMTP (inter-domain email
relay), with ports 587 and 465 used in the MUA-to-MTA *SUBMIT*
protocol, which is very similar to
MTA-STS is not the only technique, DANE (rfc7672) can be used, too (and in
fact it is by many big german providers at least).
See this slides for an introduction: https://www.netnod.se/sites/default/files/
2016-12/Anders_Berggren_can_haz_secure_mail.pdf
Or this wikipedia page:
Hi,
on 2019/8/15 15:44, a wrote:
Maximum that you can do - enable STARTTLS and configure MTA-STS (rfc8461).
Is there a guide for that?
thanks.
You can't enforce remote peer to use SSL unless that peer is under your
control.
Maximum that you can do - enable STARTTLS and configure MTA-STS (rfc8461).
чт, 15 авг. 2019 г., 9:53 Eliza :
> Hello,
>
> My MTA (postfix) has both 25 (non-SSL) and 465 (SSL) ports enabled.
>
> How to enforce the
Hello,
My MTA (postfix) has both 25 (non-SSL) and 465 (SSL) ports enabled.
How to enforce the peer MTA send messages only to 465 port for better
secure communication?
Can I just shutdown port 25?
Thanks.
12 matches
Mail list logo