Minor, but handy change to outbound messages


#1

I think we’re running 1.0.1. Here’s a patch that I keep rolling forward
as we upgrade because it’s turned out to be very helpful in getting
replies back to the queue rather than individuals. The jest of it is to
change the To: and the Bcc: lines in the following manner:

Bcc: $in_recipient$in_bcc

This way, their are no real addresses in the To: line, just an RFC
complaint named empty list of addresses. It’s greatly reduced the amount
of mail that we used to see twice: once as a part of ticket process and
once as a direct reply. It’s also helped funnel things back into the
ticket system since it leaves only the Rt address as an obvious reply
point. I’ve also added some crude filtering against some automated
senders. This could be done much better, but is useful to us.

*** /home/mathew/rt-1.0.1/lib/rt/support/mail.pm Tue Nov 16
02:38:29 1999— /usr/local/rt/lib/rt/support/mail.pm Mon Jun 5
16:15:37 2000
*** 101,113 ****
$in_subject =~ s/^(\s*)//;

  open (MAIL, "|$rt::mailprog $rt::mail_options");
  
  print  MAIL "Subject: [$rt::rtname \#". $in_serial_num . "]

($in_queue_id) $in_subject
! To: $in_recipient
! Bcc: $in_bcc
X-Request-ID: $in_serial_num
X-RT-Loop-Prevention: $rt::rtname
X-Sender: $in_current_user
— 101,116 ----
$in_subject =~ s/^(\s*)//;

  open (MAIL, "|$rt::mailprog $rt::mail_options");
  • # don't send replies to these guys MONTE -- hacky, so hacky
    
  • $in_recipient = '' if $in_recipient =~ /\@(verisign.com|uu.net)/i ;
    
    print  MAIL "Subject: [$rt::rtname \#". $in_serial_num . "]
    

($in_queue_id) $in_subject
! To: Requestor and $in_queue_id Staff: ;
! Bcc: $in_recipient$in_bcc
X-Request-ID: $in_serial_num
X-RT-Loop-Prevention: $rt::rtname
X-Sender: $in_current_user


#2

I actually put code into RT2 to do this last night :wink: I’m leery of changing
hte behavior in RT 1.0.x, but I’m sure a lot of folks will find this useful.

Thanks,
JesseOn Tue, Dec 05, 2000 at 11:27:57AM -0700, Monte Mitzelfelt wrote:

I think we’re running 1.0.1. Here’s a patch that I keep rolling forward
as we upgrade because it’s turned out to be very helpful in getting
replies back to the queue rather than individuals. The jest of it is to
change the To: and the Bcc: lines in the following manner:

To: Requestor and $in_queue_id Staff: ;
Bcc: $in_recipient$in_bcc

This way, their are no real addresses in the To: line, just an RFC
complaint named empty list of addresses. It’s greatly reduced the amount
of mail that we used to see twice: once as a part of ticket process and
once as a direct reply. It’s also helped funnel things back into the
ticket system since it leaves only the Rt address as an obvious reply
point. I’ve also added some crude filtering against some automated
senders. This could be done much better, but is useful to us.

*** /home/mathew/rt-1.0.1/lib/rt/support/mail.pm Tue Nov 16
02:38:29 1999— /usr/local/rt/lib/rt/support/mail.pm Mon Jun 5
16:15:37 2000


*** 101,113 ****
$in_subject =~ s/^(\s*)//;

  open (MAIL, "|$rt::mailprog $rt::mail_options");
  
  print  MAIL "Subject: [$rt::rtname \#". $in_serial_num . "]

($in_queue_id) $in_subject
Reply-To: $friendly_name <$temp_mail_alias>
From: $friendly_name <$temp_mail_alias>
! To: $in_recipient
Cc: $in_cc
! Bcc: $in_bcc
X-Request-ID: $in_serial_num
X-RT-Loop-Prevention: $rt::rtname
X-Sender: $in_current_user
— 101,116 ----
$in_subject =~ s/^(\s*)//;

  open (MAIL, "|$rt::mailprog $rt::mail_options");
  • # don't send replies to these guys MONTE -- hacky, so hacky
    
  • $in_recipient = '' if $in_recipient =~ /\@(verisign.com|uu.net)/i ;
    
    print  MAIL "Subject: [$rt::rtname \#". $in_serial_num . "]
    

($in_queue_id) $in_subject
Reply-To: $friendly_name <$temp_mail_alias>
From: $friendly_name <$temp_mail_alias>
! To: Requestor and $in_queue_id Staff: ;
Cc: $in_cc
! Bcc: $in_recipient$in_bcc
X-Request-ID: $in_serial_num
X-RT-Loop-Prevention: $rt::rtname
X-Sender: $in_current_user


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

that’s security the same way that asking for directions to topeka and
being told that a seal is a mammal is informative
-robin@apocalypse.org


#3

I actually put code into RT2 to do this last night :wink: I’m leery of changing
hte behavior in RT 1.0.x, but I’m sure a lot of folks will find this useful.

Nod, we use something similar about 6 months, but the change had to be
done a one layer up because modification of Monte’s patch kind (! To:
Requestor and $in_queue_id Staff: :wink: disharmonize To: line inside of
e-mail comments, etc.

Thanks,
Jesse

I think we’re running 1.0.1. Here’s a patch that I keep rolling forward
as we upgrade because it’s turned out to be very helpful in getting
replies back to the queue rather than individuals. The jest of it is to
change the To: and the Bcc: lines in the following manner:

To: Requestor and $in_queue_id Staff: ;
Bcc: $in_recipient$in_bcc

This way, their are no real addresses in the To: line, just an RFC
complaint named empty list of addresses. It’s greatly reduced the amount
of mail that we used to see twice: once as a part of ticket process and
once as a direct reply. It’s also helped funnel things back into the
ticket system since it leaves only the Rt address as an obvious reply
point. I’ve also added some crude filtering against some automated
senders. This could be done much better, but is useful to us.

*** /home/mathew/rt-1.0.1/lib/rt/support/mail.pm Tue Nov 16
02:38:29 1999— /usr/local/rt/lib/rt/support/mail.pm Mon Jun 5
16:15:37 2000


*** 101,113 ****
$in_subject =~ s/^(\s*)//;

  open (MAIL, "|$rt::mailprog $rt::mail_options");
  
  print  MAIL "Subject: [$rt::rtname \#". $in_serial_num . "]

($in_queue_id) $in_subject
Reply-To: $friendly_name <$temp_mail_alias>
From: $friendly_name <$temp_mail_alias>
! To: $in_recipient
Cc: $in_cc
! Bcc: $in_bcc
X-Request-ID: $in_serial_num
X-RT-Loop-Prevention: $rt::rtname
X-Sender: $in_current_user
— 101,116 ----
$in_subject =~ s/^(\s*)//;

  open (MAIL, "|$rt::mailprog $rt::mail_options");
  • # don't send replies to these guys MONTE -- hacky, so hacky
    
  • $in_recipient = '' if $in_recipient =~ /\@(verisign.com|uu.net)/i ;
    
    print  MAIL "Subject: [$rt::rtname \#". $in_serial_num . "]
    

($in_queue_id) $in_subject
Reply-To: $friendly_name <$temp_mail_alias>
From: $friendly_name <$temp_mail_alias>
! To: Requestor and $in_queue_id Staff: ;
Cc: $in_cc
! Bcc: $in_recipient$in_bcc
X-Request-ID: $in_serial_num
X-RT-Loop-Prevention: $rt::rtname
X-Sender: $in_current_user


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel


jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

that’s security the same way that asking for directions to topeka and
being told that a seal is a mammal is informative
-robin@apocalypse.org


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

Jan Okrouhly
-----------------------------------------±----okrouhly@civ.zcu.cz—
Laboratory for Computer Science | phone: (420 19) 7491588
University of West Bohemia | location: Univerzitni 22
Americka 42, 306 14 Pilsen, Czech Republic | room: UI404
------------------------------------------73!-de-OK1INC@OK0PPL.#BOH.CZE.EU-