Reliably identify email forwarded from inside to outside

2018-05-02 Thread Jozsef Kadlecsik
Hi, What would be the best way to identify email which is forwarded to external addresses by .forward, procmail or sieve rules? We have control over the mail gateways which handle all incoming-outgoing traffic, but no real access to the internal servers where the forward rules may be entered.

Re: Reliably identify email forwarded from inside to outside

2018-05-02 Thread Aban Dokht
Jozsef Kadlecsik wrote: Hi, What would be the best way to identify email which is forwarded to external addresses by .forward, procmail or sieve rules? As you know the maildomains you are accepting from external, just tag any mail from internal to external originating from diffent Envelope-F

Re: Reliably identify email forwarded from inside to outside

2018-05-02 Thread Wietse Venema
Jozsef Kadlecsik: > Hi, > > What would be the best way to identify email which is forwarded to > external addresses by .forward, procmail or sieve rules? > > We have control over the mail gateways which handle all incoming-outgoing > traffic, but no real access to the internal servers where the

Only accept "MAIL FROM:" one specific domain - REJECT all others

2018-05-02 Thread David Byrne
Hi, I’m trying to setup an internal postfix mail server for a very specific use for a client. They need to REJECT all mail that is attempted to be sent with a MAIL FROM: value of anything other than an address at “good-domain.com” (for this example). If someone was to MAIL FORM: ad...@google.co

Re: Only accept "MAIL FROM:" one specific domain - REJECT all others

2018-05-02 Thread Viktor Dukhovni
> On May 2, 2018, at 12:20 PM, David Byrne wrote: > > I thought I could do this in a sender access file within > smtpd_sender_restrictions, but I’m not having much luck. > > File: /etc/postfix/main.cf > smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/insiders > > File: :/et

Re: Removing trace records on submission MSA

2018-05-02 Thread @lbutlr
On 2018-05-01 (04:02 MDT), Philip Paeps wrote: > > I wonder if it wouldn't be easier to add a configuration option to smtpd to > suitably expurgate Received: headers of sensitive information. What information in the Received header do you consider sensitive? -- "You see, in this world there's

Re: Root user's sent mail

2018-05-02 Thread @lbutlr
On 2018-05-01 (04:27 MDT), Philip Paeps wrote: > > Correct. You should configure Mutt to use Maildir rather than mbox: > > set mbox_type= Maildir Thank you (and Noel), this is a better option than my first idea (piping the sent box through formail -s) -- "He is not only dull himself; he

Re: Reliably identify email forwarded from inside to outside

2018-05-02 Thread Jozsef Kadlecsik
On Wed, 2 May 2018, Wietse Venema wrote: > > What would be the best way to identify email which is forwarded to > > external addresses by .forward, procmail or sieve rules? > > > > We have control over the mail gateways which handle all incoming-outgoing > > traffic, but no real access to the i

Re: Removing trace records on submission MSA

2018-05-02 Thread Philip Paeps
On 2018-05-02 20:52:46 (+0200), @lbutlr wrote: On 2018-05-01 (04:02 MDT), Philip Paeps wrote: I wonder if it wouldn't be easier to add a configuration option to smtpd to suitably expurgate Received: headers of sensitive information. What information in the Received header do you consider sen

Re: Removing trace records on submission MSA

2018-05-02 Thread Wietse Venema
Philip Paeps: > On 2018-05-02 20:52:46 (+0200), @lbutlr wrote: > > On 2018-05-01 (04:02 MDT), Philip Paeps wrote: > >> I wonder if it wouldn't be easier to add a configuration option to > >> smtpd to suitably expurgate Received: headers of sensitive > >> information. > > > > What information in