[rt-users] Adding CC / BCC to Ticket Reply causes 533 LIST error from sendmail

Paul Broadwith paul.broadwith at blueivy.co.uk
Thu Oct 9 03:09:35 EDT 2008 

There is a HUGE warning in RT_Config.pm that you shouldn't edit it but
instead copy sections to the RT_SiteConfig.pm.

I'm still unsure of even what variable or section I should be editing.
Can you give me some pointers?

Kind regards,

Paul Broadwith (MBCS)
Blue Ivy Ltd - Microsoft Small Business Specialist, UK Partner Qualified
for 2008


Tel.: 01955 698203
Windows Messenger: paul.broadwith at blueivy.co.uk
Web: http://www.blueivy.co.uk



-----Original Message-----
From: Jesse Vincent [mailto:jesse at bestpractical.com] 
Sent: 08 October 2008 21:49
To: Paul Broadwith
Cc: RT-Users Users
Subject: Re: [rt-users] Adding CC / BCC to Ticket Reply causes 533 LIST
error from sendmail

[please keep rt-users CCed]
	
On Oct 8, 2008, at 4:29 PM, Paul Broadwith wrote:

> Hi Jesse,
>
> Thanks for emailing me.
>
> Can you be more specific? I have been through the RT_SiteConfig.pm  
> about
> a dozen times today to see if I can figure out where it is and I am  
> none
> the wiser. I have it set to 'sendmailpipe' as per the default.
>

Try RT_Config.pm, not RT_SiteConfig.pm.



> ===
> Set($MailCommand , 'sendmailpipe');
> Set($SendmailArguments , '-oi -t -ODeliveryMode=b -OErrorMode=m
> -f"support at blueivy.co.uk"');
> Set($SendmailBounceArguments , '-f "<support at blueivy.co.uk>"');
> Set($SendmailPath , "/usr/sbin/sendmail");
> ===
>
> Mail does go out and in, it just doesn't when CC or BCC addresses are
> added ...
>
> Kind regards,
>
> Paul Broadwith (MBCS)
> Blue Ivy Ltd - Microsoft Small Business Specialist, UK Partner  
> Qualified
> for 2008
>
>
> Tel.: 01955 698203
> Windows Messenger: paul.broadwith at blueivy.co.uk
> Web: http://www.blueivy.co.uk
>
>
>
> -----Original Message-----
> From: Jesse Vincent [mailto:jesse at bestpractical.com]
> Sent: 08 October 2008 20:00
> To: Paul Broadwith
> Cc: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Adding CC / BCC to Ticket Reply causes 533  
> LIST
> error from sendmail
>
>
>
>
> On Wed, Oct 08, 2008 at 04:32:23PM +0100, Paul Broadwith wrote:
>> If I click to Reply to a message in an RT Ticket and add either CC,
> BCC
>> or both I get the following message immediately returned (obviously I
>> change some names to protect the guilty - they are in uppercase):
>
> You've misconfigured RT. Have a look in the RT_Config.pm file. You  
> might
> want to look for 'Sendmail'
>
> -jesse
>
>>
>> ===
>> Your message did not reach some or all of the intended recipients.
>>
>>      Subject:	[#51] SUBJECT TEXT
>>      Sent:	08/10/2008 16:28
>>
>> The following recipient(s) cannot be reached:
>>
>>      "553 List:; syntax illegal for recipient
>> addresses"@SERVER.DOMAIN.LOCAL on 08/10/2008 16:28
>>            The format of the e-mail address is incorrect.  Check the
>> address, look up the recipient in the Address Book, or contact the
>> recipient directly to find out the correct address.
>>            < SERVER.DOMAIN.LOCAL #5.1.3>
>> ===
>>
>> I was the Requestor which is why I assume I got the message back. I
>> assume if another customer was the Requestor they would get the
> message
>> back.
>>
>> The /var/log/maillog is:
>>
>> ===
>> Oct  8 16:28:04 SERVER sendmail[11331]: m98FS4jI011331: from=apache,
>> size=1272, class=-60, nrcpts=1,
>> msgid=<rt-3.8.0-9093-1223479684-18.51-7-0 at DOMAIN.co.uk>,
>> relay=apache at localhost
>> Oct  8 16:28:04 SERVER sendmail[11331]: m98FS4jI011331:
> m98FS4jJ011331:
>> DSN: "OtherRecipients of COMPANY Ticket #51":;... List:; syntax
> illegal
>> for recipient addresses
>> ===
>>
>> I don't have the experience with RT to have changed anything other
> than
>> the config file when setting it up. Does anybody have any  
>> suggestions?
>>
>> Kind regards,
>>
>> Paul Broadwith (MBCS)
>> Blue Ivy Ltd - Microsoft Small Business Specialist, UK Partner
> Qualified
>> for 2008
>>
>>
>> Tel.: 01955 698203
>> Windows Messenger: paul.broadwith at blueivy.co.uk
>> Web: http://www.blueivy.co.uk
>>
>>
>>
>> -----Original Message-----
>> From: rt-users-bounces at lists.bestpractical.com
>> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of  
>> Gabriel
>> Cadieux
>> Sent: 08 October 2008 16:06
>> To: Curtis Bruneau; rt-users at lists.bestpractical.com
>> Subject: Re: [rt-users] reall odd apache2 crashes with blank pages
>>
>> ahh, i get you.
>>
>> indeed, the SSL functionality should work flawlessly now, but we
> weren't
>> actually *using* it per se, it was just turned on by default. our RT
>> implementation is internal only, and the mysql database is runs on  
>> the
>> same host as apache, so there's really no need for it.
>>
>> :)
>>
>> -gabe
>>
>> -----Original Message-----
>> From: Curtis Bruneau [mailto:curtisb at vianet.ca]
>> Sent: Wednesday, October 08, 2008 10:03 AM
>> To: Gabriel Cadieux; rt-users at lists.bestpractical.com
>> Subject: Re: [rt-users] reall odd apache2 crashes with blank pages
>>
>>
>> Understood, just saying you should still be able to use SSL without
>> issues with the fixed driver.
>>
>> Gabriel Cadieux wrote:
>>> yes, i understand that, but you have to take into consideration the
>> fact that someone also mentioned disabling SSL altogether slowed  
>> their
>> segfaults, and this is exactly what happened when i tried it as well.
>> before i disabled SSL, i was getting several crashes per day,  
>> around 8
>> or so... constantly. this continued for almost a week. after  
>> disabling
>> it, it went steady for a couple days between each segfault, for about
>> another week, until everything finally turned out fine (so far
> anyways)
>> when i downgraded DBD::mysql.. i haven't seen a segfault in logs  
>> since
>> last friday.
>>>
>>> logic forces me to conclude the problem was not necessarely caused,
>> but most likely exacerbated by the SSL functionality being turned on.
>>>
>>> -gabe
>>>
>>> -----Original Message-----
>>> From: Curtis Bruneau [mailto:curtisb at vianet.ca]
>>> Sent: Wednesday, October 08, 2008 9:45 AM
>>> To: Gabriel Cadieux; rt-users at lists.bestpractical.com
>>> Subject: Re: [rt-users] reall odd apache2 crashes with blank pages
>>>
>>>
>>> I think it's just a bug in DBD:mysql, I had the same issue and it's
> a
>>> well documented problem. I can't see why SSL would have any effect,
>> it's
>>> just a protocol not a driver.
>>>
>>> Gabriel Cadieux wrote:
>>>
>>>> after disabling SSL and downgrading DBD::mysql to 4.00.5 (from the
>> buggy 4.00.7), i am happy to announce that there have been no
> segfaults
>> on our RT server since last friday. i beleive each of these options
> must
>> have been partially responsible for the problem... i will wait  
>> approx.
>> another week and then consider this issue resolved due to the changes
>> applied. i will let you all know how it turns out.
>>>>
>>>> -gabe
>>>>
>>>> -----Original Message-----
>>>> From: d tbsky [mailto:tbskyd at gmail.com]
>>>> Sent: Thursday, October 02, 2008 9:20 PM
>>>> To: Gabriel Cadieux
>>>> Cc: rt-users at lists.bestpractical.com
>>>> Subject: Re: [rt-users] reall odd apache2 crashes with blank pages
>>>>
>>>>
>>>> 2008/9/30 Gabriel Cadieux <gcadieux at securetechnologies.ca>:
>>>>
>>>>
>>>>> it seems i was too quick to assume that my disabling apache's SSL
>> functionality worked to counter this issue;
>>>>>
>>>>> the server just now crapped out AGAIN with the same symptoms: i
>> clicked a link this morning after having a firefox window open on RT
> all
>> night, and was once again greeted with a white page and a nice
> segfault
>> on my tailf console... ;/ it also crashed several more times
> afterwards,
>> every single time i did an F5 to try and refresh.
>>>>>
>>>>> i have just downgraded to DBD::mysql 4.00.5 (from 4.00.7), and
> will
>> report once more in the next few days on the issue.
>>>>>
>>>>> good luck to all affected by this ubiquitous issue.
>>>>>
>>>>>
>>>>>
>>>> disable ssl  slow down the segfault. our rt system runs for 3 days.
>> it
>>>> segfault almost every day before.
>>>> but the problem is still there. i now again wondering about
>> mod_perl..
>>>> _______________________________________________
>>>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>>>>
>>>> Community help: http://wiki.bestpractical.com
>>>> Commercial support: sales at bestpractical.com
>>>>
>>>>
>>>> Discover RT's hidden secrets with RT Essentials from O'Reilly
> Media.
>>>> Buy a copy at http://rtbook.bestpractical.com
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>>
>> Community help: http://wiki.bestpractical.com
>> Commercial support: sales at bestpractical.com
>>
>>
>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
>> Buy a copy at http://rtbook.bestpractical.com
>> _______________________________________________
>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>>
>> Community help: http://wiki.bestpractical.com
>> Commercial support: sales at bestpractical.com
>>
>>
>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
>> Buy a copy at http://rtbook.bestpractical.com
>>
>
> -- 
>
------------------------------------------------------------------------
--------
>
> Blue Ivy Limited is a limited company registered in Scotland.
> Registered company number: SC 221649.
> Registered VAT number: GB 774 8460 88.
> Registered Office: 67 Kelburn Street, Barrhead, Glasgow, G78 1LD
>
> This email and its attachments may be confidential and are intended  
> solely for the use of the individual to whom it is addressed. Any  
> views or opinions expressed are solely those of the author and do  
> not necessarily represent those of ?Blue Ivy Ltd?.
>
> If you are not the intended recipient of this email and its  
> attachments, you must take no action based upon them, nor must you  
> copy or show them to anyone.
>
> Please contact the sender if you believe you have received this  
> email in error.
>
>
------------------------------------------------------------------------
--------
>
> {Blue Ivy Ltd - ICT For Small Businesses}
>

More information about the rt-users mailing list