Wietse Venema:
> I agree with Viktor that updating the TLS proxy is the more feasible
> approach (caching the TLS sessions outside delivery agents). I also
> don't believe in changing the scheduler-to-delivery agent protocol.
> The Postfix approach is not to make an existing thing more complex,
> b
On 2018-03-20 (07:41 MDT), phep wrote:
>
> Let's say my domain is example.com. We have a bunch of servers that are
> authorised to use our SMTP server to relay their mail to the outside with
> something like :
>
> mynetworks: 192.168.250.0/24
>
> So far, so good.
I disagree. Allowing unauthe
On 2018-03-20 (02:15 MDT), Dominic Raferd wrote:
>
> openssl s_client -connect -starttls smtp
This is all I ever do. Unless I've been changing the configuration, I know that
if submission is responding, it is working.
If I have been changing the configuration, I know this.
It also doesn't in
> On Mar 20, 2018, at 9:41 AM, phep wrote:
>
> Now I have a sister organisation with domain example2.com that operates a web
> app than needs to send mail through our Postfix server and I want to relay
> mails sent from this web app provided the messages sender meets a specific
> email addre
phep skrev den 2018-03-20 14:41:
How can I do that in main.cf ? Simply adding the web app server IP to
mynetworks would not do the trick since I'd rather not relay any email
traffic from this server, only this webapp messages (notwithstanding
fake headers).
possible add sasl auth to the webapp
On 20.03.18 14:41, phep wrote:
Let's say my domain is example.com. We have a bunch of servers that
are authorised to use our SMTP server to relay their mail to the
outside with something like :
mynetworks: 192.168.250.0/24
So far, so good.
Now I have a sister organisation with domain example
Hi, I use postfix version 2.6 or 2.10 I forget
Can you test setting these settings ?
In main.cf
#relay_domains = test.uconn.edu $mydestination
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
tfix]# more relay_recipients
angelo.fazz...@test.uconn.edu OK
Not sure is virtual_alias_d
Hi,
Let's say my domain is example.com. We have a bunch of servers that are
authorised to use our SMTP server to relay their mail to the outside with
something like :
mynetworks: 192.168.250.0/24
So far, so good.
Now I have a sister organisation with domain example2.com that operates a
web
* Mario :
> Mar 18 17:21:25 jessie postfix/proxymap[873]: warning: connect to mysql
> server localhost: Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")
a) is the mysql server running?
b) does /var/run/mysqld/mysqld.sock exist?
c)
On 20 March 2018 at 08:34, Alex JOST wrote:
> Am 20.03.2018 um 09:15 schrieb Dominic Raferd:
>
>> I regularly test my remote mail servers (which use postfix - with
>> dovecot for authentication) to check they are live and functioning,
>> including that they are responding correctly to authorised
Am 20.03.2018 um 09:15 schrieb Dominic Raferd:
I regularly test my remote mail servers (which use postfix - with
dovecot for authentication) to check they are live and functioning,
including that they are responding correctly to authorised login with
STARTTLS.
I currently use this (sorry about l
I regularly test my remote mail servers (which use postfix - with
dovecot for authentication) to check they are live and functioning,
including that they are responding correctly to authorised login with
STARTTLS.
I currently use this (sorry about line breaks, the original is on one line):
timeou
12 matches
Mail list logo
