Re: Adding a noreply address

2016-01-27 Thread Wietse Venema
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

2016-01-27 Thread 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, since Wietse posted: > > > > tr

Re: Adding a noreply address

2016-01-27 Thread Mick
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

2016-01-27 Thread Mick
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

2016-01-27 Thread Wietse Venema
@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

2016-01-27 Thread @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:} -- The Nixon I remembered was absolutely humorles

Re: Fwd: Adding a noreply address

2016-01-27 Thread Wietse Venema
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

2016-01-27 Thread Mick
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

2016-01-27 Thread 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 should be able to set the FR

SV: Adding a noreply address

2016-01-27 Thread Sebastian Nielsen
11:26 Till: postfix-users@postfix.org Ämne: Re: Adding a noreply address [Invalid] 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"

Re: Adding a noreply address

2016-01-27 Thread Darac Marjal
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

Re: Adding a noreply address

2016-01-26 Thread LuKreme
On Jan 26, 2016, at 09:22, Wietse Venema wrote: > transport_maps = inline:{u...@example.com=discard:} O, that is nifty! -- Suck it, Firefox!

Re: Adding a noreply address

2016-01-26 Thread btb
> On Jan 26, 2016, at 15.52, Steve Jenkins wrote: > > On Tue, Jan 26, 2016 at 12:07 PM, btb wrote: > On 2016.01.26 10.54, 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 al

Re: Adding a noreply address

2016-01-26 Thread Steve Jenkins
On Tue, Jan 26, 2016 at 12:07 PM, btb wrote: > On 2016.01.26 10.54, 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. >> > > if you int

Re: Adding a noreply address

2016-01-26 Thread btb
On 2016.01.26 10.54, 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. if you intend no mail to be sent to this address anyway, and will just t

Re: Adding a noreply address

2016-01-26 Thread Wietse Venema
Matt Bayliss: > 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. With Postfix 3.0 and later: /etc/postfix/main.cf: transport_maps = inline:{u...@example.com=

Re: Adding a noreply address

2016-01-26 Thread Ralph Seichter
On 26.01.2016 16:54, 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. While not necessarily "the best" solution, I use this: # pcre:/etc

Adding a noreply address

2016-01-26 Thread Matt Bayliss
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. I have come across a couple of tutorials which has instructions such as: ---