From: Prateek Sadhukhan <psadhukhan@hss.hns.com>
Subject: sender domain must exist...
Date: Fri, 29 Oct 1999 11:27:46 +0000 (IST) [thread overview]
Message-ID: <Pine.LNX.4.10.9910291125090.801-100000@psadhukhan.hss.hns.com> (raw)
Hi all,
when i try to send mails to some addresses it bounces saying "sender
domain must exist".
if i try to send it using pine it seems to go thru.
I am behind a firewall. my company domain is hss.hns.com, while my
machine is psadhukhan.hss.hns.com. Its seems to me that when the
receiver of the mail tries to authenticate the domain, it tries to
find the domain psadhukhan.hss.hns.com which being behind the firewall
is not visible to it. But then this should be a problem with any mails
send from my box whether i use gnus or pine.
Also most mails are going thru only a few addresses are creating this
problem. Please help.
thanks in advance,
regards
prateek
next reply other threads:[~1999-10-29 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-29 11:27 Prateek Sadhukhan [this message]
1999-10-29 5:56 ` Norbert Koch
1999-11-14 19:37 ` Greg Stark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.10.9910291125090.801-100000@psadhukhan.hss.hns.com \
--to=psadhukhan@hss.hns.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).