Briefly, how do the Messaging
Connector and Access Unit Operate?
1. The connector submits all messages
in the OUT queue $WTSPOOL/gateways/<gwid>out.
2. It picks up "max-msg-in" (default
50) messages from the X.400 (oq) and creates files
(1 per message) in the IN ($WTSPOOL/gateways/<gwid>/in
directory.
3. It then creates a handshake
file (1.cmp) for the Access Unit.
4. The Access Unit checks for
this file and, if found, downloads messages from
the server (should never be more than the max-msg-in)
and uploads messages to the OUT directory on the
connector.
5. The Access Unit then creates
a handshake file (2.wup) on the server for the connector
to recognize and process messages.
Back to top
What is the boot.req file?
The boot.req file is a zero byte
flag file created by the Access Unit to be transferred
to the connector's gateways directory $WTSPOOL/gateways/
to request a copy of the connector's configuration
file $WTROOT/conf/<gwid>/<gwid>.cfg.
When the connector sees the boot.req, it makes a copy
of its configuration file and stores it at the gateways
directory to be FTP'd over to the Access Unit. The
connector then removes the boot.req file.
Back to top
What does the mail.log warning
message "Could not find the filenames of the attachments
in IMS. Cannot preserve the filenames. Current filename
is /usr/spool/*****" mean?
One way NetJunction can find out
about the type of file is by the file's extension.
If the extension is not a well known (such as .doc.xls,
etc.) extension, then NetJunction may not be able
to preserve the filename on the destination. NetJunction
displays a warning in the log file. You can safely
ignore the warning, or advise users to use well known
extensions. Please read File/Attachment Handling
in the Core and Messaging Services manual for
more information on attachment handling.
Back to top
Can NetJunction interface with
two X.400 providers at the same time?
No.
Back to top
What should
I do when files build up in wt/wtspool/gateways/<gwid>/work
directory?
Under certain circumstances, mainly
nondeliverable messages, and certain processing points,
files in the work directory do get "stranded". The
work directory is used to deal with temporary message
building and breakdown. In most cases, what you see
in the work directory are the file attachments that
go with the messages that are being processed. In
the case of the files that are left in the work directory,
you can safely delete them. Try to remove things that
are not current or close to current, as these may
be things the system is currently working on. Removing
things that are more than a day old is definitely
safe.
Back to top
Do I need to shutdown Sendmail
before upgrading the NetJunction Server?
Yes.
Back to top
How can I capture a message from
the Sendmail "mqueue"?
One way to do this would be to change
Sendmail delivery mode from "background" to "queue"
in the sendmail.cf file. This will queue messages
for later delivery and give you time to make a copy
of the appropriate "qf" and "df" files.
1. cd /etc/mail
2. vi sendmail.cf
3. change the "O DeliveryMode=background"
to "O DeliveryMode=Queue"
4. Stop and start sendmail for this
configuration to take effect.
Back to top
Where did the g* files in the ~X.400/tmp
directory come from?
Hewlett Packard has identified a
problem where FTBP attachments can result in files
being left in the ~X.400/tmp directory, i.e. for each
FTBP one temporary 'g' file will be created that may
not be removed after processing has completed. The
workaround for this problem is simply to schedule
a cron job that clears up 'g' files in the ~x400/tmp
directory that are old. For example, more than a day
old.
Back to top
|