RT instance for INSPIRE operations

Feedback use

See SystemOperationsRTFeedback

Admin/Server issues

CNAME: inspirert4.cern.ch

https://inspirert.cern.ch/ == https://rt.inspirehep.net/

See also InspireRTatCERN

Update 12/14/2014: RT now on Openstack

As of 12/14/2014 the RT instance is rt-4.2.9 with some local customizations, additional plugins, and style adjustments. procmail setup is similar to the one outlined below, but codified in Puppet

For setup and configuration details see the Puppet repo https://git.cern.ch/web/it-puppet-hostgroup-inspire.git

You need proper egroup membership for access.

Setup

RT is installed on standard Openstack RHEL 6.6 instance inspirert4.cern.ch . There are no special requirements for the machine, although 16GB of RAM is likely the least amount necessary to maintain a responsive service.

Most of the configuration and setup is encoded in the git repo for Puppet hostgroup: inspire/rt

There is no prebuilt package for rt-4.2 and many of the required perl modules are not available as packages, either, so initial setup requires some manual work.

All sources are in /mnt/src

$ ls -al /mnt/src/
total 14864
drwxr-xr-x. 13 hschwand root 4096 Mar 3 22:01 ./
drwxr-xr-x 7 162 162 4096 Mar 3 21:59 ../
drwxr-xr-x. 5 hschwand def-cg 4096 Jan 6 18:41 module-install-rtx/
-rw-r--r--. 1 hschwand def-cg 287 Dec 14 23:24 README
drwxr-xr-x 10 hschwand def-cg 4096 Mar 2 05:32 rt-4.2.10/
-rw-r--r-- 1 hschwand def-cg 7628431 Mar 2 05:30 rt-4.2.10.tar.gz
-rw-r--r-- 1 hschwand def-cg 181 Feb 26 18:30 rt-4.2.10.tar.gz.asc
drwxrwxr-x. 10 hschwand apache 4096 Dec 23 05:43 rt-4.2.9/
-rw-r--r--. 1 hschwand def-cg 7496950 Oct 29 21:42 rt-4.2.9.tar.gz
-rw-r--r--. 1 hschwand def-cg 221 Oct 30 16:02 rt-4.2.9.tar.gz.asc
drwxr-xr-x. 8 hschwand def-cg 4096 Nov 26 06:04 rt-authen-externalauth/
drwxr-xr-x. 8 hschwand def-cg 4096 Nov 26 06:35 rt-client-cli/
drwxr-xr-x. 8 hschwand def-cg 4096 Nov 26 05:54 rt-extension-ajaxpreviewscrips/
drwxr-xr-x. 8 hschwand def-cg 4096 Nov 14 02:26 rt-extension-hotkeys/
drwxr-xr-x. 8 hschwand def-cg 4096 Jan 6 18:41 rt-extension-jsgantt/
drwxr-xr-x. 7 hschwand def-cg 4096 Dec 7 06:07 rt-extension-previewinsearch/
drwxr-xr-x. 6 hschwand def-cg 4096 Jan 6 18:40 rt-extension-rest2/
drwxr-xr-x. 6 hschwand def-cg 4096 Nov 30 03:00 rt-onlinedocs/

Follow the README for initial installation, in particular DB configuration and account setup. MariaDB config files are controlled by puppet.

Then run configure with these custom options

$ ./configure --prefix=/mnt/rt-4.2 --enable-developer --enable-graphviz --enable-gd --enable-gpg --enable-smime --with-db-database=rt42 --with-db-rt-user=rt_user --with-db-rt-pass=xxxxxxxx --with-web-user=apache

RT comes with helper scripts to test for and install missing perl modules via CPAN. Ensure that CPAN is installed and properly configured on the machine, then run

$ make testdeps

if this reports any missing modules, run

$ sudo make fixdeps

You may have to iterate those steps a few times to resolve dependencies. Once satisfied run

$ sudo make install

The local customization of RT_SiteConfig.pm and the web server setup is controlled by puppet.

In addition to the main rt package, several add-on packages are installed in the Inspire instance of RT. The sources are listed above. To install these addons

cd into each directory and run

export RTHOME=/mnt/rt-4.2

perl Makefile.PL

make

sudo sh -c '(export RTHOME=/mnt/rt-4.2 ; make install UNINST=1)'

Upgrade

Every few month a new minor release with bug-fixes and feature enhancements is released. Keep an eye on https://bestpractical.com/

To upgrade the running instance of RT, download the latest .tar.gz file from https://bestpractical.com/rt/download_file.html

unpack, configure as above. Carefully read the release notes and follow the upgrade instructions for the corresponding version at https://bestpractical.com/docs/rt/4.2/UPGRADING-4.2.html

Stop the web server and run

$ sudo /sbin/service httpd stop

$ sudo make install

which will install into the existing installation, preserving local customization in RT_SiteConfig.pm. Perform additional steps if any are outlined in the upgrade instructions for the particular versions involved.

Then clear the mason cache and restart httpd

$ sudo rm -rf /mnt/rt-4.2/var/mason_data/obj/3407077840

$ sudo /sbin/service httpd restart

Backups

Full dbdumps are performed nightly. This is controlled by an acrontab job which allows for AFS access. The backup script itself is puppetized.

$ acrontab -l
20 01 * * * inspirert4.cern.ch /mnt/rt-4.2/sbin/RT_backup.pl -lc


The backups reside on AFS, the 4 latest dumps are retained along with a snapshot of rt3 at the time of migration.

$ ls -al /afs/cern.ch/project/inspire/rt/backup/
total 20909496
drwxr-xr-x 3 simko us 2048 Mar 3 01:34 ./
drwxr-xr-x 3 root root 2048 Jan 28 17:41 ../
drwxr-xr-x 2 hschwand def-cg 2048 Mar 3 01:34 logs/
-rw-r--r-- 1 hschwand root 3605492080 Dec 16 04:17 rt3-backup-before-migration-12162014.sql.gz
-rw-rw-r-- 1 hschwand def-cg 3586713037 Feb 28 01:33 rt42-20150228.sql.gz
-rw-rw-r-- 1 hschwand def-cg 3586542110 Mar 1 01:34 rt42-20150301.sql.gz
-rw-rw-r-- 1 hschwand def-cg 3586589809 Mar 2 01:33 rt42-20150302.sql.gz
-rw-rw-r-- 1 hschwand def-cg 3587305594 Mar 3 01:34 rt42-20150303.sql.gz
-rw-r--r-- 1 hschwand root 3458670701 Dec 12 06:32 rt42test-20141212.sql.gz

In addition a .tar.gz snapshot of the rt production instance is also kept on AFS for quick recovery

$ ls -al /afs/cern.ch/project/inspire/rt
total 11749
drwxr-xr-x 3 root root 2048 Jan 28 17:41 ./
drwxrwxrwx 16 root root 6144 Dec 12 15:04 ../
drwxr-xr-x 3 simko us 2048 Mar 3 01:34 backup/
-rw-r--r-- 1 hschwand def-cg 974 Jan 18 21:08 README
-rwxr-xr-x 1 jlavik dw 59201 Dec 14 02:37 rt*
-rwxr-xr-x 1 hschwand root 59201 Dec 14 02:10 rt3*
-rwxr-xr-x 1 hschwand def-cg 79506 Dec 5 06:32 rt4*
-rw-r--r-- 1 hschwand root 5866495 Dec 14 21:59 rt-bundle-2014-12-14.tar.bz2
-rw-r--r-- 1 hschwand def-cg 5953872 Jan 17 00:16 rt-bundle-2015-01-17.tar.bz2

Restore dbdumps

Loading a rt42 dbdump is straightforward. I assume a database called rt42 exists with the correct parameters

mysql> show create database rt42;
+----------+---------------------------------------------------------------+
| Database | Create Database |
+----------+---------------------------------------------------------------+
| rt42 | CREATE DATABASE `rt42` /*!40100 DEFAULT CHARACTER SET utf8 */ |
+----------+---------------------------------------------------------------+
1 row in set (0.00 sec)

Then

$ zcat /afs/cern.ch/project/inspire/rt/backup/rt42-20150224.sql.gz | mysql -u root -h localhost -p rt42

This will recreate the exact state of the rt instance at the time of the dbdump.

Log Rotation

The log files for rt and the web server are rotated via logrotate. The config files are puppetized. Here is a snapshot of what they look like in March 2015

$ cat /etc/logrotate.d/rt42
/mnt/rt-4.2/var/log/rt.log {
rotate 360
weekly
dateext
compress
olddir /mnt/rt-4.2/var/log/archived-logs
missingok
notifempty
sharedscripts
delaycompress
copytruncate
}

and

$ cat /etc/logrotate.d/httpd-rt42
/mnt/rt-4.2/var/log/apache*log /mnt/rt-4.2/var/log/apache*err {
rotate 360
weekly
dateext
compress
olddir /mnt/rt-4.2/var/log/archived-logs
missingok
notifempty
sharedscripts
delaycompress
postrotate
/sbin/service httpd reload > /dev/null 2>/dev/null || true
endscript
}

OUTDATED pre 2015: Most of the info below is of historical interest only:

Login

Marko and Travis have admin privs on this Server. Tibor manages the configuration via Quattor.

Name

Eventually rename to inspire-support.cern.ch. If we are exposing ticket urls to users, need to alias to inspire-support.inspire-hep.net

incoming mail to support@inspire-hep.net

Cheatsheet

rt : /opt/rt3/ apachectl: /usr/sbin/apachectl mysql : rt3 rt_user

Command by Mail

RT for INSPIRE now allows commands by mail:

Making a comment rather than sending to requestor

At the moment the only way to do this is to change the "to" header from

admin@inspire-hep.net

to

rt-comment@inspire-hep.net

This will work for any queue and should ensure that your comment is threaded appropriately. Please be professional and make sure that, should the worst happen an a ticket thread become public, there is nothing extra embarrassing (beyond the annoyance of incorrect threading) in the comments.

Commands in subject body (not working yet)

DESCRIPTION
    This extension parse content of incoming messages for list commands.
    Format of commands is:

        Command: value
        Command: value
        ...

    You can find list of "COMMANDS commands below".

    Some commands (like Status, Queue and other) can be used only once.
    Commands that manage lists can be used multiple times, for example link,
    custom fields and watchers commands. Also, the latter can be used with
    "Add" and "Del" prefixes to add/delete values from the current list of
    the ticket you reply to or comment on.

  COMMANDS
   Basic
    Queue: <name>
        Set new queue for the ticket

    Subject: <string>
        Set new subject to the given string

    Status: <status>
        Set new status, one of new, open, stalled, resolved, rejected or
        deleted

    Owner: <username>
        Set new owner using the given username

    Priority: <#>
        Set new priority to the given value

    FinalPriority: <#>
        Set new final priority to the given value

   Dates
    Set new date/timestamp, or 0 to unset:

        Due: <new timestamp>
        Starts: <new timestamp>
        Started: <new timestamp>

   Time
    Set new times to the given value in minutes. Note that on
    correspond/comment "TimeWorked" add time to the current value.

        TimeWorked: <minutes>
        TimeEstimated: <minutes>
        TimeLeft: <minutes>

   Watchers
    Manage watchers: requestors, ccs and admin ccs. This commands can be
    used several times and/or with "Add" and "Del" prefixes, for example
    "Requestor" comand set requestor(s) and the current requestors would be
    deleted, but "AddRequestor" command adds to the current list.

        Requestor: <address> Set requestor(s) using the email address
        AddRequestor: <address> Add new requestor using the email address
        DelRequestor: <address> Remove email address as requestor
        Cc: <address> Set Cc watcher(s) using the email address
        AddCc: <address> Add new Cc watcher using the email address
        DelCc: <address> Remove email address as Cc watcher
        AdminCc: <address> Set AdminCc watcher(s) using the email address
        AddAdminCc: <address> Add new AdminCc watcher using the email address
        DelAdminCc: <address> Remove email address as AdminCc watcher

   Links
    Manage links. These commands are also could be used several times in one
    message.

        DependsOn: <ticket id>
        DependedOnBy: <ticket id>
        RefersTo: <ticket id>
        ReferredToBy: <ticket id>
        Members: <ticket id>
        MemberOf: <ticket id>

   Custom field values
    Manage custom field values. Could be used multiple times.

        CustomField.{CFName}: <custom field value>
        AddCustomField.{CFName}: <custom field value>
        DelCustomField.{CFName}: <custom field value>

    Short forms:

        CF.{CFName}: <custom field value>
        AddCF.{CFName}: <custom field value>
        DelCF.{CFName}: <custom field value>

This is an extension installed 13-6-2010.

http://search.cpan.org/dist/RT-Extension-CommandByMail/

It is installed from source in /opt/tbrooks (just dl and unpack tarball and run make install, and make mods in RT_SiteConfig (commited to RT branch.)

Migration Documentation

INSPIRT RT has been running well for several months. Pushing this down to the bottom of the wiki...

Email aliases

Test outgoing and incoming email from aliases

incoming

Working Great.

Tibor changed the redirections at the CERN level to get inspire-support@cernNOSPAMPLEASE.ch to go to inspirert

However, we still needed to make a change to aliases/aliases.db

[tbrooks@pcudssw1501 /etc]$ sudo pico aliases
[tbrooks@pcudssw1501 /etc]$ sudo newaliases
/etc/aliases: 79 aliases, longest 115 bytes, 1101 bytes total
[tbrooks@pcudssw1501 /etc]$ tail -1 aliases
inspire-support:  "|/usr/bin/procmail -m /opt/rt3/etc/procmail/rt_procmail" 

Now mail to help@inspire-hepNOSPAMPLEASE.net or inspire-support@cernNOSPAMPLEASE.ch both work correctly.

Any mail redirected to inspire-support@cernNOSPAMPLEASE.ch works fine. I currently redirect from inspire-hep.net and inspirebeta.net via gandi currently we have: admin@ help@ feedback@ authors@

rt-comment@support@ and inspire@ are redirected from inspire-hep.net but are not trafficed or user-facing

The queue

HEP-Additions

is used directly from the SLAC RT CLI to track uploads of eprints, and is needed for SLAC inputting workflow, but does not need an email address.

The queues

SPIRES-HEP SPIRES-INST SPIRES-CONF SPIRES-JOBS SPIRES-HEPNAMES

are populated from email addresses at SLAC (.procmailrc files in ~inst, ~spires, ~hepjobs, ~hepnames, ~conf). No configuration needed on the RT side, other than the existence of these queues and the ability of any user to create a ticket.

procmail

in inspire git repo, rt branch of tcb-public, there is rt/procmail containing rt_procmail which needs to be installed in

/opt/rt3/etc/procmail/

Also create:

/opt/rt3/var/procmail/

(Which may need to be created if it does not exist. The makefile for rt should do this, but I have not fully tested it so as not to risk messing up the production install.)

rt_procmail is responsible for filtering the mail, based on the original To: header into appropriate queues within the RT instance. it also kills some random junk mail, and should deliver failed messages in to /opt/rt3/var/procmail (which is also where the Logfile should be (pmlog)

A section in procmail is needed for each new address that should be delivered to a queue other than the default (HEP) queue, and it can be easily copied from others, just change the regexp for the address and the QUEUE for delivery.

The rt procmail in travis' git repo should be up to date as of 3-26-2011

outgoing

Working. RT_SiteConfig controls outgoing email address, and sends as inspire@inspire-hepNOSPAMPLEASE.net (change to support@inspire-hepNOSPAMPLEASE.net). Note that this is configurable on a per-queue basis, so if others (CDS/InDiCo) would like to use this instance, it will work fine (but see note in config section below about a potential hangup)

Note that this method reveals cern.ch buried deep in the headers, but this is potentially difficult to get rid of, as the mail will be passing through CERN mail gateway, I think. Anyway, it generally works, and isn't a big problem so the need for DNS/MX changes is slight.

SLAC config

SLAC config and local modifications commited in git (/inspire/rt) in rt branch of tcb-public inspire git repo. These have been modified to fit the inspirert.cern.ch instance, and committed back to git.

Note that we need Module/Refresh.pm in order to run RT in DevelMode which is useful for debugging etc.

Note that one thing that is not (easily) configurable on a per queue basis is the text in the brackets with ticket number, i.e. [INSPIRE-HEP #74522] Clearly this limits the utility for CDS/Indico folks, as I imagine they don't want to have that string in their tickets, and we don't want [CDSWare #5435] or similar. We could look into how easily this can be handled...but I'm not sure that it is simple.

test ticket resolution actions/autoreplies

NOTE change to Apache config

needed to support hardcoded links in saved searches in user prefs tables (!?)

    AddDefaultCharset UTF-8
    DocumentRoot /opt/rt3/share/html
# inserted to fix imported saved searches from SLAC instance
    Alias /rt3 /opt/rt3/share/html
    PerlModule Apache::DBI

Added several callbacks and overwrites to /opt/rt3//local/html/ (all in git and can be installed via make from git.)

  • reverse the order of history (Config setting)
  • change history and metadata in interface (/Ticket/Display.html)
  • add the basic edit functions on top of history (Callbacks/Ticket/Display.html/BeforeShowHistory and Element/SubmitSimple)
  • Dropdown for canned replies from RTFM (Callbacks/RTFM/Ticket/Update.html/BeforeMessageBox)
The first two actually we decided not to do, in conjunction with Denise. The code is available on SLAC instance, if needed.

Dump snapshot of DB and load

Create Dump

tcb@tislnx2:/home/tcb> /usr/bin/mysqldump --user=tis_rt_user --password --opt --skip-lock-tables --single-transaction --default-character-set=binary -h mysql-node01 --databases tis_rt3 > /tmp/rt/rt.sql
Enter password: 

[tbrooks@pcudssw1501 rt3]$ scp tcb@tislnx2.slac.stanford.edu:/tmp/rt/rt.sql tmp/rt.sql

...go to lunch...

This is a dump of the entire database from SLAC's TIS group. It, unfortunately includes many attachments which makes the size about 3G.

Reloading:

[tbrooks@pcudssw1501 ~]$ mysqladmin --user=root drop rt3Dropping the database is potentially a very bad thing to do.
Any data stored in the database will be destroyed.

Do you really want to drop the 'rt3' database [y/N] y
Database "rt3" dropped
[tbrooks@pcudssw1501 ~]$ mysql --user=root < /opt/rt3/tmp/rt.sql 
ERROR 1153 (08S01) at line 115: Got a packet bigger than 'max_allowed_packet' bytes

This means we didn't set the max allowed packet correctly in the my.cnf

let's check the slac install:

tcb@tislnx2 $ more /etc/my.cnf
[mysqld]
<...snip...>
#must use this to allow big attachments in RT
max_allowed_packet=16M

So I change this on inspirert Note: Needs to go in Quattor?

Resuming, we next hit:

[tbrooks@pcudssw1501 ~]$ mysql --user=root < /opt/rt3/tmp/rt.sql
ERROR 1114 (HY000) at line 1284: The table 'Attachments' is full

This looks like another settings issue. Unfortunately the settings are stored on the central mysql service which I cannot easily login to and get. I have asked our dba to report about this...however, it is pretty clear the problem was filling up the (small) /var/lib/mysql data directory with the attachments table. Thus I have to change, in my.cnf to a new datadir

datadir=/opt/rt3/var/mysql

Note change to quattor needed This will work for the moment, though in future one could imagine repartitioning, or some other scheme. (Note that because the filesystem filled up, I dropped the entire mysql datadir and reinstalled it from scrath with mysql_install_db ... I left the root password for mysql the same, though it ought to be changed)

...go to dinner...

Come back and find that the rt system is up and running with the SLAC data. The only thing needed was to

GRANT ALL on tis_rt3.* to rtuser@localhost

since the database name from slac had the 'tis' prefix I also had to reset the root pw for RT:

[tbrooks@pcudssw1501 rt3]$ sudo perl -I/opt/rt3/lib -MRT -e'\ 
               RT::LoadConfig(); RT::Init();\      
               my $u = RT::User->new($RT::SystemUser);\    
               $u->Load("root");\                                               
               print $u->SetPassword("secret");\                    
                          '

the instance is not yet ready to use, however the data is there....

redirect mail from spires@slac

Nothing done. Could we use rt-mailgate directly from slac procmail?

ToDo

A few things left to do on laundry list

nice to have:

  • search on email not working?
  • Clean up text ("SLAC" "INSPIRE" etc)
later:
  • Remove SPIRES prefix from queues (consequences on some special scripts and autoreplies)
  • put ticket number behind subject, not in front
  • careful check of my.cnf
  • Tried to get the INSPIRE image set up correctly, but not working, mason appears to interpret the image as a file to be read, rather than as an image, however, this is not true of all images I have, yet, I can view the images fine in my browser served locally. Not sure what this means, but not worth any more trouble.

Autoreply template

This is now stripped down for only two replies (the variable substitutions are removed and it is a simple if test


Subject: {$Ticket->Subject}

{
my $out_content = "";
$ticket_num = "$rtname \#".$Ticket->id;
my $tickets = RT::Tickets->new( $RT::SystemUser );  
$tickets->FromSQL( "Status = 'new' AND Queue = ". $Ticket->Queue );


if ($Ticket->QueueObj->Name =~ m/Feedback/){

$out_content = 'Thank you for your feedback regarding the INSPIRE Beta site.   We are looking forward to implementing community
suggestions and delivering a better service to you.
 
Of course we are busy with many suggestions, so we may not have time to write to you personally about your suggestion, but if we
need more information we will contact you.  If you'd like to inquire about the status of this suggestion please reference
$ticket_num in the subject of your email, or simply reply to this mail.

If your email refers to an issue with the data in the INSPIRE system, it will be redirected to help@inspire-hep.net, which is still
the correct address for corrections in both systems.

The INSPIRE team is a collaboration at CERN, DESY, Fermilab, and SLAC who are building INSPIRE, the next generation HEP Information
System.

Best Regards,
INSPIRE Team

'

}
else{
$out_content = 'Greetings from the SPIRES/INSPIRE Team!

Your message is being reviewed and routed to the appropriate SPIRES/INSPIRE specialist.  You do not need to respond to
this message.  If you would like to contact us regarding this message, please reference project number '.$ticket_num.' in the
subject line.  Alternately, simply reply to this message.

'.$tickets->Count.' people have requests that are ahead of yours, please be patient.

The INSPIRE team is a collaboration at CERN, DESY, Fermilab, and SLAC who are still running SPIRES and are building INSPIRE, the next
generation HEP Information System.

Thank you,

The SPIRES/INSPIRE Team

SPIRES: http://www.slac.stanford.edu/spires/
INSPIRE Project: http://www.projecthepinspire.net
'
}


return $out_content;

}

my.cnf

this is verbatim the my.cnf from the SLAC central server that served our RT instance.



[mysqld]

port = 3306
socket = /u2/mysql/db/mysql.sock
server-id = 1
datadir = /u2/mysql/db

read_only

log-bin = /u2/mysql/binlogs/db1
innodb_data_home_dir = /u2/mysql/ibdata
innodb_log_group_home_dir = /u2/mysql/iblogs

skip-slave-start

master_host = 192.168.1.2
master_user = ********
master_password = ********
master_port = 3306

myisam-recover = FORCE,BACKUP
default-table-type = InnoDB

innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 60
innodb_flush_method = O_DIRECT
innodb_thread_concurrency = 8

#
# 8GB machine
#

max_connections = 600
table_cache = 3000
open_files_limit = 20000
thread_cache = 400

innodb_buffer_pool_size = 3500M
innodb_additional_mem_pool_size = 20M

key_buffer_size = 512M
sort_buffer_size = 2M
read_buffer_size = 1M
read_rnd_buffer_size = 2M
tmp_table_size = 128M

innodb_log_file_size = 250M
innodb_log_buffer_size = 8M
innodb_log_files_in_group = 3

query_cache_type = 1
query_cache_size = 128M
query_cache_limit = 1M

log-slow-queries = /u2/mysql/db/mysql-sq.log
long_query_time = 1
log-long-format

max_allowed_packet = 64M

innodb_data_file_path = ibdata1:10G;ibdata2:10G;ibdata3:10G;ibdata4:10G;ibdata5:10G;ibdata6:10G;ibdata7:10G;ibdata8:10G


[client]
port = 3306
socket = /u2/mysql/db/mysql.sock

----

INSPIRE RT procmail map

Inspire RT version 3.8 runs on pcussd1501 at CERN, Tibor, Thorsten, Jan, SamK, and Mike S have sudo privs, maybe more. The Migration documentation above is partially helpful.

email to one of the list of email addresses that send records to RT will come by various paths to inspire-support@inspirertNOSPAMPLEASE.cern.ch

This is aliased at /etc/aliases to |/usr/bin/procmail -m /opt/rt3/etc/procmail/rt_procmail

in rt_procmail, the mail is routed to the proper queue according to the origin email address, emails having no such rules all go to the HEP queue

email list

There are a dozen or so email addresses, most on inspirehep.net, a few remaining on on slac.stanford.edu that send records to RT

Documentation from Gandi

On inspire-hep.net:

admin@ admin@inspirehepNOSPAMPLEASE.net
authors@ authors@inspirehepNOSPAMPLEASE.net
feedback@ feedback@inspirehepNOSPAMPLEASE.net
help@ help@inspirehepNOSPAMPLEASE.net
inspire@ inspire@inspirehepNOSPAMPLEASE.net
rt-comment@ rt-comment@inspirehepNOSPAMPLEASE.net
support@ support@inspirehepNOSPAMPLEASE.net
On inspirehep.net:

admin@ inspire-support@cernNOSPAMPLEASE.ch
authors@ inspire-support@cernNOSPAMPLEASE.ch
conf@ inspire-support@cernNOSPAMPLEASE.ch
experiments@ inspire-support@cernNOSPAMPLEASE.ch
feedback@ inspire-support@cernNOSPAMPLEASE.ch
help@ inspire-support@cernNOSPAMPLEASE.ch
hepnames@ inspire-support@cernNOSPAMPLEASE.ch
inspire@ inspire-support@cernNOSPAMPLEASE.ch
inst@ inspire-support@cernNOSPAMPLEASE.ch
jobs@ inspire-support@cernNOSPAMPLEASE.ch
rt-comment@ inspire-support@cernNOSPAMPLEASE.ch
HEP_ref_user@ inspire-support@cernNOSPAMPLEASE.ch
support@ inspire-support@cernNOSPAMPLEASE.ch
On inspirehep.org

admin@ admin@inspirehepNOSPAMPLEASE.net
authors@ authors@inspirehepNOSPAMPLEASE.net
feedback@ feedback@inspirehepNOSPAMPLEASE.net
help@ help@inspirehepNOSPAMPLEASE.net
On inspirebeta.net

admin@ inspire-support@cernNOSPAMPLEASE.ch
authors@ inspire-support@cernNOSPAMPLEASE.ch
feedback@ inspire-support@cernNOSPAMPLEASE.ch
help@ inspire-support@cernNOSPAMPLEASE.ch
hiring@ salvatore.mele@cernNOSPAMPLEASE.ch

leftover SLAC emails

There are four active email addresses at slac where tickets can come in and hit queues. These are

conf@slac
inst@slac
hepnames@slac
expwork@slac
only hepnames has a web presence, it opens a ticket on submission of the hepnames additions/updates. The other two might get some traffic from Arsella at SLAC, who is modifying SLAC publications in Spires, a few of which will have information merged into Inspire. Experiments has had nothing for some time.

Each of those email addresses has a directory with a .procmailrc file that directs the email to Inspirert via http.

/u/li/conf /u/li/hepnames /u/li/inst /u/li/expwork

Procmail logs

located in /opt/rt3/var/procmail/pmlog

-- TravisBrooks - 02-Nov-2009

Edit | Attach | Watch | Print version | History: r28 < r27 < r26 < r25 < r24 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r28 - 2016-12-05 - BernardHecker
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Inspire All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback