Re: [rt-users] Can't resolve in-progress ticket?
' = {
label = 'Open It', # loc
update = 'Respond',
},
'pending - resolved' = {
label = 'Resolve', # loc
update = 'Comment',
},
'pending - rejected' = {
label = 'Reject', # loc
update = 'Respond',
},
'pending - deleted' = {
label = 'Delete', # loc
},
'pending - pend-close' = {
label = 'Pend-close', # loc
},
'pending - inprogress' = {
label = 'Inprogress', # loc
},
'inprogress - open' = {
label = 'Open It', # loc
update = 'Respond',
},
'inprogress - resolved' = {
label = 'Resolve', # loc
update = 'Comment',
},
'inprogress - rejected' = {
label = 'Reject', # loc
update = 'Respond',
},
'inprogress - deleted' = {
label = 'Delete', # loc
},
'inprogress - pend-close' = {
label = 'Pend-close', # loc
},
'inprogress - pending' = {
label = 'Pending', # loc
},
],
},
# don't change lifecyle of the approvals, they are not capable to deal with
# custom statuses
approvals = {
initial = [ 'new' ],
active = [ 'open', 'stalled' ],
inactive= [ 'resolved', 'rejected', 'deleted' ],
defaults = {
on_create = 'new',
on_merge = 'resolved',
reminder_on_open = 'open',
reminder_on_resolve = 'resolved',
},
transitions = {
'' = [qw(new open resolved)],
# from = [ to list ],
new = [qw(open stalled resolved rejected deleted)],
open = [qw(new stalled resolved rejected deleted)],
stalled = [qw(new open rejected resolved deleted)],
resolved = [qw(new open stalled rejected deleted)],
rejected = [qw(new open stalled resolved deleted)],
deleted = [qw(new open stalled rejected resolved)],
},
rights = {
'* - deleted' = 'DeleteTicket',
'* - rejected' = 'ModifyTicket',
'* - *'= 'ModifyTicket',
},
actions = [
'new - open' = {
label = 'Open It', # loc
update = 'Respond',
},
'new - resolved' = {
label = 'Resolve', # loc
update = 'Comment',
},
'new - rejected' = {
label = 'Reject', # loc
update = 'Respond',
},
'new - deleted' = {
label = 'Delete', # loc
},
'open - stalled' = {
label = 'Stall', # loc
update = 'Comment',
},
'open - resolved' = {
label = 'Resolve', # loc
update = 'Comment',
},
'open - rejected' = {
label = 'Reject', # loc
update = 'Respond',
},
'stalled - open' = {
label = 'Open It', # loc
},
'resolved - open' = {
label = 'Re-open', # loc
update = 'Comment',
},
'rejected - open' = {
label = 'Re-open', # loc
update = 'Comment',
},
'deleted - open' = {
label = 'Undelete', # loc
},
],
},
);
Thanks,
Rezty Felty
Senior Linux Administrator
Adknowledge
816-559-1196
From: Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com
Date: Tuesday, August 26, 2014 at 9:16 AM
To: Alex Peters a...@peters.netmailto:a...@peters.net
Cc: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com
rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Can't resolve in-progress ticket?
Yes, we fixed it with lifecycle entries in the RT_SiteConfig.pm, I hadn’t
realized that lifecycles had replaced status’.
Thanks,
Rezty Felty
Senior Linux Administrator
Adknowledge
816-559-1196
From: Alex Peters a...@peters.netmailto:a...@peters.net
Date: Monday, August 25, 2014 at 5:59 PM
To: Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com
Cc: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com
rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Can't resolve in-progress ticket?
Sounds like a possible misconfiguration of the relevant lifecycle:
https://bestpractical.com/docs/rt/latest/customizing/lifecycles.html#Update-Transitions
On 26
Re: [rt-users] Can't resolve in-progress ticket?
Yes, we fixed it with lifecycle entries in the RT_SiteConfig.pm, I hadn’t realized that lifecycles had replaced status’. Thanks, Rezty Felty Senior Linux Administrator Adknowledge 816-559-1196 From: Alex Peters a...@peters.netmailto:a...@peters.net Date: Monday, August 25, 2014 at 5:59 PM To: Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com Cc: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com Subject: Re: [rt-users] Can't resolve in-progress ticket? Sounds like a possible misconfiguration of the relevant lifecycle: https://bestpractical.com/docs/rt/latest/customizing/lifecycles.html#Update-Transitions On 26/08/2014 1:40 am, Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com wrote: More info, have opened additional tickets to test, seems that when any ticket is placed in in-progress status, it then loses all status choices except in-progress. Thanks, Rezty Felty Senior Linux Administrator Adknowledge 816-559-1196 From: Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com Date: Monday, August 25, 2014 at 10:30 AM To: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com Subject: [rt-users] Can't resolve in-progress ticket? I just upgraded our RT system, from running on SLES 11 to RHEL 6.5, RT from 3.8.7 to 4.2.6, and mysql from an old version to the latest mariadb. Upgrade went smoothly, have tested everything, all seems to be well, except one thing. I have a ticket that a user placed in in-progress status after the upgrade, and now the only status anyone can place it in, even me as an RT Admin, is in-progress. Can’t resolve, open, delete, pending, etc. They aren’t even choices in the drop-down in the jumbo ticket display. Any idea what caused this, and how to resolve? Thanks, Rezty Felty Senior Linux Administrator Adknowledge 816-559-1196 -- RT Training - Boston, September 9-10 http://bestpractical.com/training -- RT Training - Boston, September 9-10 http://bestpractical.com/training
[rt-users] Can't resolve in-progress ticket?
I just upgraded our RT system, from running on SLES 11 to RHEL 6.5, RT from 3.8.7 to 4.2.6, and mysql from an old version to the latest mariadb. Upgrade went smoothly, have tested everything, all seems to be well, except one thing. I have a ticket that a user placed in in-progress status after the upgrade, and now the only status anyone can place it in, even me as an RT Admin, is in-progress. Can’t resolve, open, delete, pending, etc. They aren’t even choices in the drop-down in the jumbo ticket display. Any idea what caused this, and how to resolve? Thanks, Rezty Felty Senior Linux Administrator Adknowledge 816-559-1196 -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] Can't resolve in-progress ticket?
More info, have opened additional tickets to test, seems that when any ticket is placed in in-progress status, it then loses all status choices except in-progress. Thanks, Rezty Felty Senior Linux Administrator Adknowledge 816-559-1196 From: Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com Date: Monday, August 25, 2014 at 10:30 AM To: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com Subject: [rt-users] Can't resolve in-progress ticket? I just upgraded our RT system, from running on SLES 11 to RHEL 6.5, RT from 3.8.7 to 4.2.6, and mysql from an old version to the latest mariadb. Upgrade went smoothly, have tested everything, all seems to be well, except one thing. I have a ticket that a user placed in in-progress status after the upgrade, and now the only status anyone can place it in, even me as an RT Admin, is in-progress. Can’t resolve, open, delete, pending, etc. They aren’t even choices in the drop-down in the jumbo ticket display. Any idea what caused this, and how to resolve? Thanks, Rezty Felty Senior Linux Administrator Adknowledge 816-559-1196 -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] Difficulty implementing LDAP/AD Authorization
Well, we were unable to get the RT::Authen::ExternalAuth plugin to work, no matter what we tried, but I had a co-worker looking over my configs as well, and I had previously tried to make AD/LDAP auth work by just using Apache to do it . . . When looking in the vhost conf file for rt, he noticed I had placed my Apache Location Directive inside my Directory Directive, which is fairly common and I would never have thought twice about. However, in this instance, the Directory Directive began as such: Directory /opt/rt4/share/html and the Location Directive began as such: Location / Since they were two different paths, the Location Directive was never getting executed, which was where all the apache ldap auth info was. By moving the Location Directive outside the Directory Directive, and adding an alias: ScriptAlias / /opt/rt4/sbin/rt-server.fcgi/ we were able to make AD/LDAP authorization work. Thanks, Rezty Felty Senior Linux Administrator Adknowledge 816-559-1196 From: Alex Peters a...@peters.netmailto:a...@peters.net Date: Wednesday, July 30, 2014 at 7:31 PM To: Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com Cc: RT users rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com Subject: Re: [rt-users] Difficulty implementing LDAP/AD Authorization RT won't look at any changes you place in example RT_SiteConfig.pm files included with extensions (if that's why you've included that file in your previous e-mail). You need to copy the relevant changes into your RT installation's RT_SiteConfig.pm file. On 31/07/2014 3:12 am, Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com wrote: Jxplorer shows successful connection and authentication using the auth info I have in rt. Here is my /opt/rt4/etc/RT_SiteConfig.pm: # Any configuration directives you include here will override # RT's default configuration file, RT_Config.pm # # To include a directive here, just copy the equivalent statement # from RT_Config.pm and change the value. We've included a single # sample value below. # # This file is actually a perl module, so you can include valid # perl code, as well. # # The converse is also true, if this file isn't valid perl, you're # going to run into trouble. To check your SiteConfig file, use # this command: # # perl -c /path/to/your/etc/RT_SiteConfig.pm # # You must restart your webserver after making changes to this file. Set( $rtname, 'Adknowledge.com'); Set( $WebDomain, 'pkc-tracker02.ak-networks.comhttp://pkc-tracker02.ak-networks.com'); Set( $WebPort, 443); # You must install Plugins on your own, this is only an example # of the correct syntax to use when activating them. # Plugin( RT::Extension::QuickDelete ); # Plugin( RT::Extension::CommandByMail ); Set( @Plugins, qw(RT::Authen::ExternalAuth) ); and my /opt/rt4/local/plugins/RT-Authen-ExternalAuth/etc/RT_SiteConfig.pm, which I would think more important in this case: =head1 NAME External Authentication Configuration - Sample configs for LRT::Authen::ExternalAuth =head1 DESCRIPTION LRT::Authen::ExternalAuth provides a lot of flexibility with many configuration options. This file describes these configuration options and is itself a sample configuration suitable for dropping into your Cetc/RT_SiteConfig.pm file and modifying. =over 4 =item C$ExternalAuthPriority The order in which the services defined in ExternalSettings should be used to authenticate users. User is authenticated if successfully confirmed by any service - no more services are checked. You should remove services you don't use. For example, if you're only using My_LDAP, remove My_MySQL and My_SSO_Cookie. =cut Set($ExternalAuthPriority, [ 'My_LDAP', 'My_MySQL', 'My_SSO_Cookie' ] ); =item C$ExternalInfoPriority When multiple auth services are available, this value defines the order in which the services defined in ExternalSettings should be used to get information about users. This includes RealName, Tel numbers etc, but also whether or not the user should be considered disabled. Once a user record is found, no more services are checked. You CANNOT use a SSO cookie to retrieve information. You should remove services you don't use, but you must define at least one service. =cut Set($ExternalInfoPriority, [ 'My_LDAP', 'My_MySQL', ] ); =item C$ExternalServiceUsesSSLorTLS If this is set to true, then the relevant packages will be loaded to use SSL/TLS connections. At the moment, this just means LNet::SSLeay. =cut Set($ExternalServiceUsesSSLorTLS,0); =item C$AutoCreateNonExternalUsers If this is set to 1, then users should be autocreated by RT as internal users if they fail to authenticate from an external service. This is useful if you have users outside your organization who
[rt-users] Difficulty implementing LDAP/AD Authorization
I have a new install of RT 4.2.4 running on Centos 6.4 64 bit with Apache 2.2.15. I have installed RT::Authen::ExternalAuth and Net::LDAP, and have configured my /opt/rt4/local/plugins/RT-Authen-ExternalAuth/etc/RT_SiteConfig.pm with the right server address and LDAP user and password, and added Set( @Plugins, qw(RT::Authen::ExternalAuth) ); to the file /opt/rt4/etc/RT_SiteConfig.pm. I have restarted https, restarted the entire server, but i continue to see the same results, e.g. I can log in to RT with the default installed root account, but when I try any AD user, it fails, and the error I receive in both /var/log/messages and /var/log/httpd/error_log is the same: “FAILED LOGIN for user from serveraddress (/opt/rt4/sbin/../lib/RT/Interface/Web.pm:811) Any suggestions on where to begin troubleshooting this would be appreciated. Thanks, Rezty Felty Senior Linux Administrator Adknowledge 816-559-1196 -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] Difficulty implementing LDAP/AD Authorization
section below. You can remove values you don't
expect to match, but it's recommended to use 'Name' and 'EmailAddress'
at minimum. For example:
'attr_match_list' = [
'Name',
'EmailAddress',
],
You should not use items that can map to multiple users (such as a
RealName or building name).
=item attr_map
Mapping of RT attributes on to attributes in the external source.
Valid keys are attributes of an
LRT::User|http://bestpractical.com/rt/docs/latest/RT/User.html.
The values are attributes from your authentication source.
For example, an LDAP mapping might look like:
'attr_map' = {
'Name' = 'sAMAccountName',
'EmailAddress' = 'mail',
'Organization' = 'physicalDeliveryOfficeName',
'RealName' = 'cn',
...
},
=back
=cut
Set($ExternalSettings, {
# AN EXAMPLE DB SERVICE
'My_MySQL' = {
'type' = 'db',
'server'= 'server.domain.tld',
'database' = 'DB_NAME',
'table' = 'USERS_TABLE',
'user' = 'DB_USER',
'pass' = 'DB_PASS',
'port' = 'DB_PORT',
'dbi_driver'= 'DBI_DRIVER',
'u_field' = 'username',
'p_field' = 'password',
'p_enc_pkg' = 'Crypt::MySQL',
'p_enc_sub' = 'password',
'd_field' = 'disabled',
'd_values' = ['0'],
'attr_match_list' = [
'Gecos',
'Name',
],
'attr_map' = {
'Name' = 'username',
'EmailAddress' = 'email',
'ExternalAuthId' = 'username',
'Gecos' = 'userID',
},
},
# AN EXAMPLE LDAP SERVICE
'My_LDAP' = {
'type' = 'ldap',
'server'= '10.201.0.200',
'user' = 'apachel...@adknowledge.com',
'pass' = ‘redacted',
'base' = 'dc=adknowledge,dc=com',
'filter'= '(FILTER_STRING)',
'd_filter' = '(FILTER_STRING)',
'group' = 'GROUP_NAME',
'group_attr'= 'GROUP_ATTR',
'tls' = 0,
'ssl_version' = 3,
'net_ldap_args' = [version = 3 ],
'group_scope' = 'base',
'group_attr_value' = 'GROUP_ATTR_VALUE',
'attr_match_list' = [
'Name',
'EmailAddress',
'RealName',
],
'attr_map' = {
'Name' = 'sAMAccountName',
'EmailAddress' = 'mail',
'Organization' = 'physicalDeliveryOfficeName',
'RealName' = 'cn',
'ExternalAuthId' = 'sAMAccountName',
'Gecos' = 'sAMAccountName',
'WorkPhone' = 'telephoneNumber',
'Address1' = 'streetAddress',
'City' = 'l',
'State' = 'st',
'Zip' = 'postalCode',
'Country' = 'co'
},
},
# An example SSO cookie service
'My_SSO_Cookie' = {
'type' = 'cookie',
'name' = 'loginCookieValue',
'u_table' = 'users',
'u_field' = 'username',
'u_match_key' = 'userID',
'c_table' = 'login_cookie',
'c_field' = 'loginCookieValue',
'c_match_key' = 'loginCookieUserID',
'db_service_name' = 'My_MySQL'
},
} );
1;
Thanks,
Rezty Felty
Senior Linux Administrator
Adknowledge
816-559-1196
From: Marco Agostini comunelev...@gmail.commailto:comunelev...@gmail.com
Date: Wednesday, July 30, 2014 at 11:38 AM
To: Rezty Felty rfe...@adknowledge.commailto:rfe...@adknowledge.com
Subject: Re: [rt-users] Difficulty implementing LDAP/AD Authorization
Il 30/lug/2014 17:34 Rezty Felty
rfe...@adknowledge.commailto:rfe...@adknowledge.com ha scritto:
I have a new install of RT 4.2.4 running on Centos 6.4 64 bit with Apache
2.2.15. I have installed RT::Authen::ExternalAuth and Net::LDAP, and have
configured my
/opt/rt4/local/plugins/RT-Authen-ExternalAuth/etc/RT_SiteConfig.pm with the
right server address and LDAP user and password, and added Set( @Plugins,
qw(RT::Authen::ExternalAuth) ); to the file /opt/rt4/etc/RT_SiteConfig.pm. I
have restarted https, restarted the entire server, but i continue to see the
same results, e.g. I can log in to RT with the default installed root
account, but when I try any AD user
[rt-users] AUTO: Rezty Felty has left the building (returning 10/31/2011)
I am out of the office until 10/31/2011. I am moving on to a new opportunity, and 9/23 will be my last day at Hallmark. Please address all issues and inquiries to the backend team at hm-back...@hmkb2c.com.I will be available at 816.559.1196 for emergencies. Best Wishes, Rezty Felty Note: This is an automated response to your message Re: [rt-users] AutoCreate with Group Membership. sent on 9/22/2011 4:00:08 PM. This is the only notification you will receive while this person is away. This message, including any attachments, is for the designated recipient only and/or Hallmark Cards, Inc. employees. It may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail, disclosure of the information, or distribution by you is prohibited. RT Training Sessions (http://bestpractical.com/services/training.html) * Chicago, IL, USA September 26 27, 2011 * San Francisco, CA, USA October 18 19, 2011 * Washington DC, USA October 31 November 1, 2011 * Melbourne VIC, Australia November 28 29, 2011 * Barcelona, Spain November 28 29, 2011
Re: [rt-users] Where is my error?
OK, I was able to get my new RT system to quit timing out on create ticket by re-indexing the DB. I still am struggling with the RTFM problem, i have checked and the Article Text custom field exists in FM_CustomField, in RT the right to view article text is enabled for everyone, yet when you click on an article, it still is not showing article text. Any ideas, anyone? Rezty Felty Hallmark Digital - Infrastructure 816.559.1196 MSN rustyfe...@hotmail.com YIM HiRez_L AIM HiRezL ICQ 1932818 Skype Rezty.Felty Googletalk re...@kc-felty.net From: Rezty Felty rfel...@hallmark.com To: rt-users@lists.bestpractical.com Date: 08/17/2011 13:34 Subject: [rt-users] Where is my error? Sent by: rt-users-boun...@lists.bestpractical.com I have a production RT 3.8.0 instance running on a local Solaris server. I have been tasked with migrating it to a remote vmware RHEL Linux instance and upgrading to RT 3.8.8 at the same time. So I installed RT3.8.8 on the new server, and then did a MySQL dump of the db from the existing server, and moved it over and imported it to the new server, for my test instance for the migration. At first, RTFM did not work, (it would show RTFM, and article titles, but if you clicked on one, no article body), there were permission errors, I had a few problems. I engaged RT support for 4 hours of paid support, and we worked through all of those issues, and i documented all the steps we took. Then RT on the new server was working right and we scheduled a Saturday midnight cutover , the plan was to take another dump after shutting down the existing prod RT instance, copy it over, do the DB transforms for the upgrade, and all should be well. I did that, and RTFM would not show article bodies again, screens timed out opening new tickets, the server could not find cgi-bin, even though it was exactly in the location the error logs said it was looking. Here are the commands I ran, see if you can spot a step I missed, because I have to reschedule this and try again: 752 mv /data01/home/rfelty2/rt3_backup-20110813.sql.gz /data02/rt3/ 753 cd /data02/rt3/ 754 gunzip rt3_backup-20110813.sql.gz 755 mysql -h localhost -u root -p*PW-Redacted* rt3 rt3_backup-20110813.sql 757 vi /etc/my.cnf 758 service mysqld restart 759 mysql -h localhost -u root -p*PW-Redacted* rt3 rt3_backup-20110813.sql 760 cd /data02/rt3 761 mysql -h localhost -u root -p*PW-Redacted* rt3 rt3_backup-20110813.sql 762 /data02/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade 763 /data02/rt3/sbin/rt-setup-database --dba root -p*PW-Redacted* --action upgrade 764 /data02/rt3/sbin/rt-setup-database --action schema --datadir etc --dba admin --prompt-for-dba-password 765 /data02/rt3/sbin/rt-setup-database --action schema --datadir etc --dba root --prompt-for-dba-password 766 /data02/rt3/sbin/rt-setup-database --action acl --datadir etc/upgrade/2.1.0 --dba root --prompt-for-dba-password 767 /data02/rt3/sbin/rt-setup-database --action insert --datadir etc/upgrade/2.1.0 --dba root --prompt-for-dba-password 768 /data02rt3/sbin/rt-setup-database --action schema --datadir etc/upgrade/2.1.30 --dba root --prompt-for-dba-password 769 /data02/rt3/sbin/rt-setup-database --action schema --datadir etc/upgrade/2.1.30 --dba root --prompt-for-dba-password 770 /data02/rt3/sbin/rt-setup-database --action acl --datadir etc/upgrade/2.1.30 --dba root --prompt-for-dba-password 771 /data02/rt3/sbin/rt-setup-database --action insert --datadir etc/upgrade/2.1.30 --dba root --prompt-for-dba-password 772 /data02/rt3/sbin/rt-setup-database --action schema --datadir etc/upgrade/2.2.0RC2 --dba root --prompt-for-dba-password 773 perl etc/upgrade/upgrade-mysql-schema.pl rt3 root *PW-Redacted* sql.queries mysql -u root -p rt3 sql.queries 774 perl etc/upgrade/upgrade-mysql-schema.pl 775 perl ./etc/upgrade/upgrade-mysql-schema.pl 777 cd /data02/rt3/local/plugins/RT-FM/etc/upgrade/ 778 perl ./upgrade-mysql-schema.pl 779 perl ./upgrade-mysql-schema.pl rt3 root *PW-Redacted* 780 perl ./upgrade-mysql-schema.pl rt3 root *PW-Redacted* sql.queries 782 service httpd restart 783 vi /data02/rt3/etc/RT_SiteConfig.pm 784 service httpd restart 785 perl -c /data02/rt3/etc/RT_SiteConfig.pm 798 cd /data02/RTFM-2.4.3/ 799 perl Makefile.PL 800 make install 804 /data02/rt3/sbin/rt-setup-database --action schema --datadir etc/upgrade/2.1.0 806 /data02/rt3/sbin/rt-setup-database --action --dba root schema --datadir etc/upgrade/2.1.0 807 /data02/rt3/sbin/rt-setup-database --action schema --dba root --datadir etc/upgrade/2.1.0 808 /data02/rt3/sbin/rt-setup-database --action acl --dba root --datadir etc/upgrade/2.1.0 809 /data02/rt3/sbin/rt-setup-database --action insert --dba root --datadir etc/upgrade/2.1.0 812 /data02/rt3/sbin/rt
[rt-users] AUTO: Rezty Felty is out of the office (returning 08/22/2011)
I am out of the office until 08/22/2011. Avaialable at 816.559.1196 for emergencies. Note: This is an automated response to your message Re: [rt-users] Dump all except tickets+attachments? sent on 8/18/2011 7:33:11 AM. This is the only notification you will receive while this person is away. This message, including any attachments, is for the designated recipient only and/or Hallmark Cards, Inc. employees. It may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail, disclosure of the information, or distribution by you is prohibited. RT Training Sessions (http://bestpractical.com/services/training.html) * Chicago, IL, USA September 26 27, 2011 * San Francisco, CA, USA October 18 19, 2011 * Washington DC, USA October 31 November 1, 2011 * Melbourne VIC, Australia November 28 29, 2011 * Barcelona, Spain November 28 29, 2011
