Feedback on Tutorial

Hello Postfix users, I made a relatively comprehensive tutorial[1] on how to set up a mail server (Postfix, Dovecot, Rspamd,..) and integrate it with Nextcloud. My goal was to create a all-in-one, step-by-step tutorial from beginning to end. I partly used other tutorials as a basis, but also di

Re: Postfix-3.3.0_1 Can't assign requested address

On Fri, June 15, 2018 15:40, Ralf Hildebrandt wrote: >> 84A19B389 1256 Wed Jun 13 16:03:45 byrn...@harte-lyne.ca >> (delivery temporarily suspended: connect to >> inet07.hamilton.harte-lyne.ca[216.185.71.27]:25: Can't assign >> requested address) > > ... > >> smtp_bind_address = 127.0.31.1

Re: Postfix-3.3.0_1 Can't assign requested address

James B. Byrne: > I am setting up a new mail hub in a FreeBSD-11.1 jail. When routing > traffic through this host to our existing IMAP service I see this > error in the maillog file: > > 84A19B389 1256 Wed Jun 13 16:03:45 byrn...@harte-lyne.ca > (delivery temporarily suspended: connect to >

Re: Postfix-3.3.0_1 Can't assign requested address

> 84A19B389 1256 Wed Jun 13 16:03:45 byrn...@harte-lyne.ca > (delivery temporarily suspended: connect to > inet07.hamilton.harte-lyne.ca[216.185.71.27]:25: Can't assign > requested address) ... > smtp_bind_address = 127.0.31.1 That's why. I think. -- [*] sys4 AG https://sys4.de, +49 (8

Postfix-3.3.0_1 Can't assign requested address

I am setting up a new mail hub in a FreeBSD-11.1 jail. When routing traffic through this host to our existing IMAP service I see this error in the maillog file: 84A19B389 1256 Wed Jun 13 16:03:45 byrn...@harte-lyne.ca (delivery temporarily suspended: connect to inet07.hamilton.harte-lyne.ca

Re: Update to recommended TLS settings

> On Jun 15, 2018, at 8:28 AM, micah anderson wrote: > > In 2015, Viktor wrote an email detailing the current recommended TLS > settings[0]. > > Now that we are three years later, are these still the best settings? Is > there something better we can be recommending? > > If anything, I think

Update to recommended TLS settings

In 2015, Viktor wrote an email detailing the current recommended TLS settings[0]. Now that we are three years later, are these still the best settings? Is there something better we can be recommending? If anything, I think that 'smtp_tls_security_level = may' should be recommended (it actually

Re: masquerade_domains map?

On 15/06/2018 12:58 CEST, Wietse Venema wrote: [...] And here is an example from several other Postfix features: Specify a list of [things], "/file/name" or "type:table" patterns, separated by commas and/or whitespace. The list is matched left to right, and the search stops on the

Re: masquerade_domains map?

Marco: > Hello Postfix users, > > while "masquerade_exceptions" supports "type:table" patterns, > "masquerade_domains" supports only a static list of domain names in main.cf. > > http://www.postfix.org/ADDRESS_REWRITING_README.html#masquerade > > > For me, it could be useful to manage also t

masquerade_domains map?

Hello Postfix users, while "masquerade_exceptions" supports "type:table" patterns, "masquerade_domains" supports only a static list of domain names in main.cf. http://www.postfix.org/ADDRESS_REWRITING_README.html#masquerade For me, it could be useful to manage also these domains in a file,

Re: spamming mailbox ?

On 14-06-18 15:27, Poliman - Serwis wrote: > I check the mail queue and the logs and this time I found some strange > thing. I used command "grep -r "emailemailemail.com > " /var/log/mail.log" and result is in > attached .txt file. If I understand properly there is ma