Stop emails being sent for certain email addresses

Hi,

Presently we have several servers which send a notification email to our RT
instance. I just wondered does anyone no of a way that we can prevent
auto-replies and resolved emails going to these email addresses. The reason
being is it is just servername@ourdomain.co.nz which is not setup as a
mailbox and causes sendmail of course to log it’s inability to send it and
bounced mail recorded in our exchange server. Can we do this?
Regards

Aaron

We have a similar situation. We just changed the from address to be
noreply@rt.domain.com. We then create an alias for noreply and send it to
/dev/null.
You could write scrips for this as well. Above is just an easy way without
having to write anything. We let RT do its magic, but then just trash the
emails.

MattOn Mon, Mar 2, 2009 at 4:04 PM, Aaron Guise aaron@guise.net.nz wrote:

Hi,

Presently we have several servers which send a notification email to our RT
instance. I just wondered does anyone no of a way that we can prevent
auto-replies and resolved emails going to these email addresses. The reason
being is it is just servername@ourdomain.co.nz which is not setup as a
mailbox and causes sendmail of course to log it’s inability to send it and
bounced mail recorded in our exchange server. Can we do this?

Regards

Aaron


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Thanks Matt,

I never thought of that, I’ll give that a go it appears for some of the
emails at least it will work. But alas some are hard coded and cannot be
changed,On Tue, Mar 3, 2009 at 3:47 PM, Matt Hoover mhoover@thectogroup.com wrote:

We have a similar situation. We just changed the from address to be
noreply@rt.domain.com. We then create an alias for noreply and send it to
/dev/null.
You could write scrips for this as well. Above is just an easy way without
having to write anything. We let RT do its magic, but then just trash the
emails.

Matt

On Mon, Mar 2, 2009 at 4:04 PM, Aaron Guise aaron@guise.net.nz wrote:

Hi,

Presently we have several servers which send a notification email to our
RT instance. I just wondered does anyone no of a way that we can prevent
auto-replies and resolved emails going to these email addresses. The reason
being is it is just servername@ourdomain.co.nz which is not setup as a
mailbox and causes sendmail of course to log it’s inability to send it and
bounced mail recorded in our exchange server. Can we do this?

Regards

Aaron


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Presently we have several servers which send a notification email to our
RT instance. I just wondered does anyone no of a way that we can prevent
auto-replies and resolved emails going to these email addresses. The reason

Hi Aaron,

I believe this is what you are looking for:

http://wiki.bestpractical.com/view/OnCreateAutoReplyException

You define an array of emails that are never to get a reply

my @exceptionList = (‘robot@automated.sys’,
‘cyborg@sky.net’);

in the condition, and replies still go out to anyone not in that
array. I’d imagine it would be easy to use on actions other than
ticket create, as well.

/chown -R us:us /yourbase

I’m running RT v3.8.0 and RT::FM v2.2.1 and both are working ok. After
installing RT v.3.8.2 and RTFM 4.2.1 on a fresh directory, all non-ascii
characters are beeing displayed as it’s original ASCII characters
instead of UTF-8 characters:

 3.8.0: 35493 	Liberação de Acesso - 150.164.76.74
 3.8.2: 35493 	Liberação de Acesso - 150.164.76.74

It occurs only with tickets. RT titles, in portuguese, are displayed ok.

Updates were applied to database (RT 3.8.0 is working with 3.8.2 mysql
db schema). Original RT_Siteconfig.pm was copied to the new directory.
Nothing else was modified: I have both versions installed and I change
between versions stoping httpd, renaming RT’s directory (/opt/rt to
/opt/rt-3.8.2, /opt/rt-3.8.0 to /opt/rt) end restarting httpd.

Does anyone have a single suggestion about the source of the problem?

Thanks,

 Fernando Frota Machado de Morais
    Divisao de Redes de Comunicacao
    Centro de Computacao
    Universidade Federal de Minas Gerais
    Brasil
    Tel. +55(31)3409.4007  Fax. +55(31)3409.4004

I’m running RT v3.8.0 and RT::FM v2.2.1 and both are working ok. After
installing RT v.3.8.2 and RTFM 4.2.1 on a fresh directory, all non-ascii
characters are beeing displayed as it’s original ASCII characters
instead of UTF-8 characters:

 3.8.0: 35493 	Libera��o de Acesso - 150.164.76.74
 3.8.2: 35493 	Liberação de Acesso - 150.164.76.74

It occurs only with tickets. RT titles, in portuguese, are displayed ok.

Updates were applied to database (RT 3.8.0 is working with 3.8.2 mysql

Did you really read and applied steps explained in UPGRADING.mysql ??

That’s Great Rob,

I had missed that one on the wiki. That looks like it will suit perfectly.

Regards,

*Aaron Guise
027 212 6638
aaron@guise.net.nzOn Wed, Mar 4, 2009 at 6:28 AM, Rob Munsch rob.munsch@gmail.com wrote:

Presently we have several servers which send a notification email to
our

RT instance. I just wondered does anyone no of a way that we can
prevent

auto-replies and resolved emails going to these email addresses. The
reason

Hi Aaron,

I believe this is what you are looking for:

http://wiki.bestpractical.com/view/OnCreateAutoReplyException

You define an array of emails that are never to get a reply

my @exceptionList = (‘robot@automated.sys’,
‘cyborg@sky.net’);

in the condition, and replies still go out to anyone not in that
array. I’d imagine it would be easy to use on actions other than
ticket create, as well.


/chown -R us:us /yourbase

Aaron-

Another thought, you could also use your local email client on the RT server
to capture those emails and route them to /dev/null. Here is a url to the
postfix manual :

http://www.postfix.org/ADDRESS_REWRITING_README.html

MattOn Mon, Mar 2, 2009 at 9:53 PM, Aaron Guise aaron@guise.net.nz wrote:

Thanks Matt,

I never thought of that, I’ll give that a go it appears for some of the
emails at least it will work. But alas some are hard coded and cannot be
changed,

On Tue, Mar 3, 2009 at 3:47 PM, Matt Hoover mhoover@thectogroup.comwrote:

We have a similar situation. We just changed the from address to be
noreply@rt.domain.com. We then create an alias for noreply and send it
to /dev/null.
You could write scrips for this as well. Above is just an easy way
without having to write anything. We let RT do its magic, but then just
trash the emails.

Matt

On Mon, Mar 2, 2009 at 4:04 PM, Aaron Guise aaron@guise.net.nz wrote:

Hi,

Presently we have several servers which send a notification email to our
RT instance. I just wondered does anyone no of a way that we can prevent
auto-replies and resolved emails going to these email addresses. The reason
being is it is just servername@ourdomain.co.nz which is not setup as a
mailbox and causes sendmail of course to log it’s inability to send it and
bounced mail recorded in our exchange server. Can we do this?

Regards

Aaron


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com