title: How can a Request Tracker `scrip` insert multiple IP addresses in RT4's new IP Address custom field?
body: <p>RT4 allows for a new CustomField consisting of a validated ipv4 or ipv6 address, and also allows for multiple values.  This allows me to have an "IP Addresses" custom field that has several addresses for a ticket.  </p>
  
  <p>I cannot seem to get a <code>scrip</code> that will accept multiple addresses from an email (or any <code>correspond</code> event for that matter), only one address will be accepted.</p>
  
  <p>The <code>scrip</code> I am using is a custom action that looks like this:</p>
  
  <pre><code>my $Ticket = $self-&gt;TicketObj;
  my $Transaction = $self-&gt;TransactionObj;
  my $body = $Transaction-&gt;Content();
  my $cf = new RT::CustomField($RT::SystemUser);
  my $id;
  my $msg;
  my $queue = 'Testes';
  
  #---IPS
  if($body =~ /X-addresses\:(.*)\n/i){
  my $iplist = $1;
  ($id,$msg) = $cf-&gt;LoadByNameAndQueue (Name=&gt;'addresses', Queue=&gt;$queue);
  ($id,$msg) = $Ticket-&gt;AddCustomFieldValue (Field =&gt; $cf, Value =&gt;$iplist);
  }
  return(1);
  </code></pre>
  
  <p>I'm not opposed to being told I'm going about this the wrong way; present practice for my RT install is to have a web form submit requests, currently that request will have an IP address field that is picked up by a similar <code>scrip</code> (in addition to x-fqdn, x-contact, x-OS, and other information being collected) and I was thinking a comma-seperated list of mixed ipv4,ipv6 could be snarfed in one line and, as long as RT's address parser validated it, we'd be in business.</p>
  
  <p>Any suggestions would be appreciated, except those that direct me to the hideous BestPractical wiki, I have combed through every tumbleweed-ridden page and come up empty.</p>