I'm running fetchmail-6.3.2_1  on 4.10-STABLE

My fetchmailrc file is:

set postmaster "postmaster"
set bouncemail
set no spambounce
set properties ""

poll 10.229.66.116 with proto POP3
       user 'myid' there with password 'mypwd' is 'myid' here

Fetchmail has been running perfectly until just the other day, for literally several years,
with upgrades along the way. I haven't upgraded anything recently or crashed.

I've tried to reinstall fetchmail but no luck there. Googling is not finding anything yet. I have another
FBSD box running 4.10 stable with the same version of fetchmail and it's fine.

I'm stumped.

Thanks,
Jim


At 5:07 PM -0800 2/21/06, Rob wrote:
Jim wrote:
 spike# fetchmail -v
 fetchmail: WARNING: Running as root is discouraged.
 fetchmail: removing stale lockfile
 fetchmail: 6.3.2 querying 10.229.66.116 (protocol
 POP3) at Tue Feb 21
 16:38:52 2006: poll started
 Segmentation fault (core dumped)

 Not sure what I can do to fix this. Any pointers
 greatly appreciated.

What version of FreeBSD do you use?
I have fetchmail-6.3.2_1 installed on a 6-Stable PC.
No problems.

Does your rc file have the proper syntax?
This is mine:

# fetchmailrc
set invisible
set postmaster "postmaster"
set no bouncemail
set no spambounce
set properties ""
set daemon 30
poll localhost with proto IMAP port 22143
  user 'myid' there with password 'mypasswd' is \
       'myid' here options fetchall
folder INBOX.MYMAILBOX

Ah, note that I make use of an ssh-tunnel from
localhost port 22143 to port 143 on the imap server.
You may want to replace 'localhost' and 22143 by
your appropriate settings.
However, remember that pop3 and imap is too
insecure when not using encryption!

Regards,
Rob.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com


_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to