|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: iudicium ferat (sneex_at_bellsouth.net)
Date: Tue Oct 01 2002 - 19:46:21 CDT
It claimed to be
>> Oct 1 16:44:20 suse postfix/smtpd[9975]: connect from
>> pool-141-157-238-64.ny325.east.verizon.net[141.157.238.64]
>
> Did that machine say HELO verizon.net and proceed to talk, or did
> it claim
> to be somewhere else? If it claimed to be someone else, then the HELO
> restriction won't work. A client_access probably will.
>
But I do not see a HELO in the log :/
I will move these to a client access hash; also, what are your
thought about stopping this type of relaying:
Oct 1 19:31:30 suse postfix/smtp[10407]: BB647B0325:
to=<owner-nolist-R742*DGUILER**INSECURITY*-ORG
E.EMAILSERVER14.COM>,
relay=e.emailserver14.com[141.157.238.64], delay=10008,
status=sent (250 Ok, message queued (3349 bytes))
Both the target TO and the RELAY server match. I do not want to
see people connecting to me just to e-mail another server...
(BTW - this particular conversation was somewhat long with many
false steps before it was successful.)
???/Sx ?
-
To unsubscribe, send mail to majordomo
postfix.org with content
(not subject): unsubscribe postfix-users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]