Hello,

What does the following error mean wrt AR set on one account as a result of which incoming.pl terminates

Config file '/path/to/data/users/domain.com/s/sales/.autoreplied' did not return a hash reference. at ./incoming.pl line 976.

Not sure how many users have AR configured but got complain from few users that mails were not being delivered and on running ./incoming.pl found the above error. How to correct this?



CEHCKING THE .autoreplied file found this content which is not the content posted and see in user front end:

\-> less .autoreplied
{
'bison Content-Transfer-Encoding: 8bit Syrup:
e5280ef4837e3ce9c02c71730d34105c Content-Type: text/plain X-Mailer:
Ximian Evolution 1.0.4 Subject: he area concerned to:
williampecor@starpower.net to: fredg333@sbcglobal.net to:
dinotto2@aol.com to: floridaprincess@att.net to:
ikeogut@awc-carriers.com to: plettlm@sbcglobal.net slaughter storage
temperature for the meat are all specified. he ham produced within
these criteria is given the uropean nion status rotected esignation of
rigin and as such is called ayonne am. nforcement of these regulations
and .' => '1161585303'
};

# vim:syn=perl:ts=4:noet



No amount of editing removes that text. How could this be possible?

Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================

ok .autoreplied is for tracking replies sent? If yes then what is writing that content to the file as noted above for the said account.? Server is definitely not hacked and the ownership of the file is ok.

Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================

It should be a hash of e-mail to unixtime, but it looks like in that case, the e-mail address was pulled in incorrectly. However, if the file is as shown, Perl still should be able to parse it fine, but it looks like it's a parsing bug with Perl. To fix it, you'll have to delete the .autoreplied file, and make the following change to GT/Config.pm (around line 248):
(delete the var line).

Adrian

Hi,

Is the suggested correction in the following:

# Print actual data:
my $dump = GT::Dumper->dump(
var => '',
data => \%data,
sort => 1,
$att->{sort_order} ? (order => $att->{sort_order}) : (),
tab => $att->{tab}
);

We are on perl 5.8.8

I ma presuming no other .autorespond file is having that sort of data as repeated runs of .incoming.pl after emptying out the file which caused problems there are no issues seen.

A company in Europe, sent us IMATE Jam just for doing BUG Testing ;-)

Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================

Yes, that is where it should be changed. The parse problem that caused the problem should be pretty rare, so you probably won't have very many broken .autorespond files.

Adrian