On Fri, Mar 30, 2018 at 12:27:37AM -0700, yangyangyang wrote:
> I have add the client ip into mynetworks, but smtp connection from the
> specified account from the specified device always be lost, after data
> Any one could give me some suggesstion?
Disable verbose logging.
I'm frequently appalled by the low regard you Earthmen have for life.
-- Spock, "The Galileo Seven", stardate 2822.3
>this issues always follow the smtp command "DATA"
>2018-03-28T09:53:25.409198+08:00 localhost postfix/smtpd: >
>unknown[10.100.1.237]: 250 2.1.5 Ok
>2018-03-28T09:53:25.450287+08:00 localhost postfix/smtpd: <
>2018-03-28T09:53:25.450309+08:00 localhost postfix/smtpd: >
>unknown[10.100.1.237]: 354 End data with <CR><LF>.<CR><LF>
>2018-03-28T09:53:25.451396+08:00 localhost postfix/smtpd: smtp_get:
may be a broken client.
being that an external IP I would guess remote mailserver checking validity
of mail addresses at your system.
Matus UHLAR - fantomas, [hidden email] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Linux is like a teepee: no Windows, no Gates and an apache inside...
True, but having verbose logging switched on has clearly led to
The message you are asking about is not intrinsically a problem. It
merely indicates that the SMTP session has no more data to be read and
has been closed. This is something that happens normally at the end of
every SMTP session. It is an event, not an error.
The relevant log message is the last one you quoted:
lost connection after CONNECT from unknown[10.100.1.85]
This is logged normally. It includes all of the details ofthe relevant
context that you need to understand the event.
This indicates that the prospective SMTP client at 10.100.1.85, whose
hostname is unknown, closed an established TCP connection before sending
any SMTP commands. Exactly why that happened can probably only be
diagnosed from the client side. The only oddity about this sort of an
event is that it is coming from a RFC1918 private IP, i.e. within your
own network, rather than from somewhere out on the Internet on the other
side of one or more routers run by total strangers.