Messages containing leading whitespace in the recipient address are
rejected.
Example:
Jan 22 08:32:41 vps10 postfix/smtpd[5937]: NOQUEUE: reject: RCPT from
smtpout.eastlink.ca[24.222.0.30]: 550 5.1.1 soli...@example.com:
Recipient address rejected: User unknown in virtual alias table;
* Doug Robbins drobb...@smartlabrador.ca:
Messages containing leading whitespace in the recipient address are
rejected.
Example:
Jan 22 08:32:41 vps10 postfix/smtpd[5937]: NOQUEUE: reject: RCPT from
smtpout.eastlink.ca[24.222.0.30]: 550 5.1.1 soli...@example.com:
Recipient address
Doug Robbins:
Messages containing leading whitespace in the recipient address are
rejected.
Only if the recipient does not exist.
Example:
Jan 22 08:32:41 vps10 postfix/smtpd[5937]: NOQUEUE: reject: RCPT from
smtpout.eastlink.ca[24.222.0.30]: 550 5.1.1 soli...@example.com:
Recipient
On 22-Jan-2010 10:11 AM, Wietse Venema wrote:
Doug Robbins:
Messages containing leading whitespace in the recipient address are
rejected.
Only if the recipient does not exist.
Example:
Jan 22 08:32:41 vps10 postfix/smtpd[5937]: NOQUEUE: reject: RCPT from
smtpout.eastlink.ca[24.222.0.30]:
On Fri, Jan 22, 2010 at 09:40:58AM -0330, Doug Robbins wrote:
Is there something I can do to avoid these rejections (other than
the obvious -- get dba...@example2.com to fix his address book)?
A milter could remove recipients with spaces and add back ones without
spaces. To do it completely
On Fri, Jan 22, 2010 at 02:13:17PM +0100, Ralf Hildebrandt wrote:
Is there something I can do to avoid these rejections (other than the
obvious -- get dba...@example2.com to fix his address book)?
Hm, you could try and alias soli...@example.com to
soli...@example.com
But how???
The
* Victor Duchovni victor.ducho...@morganstanley.com:
This said, far better to just reject this, and let the sender correct
their address list.
Yes.
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Victor Duchovni:
On Fri, Jan 22, 2010 at 02:13:17PM +0100, Ralf Hildebrandt wrote:
Is there something I can do to avoid these rejections (other than the
obvious -- get dba...@example2.com to fix his address book)?
Hm, you could try and alias soli...@example.com to
On Fri, Jan 22, 2010 at 09:16:07AM -0500, Wietse Venema wrote:
The lookup keys and RHS values for virtual(5) are in rfc822 format.
A PCRE table can take care of this:
Virtual alias lookups are done in the unquoted form, while
canonical map lookups are in quoted form.
No, the cleanup(8)
Victor Duchovni:
On Fri, Jan 22, 2010 at 09:16:07AM -0500, Wietse Venema wrote:
The lookup keys and RHS values for virtual(5) are in rfc822 format.
A PCRE table can take care of this:
Virtual alias lookups are done in the unquoted form, while
canonical map lookups are in quoted
On Fri, Jan 22, 2010 at 10:33:58AM -0500, Wietse Venema wrote:
One could argue that the SMTP server should use the external form of the
recipient for these lookup, to match downstream behaviour in cleanup(8)...
Indeed. There was no address validation in the initial design and
11 matches
Mail list logo
