RT_CorrespondAddressNotSet

A number of my queues do not have email addresses. This is fine as
people do not need to create tickets via email in those queues. Queues
without email addresses are mainly used internally by our staff.

If a queue does not have an email address specified sends out mail, it
uses the RT_CorrespondAddressNotSet address, which is fine. I know I can
control what this address is in RT_Siteconfig.pm, and I will change it
to something else.

When setting up the line in /etc/aliases for
RT_CorrespondAddressNotSet@mydomain.edu, I’m curious what I should do.
Is the queue name required? This email address is only for replies to
emails sent from RT, so I don’t want it to point to a queue. I just need
it as a means for people to reply back to existing tickets.

RT_CorrespondAddressNotSet: “|/etc/smrsh/rt-mailgate --queue general
–action correspond --url https://rt0.itcs.uiuc.edu/rt/

Does this make sense? Any suggestions on how to handle this in
/etc/aliases? Can I just leave the queue name out?

Does this make sense? Any suggestions on how to handle this in /etc/
aliases? Can I just leave the queue name out?

no, you cannot leave it out. mailgate doesn’t like that.

smime.p7s (2.47 KB)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1On Jan 5, 2007, at 12:18 PM, Vivek Khera wrote:

On Jan 5, 2007, at 10:43 AM, John Arends wrote:

Does this make sense? Any suggestions on how to handle this in /
etc/aliases? Can I just leave the queue name out?

no, you cannot leave it out. mailgate doesn’t like that.

If you leave it out, it defaults to “general”, which is fine if
you’re only sending mail about existing tickets, as the mailgate is
smart enough to deal with a ticket hitting any address, no matter
what queue it’s in. So actually, should just work. Vivek: what
failure case where you thinking of?

Jesse

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFFnrGeEi9d9xCOQEYRAjz3AKC5rtcn6r6T+3OGnAz/bUCT/qKMjwCeJd7g
cDkCAlBbbgMTTZOW+L+kHGs=
=GCqz
-----END PGP SIGNATURE-----

If you leave it out, it defaults to “general”, which is fine if
you’re only sending mail about existing tickets, as the mailgate is
smart enough to deal with a ticket hitting any address, no matter
what queue it’s in. So actually, should just work. Vivek: what
failure case where you thinking of?

must have misremembered. i was playing with the mailgate a lot the
other week trying to get autoresponder to ignore messages tagged with
"spam" by spam assassin, and it complained about some missing args if
I didn’t specify all of them.

smime.p7s (2.47 KB)

Hi, folks.

I have noticed, running my preliminary tests, when the RT System send an e-mail, the text RT_CorrespondAddressNotSet is showed. Why does it happen?

Wagner Pereira

PoP-SP/RNP - Ponto de Presen�a da RNP em S�o Paulo
CCE/USP - Centro de Computa��o Eletr�nica da Universidade de S�o Paulo
http://www.pop-sp.rnp.br
Tel. (11) 3091-8901

That means you didn’t configure the $CorrespondAddress or $CommentAddress in
etc/RT_SiteConfig.pm.
Mathieu Longtin
1-514-803-8977On Tue, Jan 12, 2010 at 12:24 PM, Wagner Pereira wpereira@pop-sp.rnp.brwrote:

Hi, folks.

I have noticed, running my preliminary tests, when the RT System send an
e-mail, the text RT_CorrespondAddressNotSet is showed. Why does it happen?

From: “Wagner Pereira via RT” <RT_CorrespondAddressNotSet>
Reply-To: RT_CorrespondAddressNotSet

Wagner Pereira

PoP-SP/RNP - Ponto de Presença da RNP em São Paulo
CCE/USP - Centro de Computação Eletrônica da Universidade de São Paulo
http://www.pop-sp.rnp.br
Tel. (11) 3091-8901


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