|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: RCPT TO:
From: Sergei Laskavy (ls
gambit.msk.su)Date: Wed Oct 11 2000 - 08:04:11 CDT
- Next message: Wietse Venema: "Re: debug smtp"
- Previous message: Matthew Hawkins: "Re: Usermanagement"
- In reply to: Wietse Venema: "Re: postfix/smtp: warning: valid_hostname: invalid character 91(decimal): [168.100.1.4]"
- Reply: Sergei Laskavy: "RCPT TO: <user
[host>"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thank you!
No warning on [<legal.ip.address.here>]
But what if someone uses RCPT TO: <username
[hostname>?
Postfix answers:
<"<user"
[host>]>: bad host/domain syntax: "[host>]"
or
550 <<user
[host>]>: Recipient address rejected: Relay access denied
Also looks little strange :-(
On Tue, Oct 10, 2000 at 01:28:23PM -0400, Wietse Venema wrote:
> Postfix has become stricted with things, and this reveals that
> Postfix as doing DNS lookups for [172.16.0.2], in an effort to
> expand aliases in MAIL FROM and RCPT TO commands. Below is a little
> patch.
>
> Wietse
>
*** ./src/smtp/smtp_unalias.c- Sun Sep 17 21:24:47 2000
--- ./src/smtp/smtp_unalias.c Thu Sep 28 13:06:09 2000
***************
*** 68,73 ****
--- 68,76 ----
VSTRING *fqdn;
char *result;
+ if (*name == '[')
+ return (name);
+
/*
* Initialize the cache on the fly. The smtp client is designed to exit
* after servicing a limited number of requests, so there is no need to
- Next message: Wietse Venema: "Re: debug smtp"
- Previous message: Matthew Hawkins: "Re: Usermanagement"
- In reply to: Wietse Venema: "Re: postfix/smtp: warning: valid_hostname: invalid character 91(decimal): [168.100.1.4]"
- Reply: Sergei Laskavy: "RCPT TO: <user
[host>"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]