[PREVIOUS CHAPTER] [NEXT CHAPTER]

7 Trouble Shooting (around FML itself)

    7.1	FML accepts only user@domain form, denies addr without domain part

    7.2	550 and so on ... in log file

    FML logs error messages from sendmail which messages begin with 4XX or
    5XX. Check log file of FML and sendmail. $DIR/var/log/_smtplog (SMTP
    session log) may be useful.

    7.3	WARNING: UNIX FROM Loop

    Warning against mail loop. This warning occurs if the mail is MAIL
    FROM: $MAINTAINER. IT MUST BE INVALID since it implies the mail comes
    from fml.pl itself. This error may occur when a site runs "sendmail -
    bd -t" (A BIG MISTAKE).

    Also if $MAINTAINER is yourself address and you send e-mail to fml.pl
    on its host, this mechanism works and rejects your mail as mail loop.
    Hence we recommend $MAINTAINER is -admin or -request form. If

    	$NOT_USE_UNIX_FROM_LOOP_CHECK = 1; (default 0)

    this mechanism does not work.

    7.4	Try mci:prog since smtp connections cannot be opened

    FML connects MTA as a delivery system via SMTP connection. If socket()
    or connect() establishment fails, FML executes local programs
    e.g. sendmail and use it. If this log message occurs a lot of times,
    it is better to enforce to run sendmail as a command always not using
    socket connection to sendmail, To do it, set up in config.ph

    	$Envelope{'mci:mailer'} = 'prog';

    In this case fml.pl runs $SENDMAIL as a delivery program.

    	$SENDMAIL (default "/usr/sbin/sendmail")

    7.5	The flock() function is unimplemented ...

    * compilation of perl fails
    * you compiled perl as not using flock()
    * perl cannot emulate flock() on some SYSV?

    If you cannot avoid this, please set

    	$USE_FLOCK = 0;

    in config.ph. FML does not use flock(2) but use link(2) style lock
    algorithm.

    7.6	503 Need RCPT (recipient)

    Check mail headers from the person.

    * header is invalid?
    * cannot extract address part from From: field?

    7.7	fml.pl works well but msend.pl and cron.pl cannot work. Why?

    In some ISP's, a host where user's cron job runs and a host receiving
    in coming mails are different, in addition they are different
    operations systems. This is a special case, so please consult with
    your ISP or administrators of your host.

    7.8	Grammer of msend control file

    *** not translated sine this is in the old age.

    msend.pl understand the following format. Hence if you edit the digest
    control file (active file) by hand, you should write the following
    format.

    	address	m=digest-parameter

    #.FML HEADER
    # NEW FORMAT FOR FURTHER EXTENSION
    # e.g. fukachan@phys r=relayserver m=3u s=skip
    # r= relayserver
    # m= matomeokuri parameter is time and option
    # s= skip. can post from this address but not delivered here.
    #
    # the same obsolete format is compatible with new format and as follows:
    # e.g. fukachan@phys relay-server matome 3u
    #.endFML HEADER
    Elena@Baycity.jp  m=1u

    7.9	Perl understand EUC file as a binary file

    *** Japanese specific problem.

    7.10	Lha or ish is not found

    *	lha or ish not exist
    *	shared library is different
    	Some ISP's provide a user for several hosts with different OS's.
    	So fml.pl and msend.pl works differently.

    7.11	A ML host and a WWW host are different

    If you runs fml.pl on a host but the host file system is different one
    the www server uses, you cannot provide www access. One possible
    solution is to run fml.pl using POP3.

    7.12	Can't locate sys/socket.ph in @INC

    	Can't locate sys/socket.ph in @INC (did you run h2ph?) at ...
    	554 "|/usr/spool/driver/fml"... unknown mailer error 2

    You need to create e.g. /usr/local/lib/perl/sys/socket.ph by running h2ph.

    	% (cd /usr/include; h2ph * sys/*)

    7.13	You should install sys/socket.ph using h2ph.

    Please see the previous session for the reason.

[PREVIOUS CHAPTER] [NEXT CHAPTER]