From: "Mehul N. Sanghvi" <mehul.sanghvi@gmail.com>
To: mlmmj@mlmmj.org
Subject: Re: virtual domain support
Date: Fri, 08 Jun 2007 10:46:42 +0000 [thread overview]
Message-ID: <46693392.5050006@gmail.com> (raw)
In-Reply-To: <464DAF4C.1030800@gmail.com>
Morten K. Poulsen said the following on 5/31/2007 1:09 PM:
> Hi Mehul,
>
> "Mehul N. Sanghvi" <mehul.sanghvi@gmail.com> wrote:
>> In trying to send a message to the list I get the following
>> entries in the /var/log/mail.log file:
> [snip]
>> May 30 23:54:51 REAL_HOST postfix/smtpd[17679]: NOQUEUE: reject: RCPT from
>> localhost.localdomain[127.0.0.1]: 504 5.5.2 <REAL_HOST>: Helo command
>> rejected:
>> need fully-qualified hostname; from=<mlmmj-test+bounces-help@VHOST.TLD>
>> to=<USER@VHOST.TLD> proto=SMTP helo=<REAL_HOST>
> [snip]
>> Why is getting rejected ?
>
> Because your host does not know its own FQHN.
>
I wonder how mailman does things then, because my mailing lists work fine in
Mailman on the same system. But Mailman is overkill for what I want to do
>> I would like mlmmj to use the VHOST.TLD in the HELO rather then the
>> REAL_HOST, is that possible ?
>
> No, that is not possible.
>
> Mlmmj asks the operating system - via gethostname() - what its hostname is.
> Then it does a lookup - via gethostbyname() - to get the host's FQHN.
>
> How does your /etc/hosts look?
127.0.0.1 localhost localhost.localdomain
192.168.x.x REAL_HOST
cheers,
mehul
--
Mehul N. Sanghvi
email: mehul.sanghvi@gmail.com
next prev parent reply other threads:[~2007-06-08 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 13:51 virtual domain support Mehul N. Sanghvi
2007-05-18 14:07 ` Christian Laursen
2007-05-31 4:15 ` Mehul N. Sanghvi
2007-05-31 17:09 ` Morten K. Poulsen
2007-06-08 10:46 ` Mehul N. Sanghvi [this message]
2007-06-10 12:55 ` Morten K. Poulsen
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=46693392.5050006@gmail.com \
--to=mehul.sanghvi@gmail.com \
--cc=mlmmj@mlmmj.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.