LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (31 lines)
Print Reply
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Tue, 10 Jan 2006 17:47:54 -0500
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
Content-type:
text/plain; charset=US-ASCII
Subject:
From:
Francoise Becker <[log in to unmask]>
Content-transfer-encoding:
7BIT
In-Reply-To:
<43C39F40.449.160DE2BD@localhost>
MIME-Version:
1.0
Comments:
cc: David Phillips <[log in to unmask]>
I think I've figured it out. The key is here:

Jan 10 20:07:14 shelmerston postfix/smtpd[25950]: 7EC8D73CB9: reject:
RCPT from sv12pub.verizon.net[206.46.252.148]: 550
<owner-saulnachem*XXX**VERIZON*[log in to unmask]>: User
unknown in local recipient table;
from=<[log in to unmask]>
to=<owner-saulnachem*XXX**VERIZON*[log in to unmask]>
proto=SMTP helo=<sv12pub.verizon.net>

Looks like Verizon is using an anti-spam solution that actually tries 
to do an SMTP handshake with the sending server to check if the 
bounce address (aka the RFC821 MAIL FROM address aka the Return-Path: 
address) exists.

So the problem really IS that Postfix on your server is not 
configured to accept probe messages. This means that once the Postfix 
configuration is fixed, the Verizon problem should be too. Postfix is 
outside my area of expertise, so I don't have the final solution for 
you yet, but I think we have found a very likely candidate. 

The question to be answered now is:

How do you tell Postfix to forward all mail for HMSSURPRISE.ORG to 
LISTSERV and let LISTSERV decide how to deal with it?

-- 
Francoise Becker <[log in to unmask]>

Knowledge is just a click away: http://www.lsoft.com/optin.html

ATOM RSS1 RSS2