Bug 7243 - warn: archive-iterator: no access to start: No such file or directory at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/ArchiveIterator.pm
Summary: warn: archive-iterator: no access to start: No such file or directory at /usr...
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Learner (show other bugs)
Version: 3.4.1
Hardware: PC Linux
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-07 03:47 UTC by danieltw
Modified: 2018-02-04 16:37 UTC (History)
3 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description danieltw 2015-09-07 03:47:32 UTC 
I installed Spamassassin 3.4.1 in my linux server, when I run spamassassin start and it shows error as below:
Sep  7 11:09:54.925 [10713] warn: archive-iterator: no access to start: No such file or directory at /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/ArchiveIterator.pm line 833.
Sep  7 11:09:54.925 [10713] warn: archive-iterator: unable to open start: No such file or directory

I can find ArchiveIterator.pm in directory /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin,what's problem and who can help me?
Comment 1 Mark Martinec 2015-09-07 09:22:36 UTC 
> Sep  7 11:09:54.925 [10713] warn: archive-iterator: no access to start: No
> such file or directory at
> /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/ArchiveIterator.pm line 833.

line 833:
  @s  or warn "archive-iterator: no access to $mail: $!";

ArchiveIterator thinks the name of your mail file is 'start',
but such file does not exist.  Looks like an invocation mistake.
Comment 2 Kevin A. McGrail 2015-09-07 16:44:32 UTC 
Also, after install, did you run sa-update to make sure you have a set of rules?
Comment 3 Giovanni Bechis 2018-02-03 11:23:12 UTC 
Spamassassin is trying to read email message named "start", I think this is an invocation error and not a bug.
Comment 4 Bill Cole 2018-02-04 16:37:54 UTC 
Running the command "spamassassin start" is not how one starts the SpamAssassin daemon (spamd.) How one does that varies by platform, but on various versions of Linux may be one of these:

/etc/init.d/spamassassin start
/etc/rc.d/spamassassin start
systemctl start spamassassin