Re: Rewriting local addresses before pickup

> On Dec 22, 2018, at 11:34 PM, Matt Saladna wrote: > > I feared that. Are there any suitable sendmail wrappers that would provide > equivalent functionality? With Postfix, it suffices to set the "MAIL_CONFIG" environment variable, which results in /usr/sbin/sendmail submitting mail to a

Re: Rewriting local addresses before pickup

I feared that. Are there any suitable sendmail wrappers that would provide equivalent functionality? - Matt On 12/22/2018 7:47 PM, Viktor Dukhovni wrote: On Sat, Dec 22, 2018 at 07:32:37PM -0600, Matt Saladna wrote: I have an odd setup in which each base directory contains a complete

Re: Rewriting local addresses before pickup

On Sat, Dec 22, 2018 at 07:32:37PM -0600, Matt Saladna wrote: > I have an odd setup in which each base directory contains a complete > virtual filesystem with potentially overlapping usernames (UIDs are > unique). domain1.com could consist of system user user1 (UID: 500), > user2 (UID: 501).

Rewriting local addresses before pickup

Hi all, I have an odd setup in which each base directory contains a complete virtual filesystem with potentially overlapping usernames (UIDs are unique). domain1.com could consist of system user user1 (UID: 500), user2 (UID: 501). domain2.com could consist of user1 (UID: 502), user12 (UID:

Re: Good sender name

Philippe - Forums: > Hello. > > I want to have the good sender name when an email is sending from my > mailserver. > > I explain my problem: > > I have 5 different servers including my mailserver. > > When I send an email from my mailserver with a user (for example : > user=backup) I

Good sender name

Hello. I want to have the good sender name when an email is sending from my mailserver. I explain my problem: I have 5 different servers including my mailserver. When I send an email from my mailserver with a user (for example : user=backup) I receive the mail from "backup@server-name".

Re: More secure postfix

It's seem to be good with this option. Thanks. --- ## Philippe - Forums Le 2018-12-22 22:46, Wietse Venema a écrit : > Philippe - Forums: > >> Yes, with this option I can't send an email with my smartphone, because >> the smartphone IP have not proper reverse DNS. >> >>

Re: More secure postfix

Philippe - Forums: > Yes, with this option I can't send an email with my smartphone, because > the smartphone IP have not proper reverse DNS. > > And there is my problem: reject all IPs without proper reverse DNS but > accept my smartphone. Use permit_sasl_authenticated before

Re: Restricting Emails to a domain per email.

Philip: > Hi List, Seasons Greetings. > > I'm using *destination_rate_delay* to limit emails going out as quickly > is there a setting I'm not aware off that could limit the number of > emails to a particular domain based on a 24 hour block? Such large intervals make no sense because: - They

Re: More secure postfix

On 12/22/18 4:26 PM, Philippe - Forums wrote: > > Yes, with this option I can't send an email with my smartphone, > because the smartphone IP have not proper reverse DNS. > > And there is my problem: reject all IPs without proper reverse DNS but > accept my smartphone. > And what is special about

Re: More secure postfix

Yes, with this option I can't send an email with my smartphone, because the smartphone IP have not proper reverse DNS. And there is my problem: reject all IPs without proper reverse DNS but accept my smartphone. --- ## Philippe - Forums Le 2018-12-22 10:55, Matus UHLAR -

Restricting Emails to a domain per email.

Hi List, Seasons Greetings. I'm using *destination_rate_delay* to limit emails going out as quickly is there a setting I'm not aware off that could limit the number of emails to a particular domain based on a 24 hour block? If I could get pointed in the right direction it would be much

Re: More secure postfix

> On Dec 22, 2018, at 4:13 AM, Philippe - Forums wrote: > > smtpd_tls_cert_file=/path/to/certs/fullchain.pem > smtpd_tls_key_file=/path/to/certs/privkey.pem Fine, but if Let's Encrypt creates a single file with both the key and the certificate use that instead. >

Re: detect fake mx, tls security encrypt

Hi Robert, thanks. already saw that but i dont want to bother remote sites with a 'full verify'. still like the policy server approach. should be no big thing for a coder - familiar with perl. Am Samstag, 22. Dezember 2018 schrieb Robert Schetterer : > Am 22.12.18 um 07:55 schrieb Stefan Bauer:

Re: More secure postfix

On 22.12.18 10:13, Philippe - Forums wrote: I would like to secure more my postfix. My SMTP configuration actually is: _smtpd_tls_cert_file=/path/to/certs/fullchain.pem_ _smtpd_tls_key_file=/path/to/certs/privkey.pem_ _smtpd_tls_CAfile=/path/to/certs/chain.pem_ _smtpd_use_tls=yes_

More secure postfix

Hello, I would like to secure more my postfix. My SMTP configuration actually is: _smtpd_tls_cert_file=/path/to/certs/fullchain.pem_ _smtpd_tls_key_file=/path/to/certs/privkey.pem_ _smtpd_tls_CAfile=/path/to/certs/chain.pem_ _smtpd_use_tls=yes_ _smtpd_tls_session_cache_database =

Re: detect fake mx, tls security encrypt

Am 22.12.18 um 07:55 schrieb Stefan Bauer: nights later, a better approach seems to have a policy service that does the tls pre-checking. long time ago i wrote this https://blog.sys4.de/recipient-verification-tls-mandatory-modus-en.html perhaps it helps Something like this already