On Wed, Oct 23, 2002 at 03:00:43PM +0530, Sandip P Deshmukh wrote:
| hello all!
|
| my troubles with exim seem to be endless!
Actually, I think you're really close. See below.
| now, 192.168.100.1 is ip address of nt server we have here to which i am
| connected. i use the same address in my mozilla as smtp server and it
| works well.
| here is what i got in mainlog in /var/log/exim:
| 2002-10-23 14:21:38 184HEn-00004j-00 <= sandip@deshmukh.work U=sandip
| P=local S=321
| 2002-10-23 14:21:38 184HEn-00004j-00 => sandip <sandip@deshmukh.work>
| D=localuser T=local_delivery
| 2002-10-23 14:21:38 184HEn-00004j-00 Completed
This is good. A test message sent locally (via a pipe) was delivered
to the local user.
| 2002-10-23 14:23:01 Start queue run: pid=353
| 2002-10-23 14:23:01 182s7y-00003y-00 Message is frozen
[...]
Since these messages are frozen, exim isn't going to try doing
anything with them. That's the definition of "frozen". Use
'exim -qff' to force exim to attempt a delivery of the frozen
messages. Then look at the log to see if any problems remain.
Messages are frozen if a really fatal error occurs causing delivery to
be impossible until an admin fixes the problem.
| 2002-10-23 14:27:30 184HKU-000068-00 <= sandip@deshmukh.work U=sandip
| P=local S=317
| 2002-10-23 14:27:30 184HKU-000068-00 => sandip <sandip@deshmukh.work>
| D=localuser T=local_delivery
| 2002-10-23 14:27:30 184HKU-000068-00 Completed
Another successful test like above.
| 2002-10-23 14:28:35 184HLX-00006K-00 <= sandip@deshmukh.work U=sandip
| P=local S=313
| 2002-10-23 14:28:35 184HLX-00006K-00 => deshmukh@zapo.net R=smarthost
| T=remote_smtp H=192.168.100.1 [192.168.100.1]
| 2002-10-23 14:28:35 184HLX-00006K-00 Completed
In this case you tried another test message. You created it the same
way as the others, except this time it wasn't destined for a local
user. exim successfully connected to the smarthost (190.168.100.1)
and it accepted responsibility for the message.
| i do not know what are start queue run
Any mailserver has a queue of messages to process. SMTP is a
store-and-forward system. That means each node in the network
receives the entire data set, stores it locally, then forwards it to
the appropriate destination when the time is right. As a result, exim
needs to perform a "queue run" periodically -- it needs to go through
each message on the queue and decide what to do with it now and then
do it.
| and what messages are frozen.
You can get some more info on the frozen messages by running 'mailq'.
If they aren't too old, then running 'exigrep' on the log files will
show you the error message from the error which caused them to be
frozen. Alternatively, force a delivery attempt and watch the log for
the error message.
| by the way, the first message - sent to sandip@deshmukh.work was
| successfully received.
Good.
| the other one - deshmukh@zapo.net was never received!
As far as exim is concerned it was. The machine whose address is
192.168.100.1 accepted full responsibility to ensure that the message
wsa delivered or that a bounce was returned to the sender. Does the
NT box actually work? Also, you should fix that sender address --
you'll never get a bounce unless it originates on your own machine.
With the eximconfig-generated config, you can fix the sender address
by putting
sandip: Your@Real.Address
in /etc/email-addresses.
| in an earlier attempt, i had tried a few working e-mail addresses and
| the messages were never delivered.
| i have checked if the mail has bounced - it has not. no fresh mail for
| sandip or root on my system.
If you go to the NT box, can you ping "deshmukh.work"? I suspect you
won't be able to, and that's why you can't get bounce messages -- no
machine knows who your machine is!
HTH,
-D
--
After you install Microsoft Windows XP, you have the option to create
user accounts. If you create user accounts, by default, they will have
an account type of administrator with no password.
-- bugtraq
http://dman.ddts.net/~dman/
Attachment:
pgpar112t_3mo.pgp
Description: PGP signature