Re: Adding a noreply address

Viktor Dukhovni: > On Wed, Jan 27, 2016 at 04:03:08PM -0500, Wietse Venema wrote: > > > @lbutlr: > > > On 27 Jan 2016, at 05:46, Mick wrote: > > > > 'nore...@domain.com' needs to exist as a mailbox in order for you to > > > > discard mail to it as far as I can tell. > > > > > > Obviously not,

Re: Adding a noreply address

On Wed, Jan 27, 2016 at 04:03:08PM -0500, Wietse Venema wrote: > @lbutlr: > > On 27 Jan 2016, at 05:46, Mick wrote: > > > 'nore...@domain.com' needs to exist as a mailbox in order for you to > > > discard mail to it as far as I can tell. > > > > Obviously not, since Wietse posted: > > > > tr

Re: Adding a noreply address

Prior to Wietse's earlier post on this thread, I didn't know you could alias a non existent address back on itself in order to make the address known to Postfix. That's simply clever! I did know you can't silently discard messages using Transport if the address didn't exist, nor by aliasing

Re: Adding a noreply address

Indeed. On 27/01/2016 20:45, @lbutlr wrote: On 27 Jan 2016, at 05:46, Mick wrote: 'nore...@domain.com' needs to exist as a mailbox in order for you to discard mail to it as far as I can tell. Obviously not, since Wietse posted: transport_maps = inline:{u...@example.com=discard:}

Re: Adding a noreply address

@lbutlr: > On 27 Jan 2016, at 05:46, Mick wrote: > > 'nore...@domain.com' needs to exist as a mailbox in order for you to > > discard mail to it as far as I can tell. > > Obviously not, since Wietse posted: > > transport_maps = inline:{u...@example.com=discard:} Unfortunately, transport_maps

Re: Adding a noreply address

On 27 Jan 2016, at 05:46, Mick wrote: > 'nore...@domain.com' needs to exist as a mailbox in order for you to discard > mail to it as far as I can tell. Obviously not, since Wietse posted: transport_maps = inline:{u...@example.com=discard:} -- The Nixon I remembered was absolutely humorles

Re: is postfix vulnerable to this kind of attack?

On Jan 27, 2016, at 11:24 AM, Viktor Dukhovni wrote: > > On Wed, Jan 27, 2016 at 10:54:50AM -0800, Louis Kowolowski wrote: > >> I found an interesting email that got caught in my spam quarantine. I�m >> wondering if postfix is vulnerable to this kind of code execution (I�m >> aware that other c

Re: is postfix vulnerable to this kind of attack?

On Wed, Jan 27, 2016 at 10:54:50AM -0800, Louis Kowolowski wrote: > I found an interesting email that got caught in my spam quarantine. I�m > wondering if postfix is vulnerable to this kind of code execution (I�m > aware that other components could be vulnerable, but this question is > specificall

is postfix vulnerable to this kind of attack?

I found an interesting email that got caught in my spam quarantine. I’m wondering if postfix is vulnerable to this kind of code execution (I’m aware that other components could be vulnerable, but this question is specifically targeting postfix). The idea is to insert shell commands into various

Re: How to block sending outgoing mail from other domains in from field

Thank you very Jones, it solved the issue after mapping system users to email address. On Wed, Jan 27, 2016 at 8:10 PM, Noel Jones wrote: > On 1/27/2016 1:21 AM, Amit Bondwal wrote: > > Hi Everyone, > > > > In my postfix mail server, users are able to send mail on name of > > different domains >

Re: How to block sending outgoing mail from other domains in from field

On 1/27/2016 1:21 AM, Amit Bondwal wrote: > Hi Everyone, > > In my postfix mail server, users are able to send mail on name of > different domains > using from field in mail client software. > > For eg. I am using sendEmail mail client, and I can send emails with > hdfc.com doma

Re: Returning from custom restriction class and proceed with the remaning checks

On 1/27/2016 8:18 AM, Igor Sverkos wrote: > Hi, > > OK, when I jump from smtpd_client_restrictions via check_*_access into > a custom restriction class a "DUNNO" to end (skip) the custom > restriction class will send me back to smtpd_client_restrictions. > > Can I get postfix's dnswl_client check

Re: Returning from custom restriction class and proceed with the remaning checks

Hi, OK, when I jump from smtpd_client_restrictions via check_*_access into a custom restriction class a "DUNNO" to end (skip) the custom restriction class will send me back to smtpd_client_restrictions. Can I get postfix's dnswl_client check to return with DUNNO when I want this check to decide i

Re: Fwd: Adding a noreply address

Matt Bayliss: > Firstly, thanks for all the replies. Forget I said best practices, I agree > it's a rubbish term - what I really meant was the best way to achieve what > I want. > > I suppose I really have two requirements. 1) Monitoring devices that use > this Postfix installation as a relay sh

Re: Fwd: Adding a noreply address

On 27/01/2016 12:00, Matt Bayliss wrote: However when I send mail to nore...@domain.com from an external source (Gmail) I get a bounceback and "Recipient address rejected: User unknown in local recipient table;" in the log. Similarly when I try to use it in a

Fwd: Adding a noreply address

Firstly, thanks for all the replies. Forget I said best practices, I agree it's a rubbish term - what I really meant was the best way to achieve what I want. I suppose I really have two requirements. 1) Monitoring devices that use this Postfix installation as a relay should be able to set the FR

SV: Adding a noreply address

I would suggest against this, since there is a risk that servers aren't supporting this, and might deny the mail, discard it (send it to /dev/null, which I do with obvious spam), quarantine it or sort it to the end user's spam folder. Its better to set up a nore...@yourdomain.tld adress set to

Re: Adding a noreply address

On Tue, Jan 26, 2016 at 03:54:51PM +, Matt Bayliss wrote:   I'm trying to find the correct/best practice method for setting up a black hole email address for such items as "noreply" addresses when sending alerts from monitoring devices etc.  RFC 6854 adds the ability to use "Group Addresse