We have had a 575 for just over a year and its been fine but two days ago emails stopped sending. After narrowing down the problem to larger files and monitoring the SMTP gateway we found that the printer is closing the connection before probably sending the message. I have no idea why this is happening and upgraded the firmware to the latest to hopefully resolve it 2302243_421976.
Small 75 dpi B&W pdf that is SUCCESFUL (failure below this):
> Successful Connection
> ====================
>
> 14:45:26.37 5 SMTP connection request from [69.74.75.18:1077],
> socket=11
> 14:45:26.37 4 SMTPI-07055([69.74.75.18]) got connection on
> [69.60.11.122:25]
> 14:45:26.37 5 SMTPI-07055([69.74.75.18]) out: 220 terminate.net ESMTP
> CommuniGate Pro 4.2.8 is glad to see you!\r\n
> 14:45:26.39 5 SMTPI-07055([69.74.75.18]) inp: EHLO wince
> 14:45:26.39 5 SMTPI-07055([69.74.75.18]) out: 250-terminate.net we
> trust you
> wince\r\n250-HELP\r\n250-PIPELINING\r\n250-ETRN\r\n250-DSN\r\n250-TURN
> \r\n250-ATRN\r\n250-SIZE
> 31457280\r\n250-STARTTLS\r\n250 EHLO\r\n
> 14:45:26.41 5 SMTPI-07055([69.74.75.18]) inp: MAIL
> FROM:<scanner@xxxx.xxx>
> 14:45:26.41 5 SMTPI-07055([69.74.75.18]) out: 250
> scanner@xxxx,xxx sender accepted\r\n
> 14:45:26.42 5 SMTPI-07055([69.74.75.18]) inp: RCPT
> TO:<person@xxxx.xxxx> NOTIFY=FAILURE
> 14:45:26.42 5 SMTPI-07055([69.74.75.18]) out: 250
> person@xxxx.xxxx will relay mail from a client
> address\r\n
> 14:45:26.43 5 SMTPI-07055([69.74.75.18]) inp: DATA
> 14:45:26.43 5 SMTPI-07055([69.74.75.18]) out: 354 Enter mail, end with
> "." on a line by itself\r\n
> 14:45:39.00 5 SMTP stream thread finished
> 14:45:40.00 5 SMTP stream thread finished
> 14:45:43.63 2 SMTPI-07055([69.74.75.18]) [3611641] received, 14134
> bytes
> 14:45:43.63 5 SMTPI-07055([69.74.75.18]) out: 250 3611641 message
> accepted for delivery\r\n
> 14:45:43.63 2 QUEUE([3611641]) from <scanner@xxxx.xxx>, 14134
> bytes
> (<1e5883ea5aba9c57110cb98ad229f103@wince>)
> 14:45:43.63 4 SMTP(marinuscap.com) record created
> 14:45:43.64 4 SMTP(marinuscap.com) [3611641] enqueueing (new)
> 14:45:43.64 5 SMTP waiting: marinuscap.com active:
> 14:45:43.64 5 SMTP(marinuscap.com) ready in queue
> 14:45:43.64 2 ENQUEUER-01([3611641]) enqueued
> 14:45:43.64 5 SMTP waiting: active: marinuscap.com
> 14:45:43.64 4 SMTP queue is empty
> 14:45:43.64 4 SMTP sending to marinuscap.com
> 14:45:43.64 5 SMTP new VStream created, n=1
> 14:45:43.64 5 SMTP waiting(get): active: marinuscap.com
> 14:45:43.64 5 SMTP stream thread started
> 14:45:43.64 4 SMTP queue is empty
> 14:45:43.64 5 SMTP-00703() started
> 14:45:43.64 5 SMTP-00703(marinuscap.com) processing
> 14:45:43.67 5 SMTPI-07055([69.74.75.18]) inp: QUIT
> 14:45:43.67 5 SMTPI-07055([69.74.75.18]) out: 221 terminate.net
> CommuniGate Pro SMTP closing connection\r\n
> 14:45:43.67 4 SMTPI-07055([69.74.75.18]) closing connection
> 14:45:43.67 4 SMTPI-07055([69.74.75.18]) releasing stream
Below is a FAILED connection
> Failed connection
> =================
>
> 14:42:05.86 5 SMTP connection request from [69.74.75.18:1075],
> socket=12
> 14:42:05.86 5 SMTP new VStream created, n=2
> 14:42:05.86 5 SMTP stream thread started
> 14:42:05.86 4 SMTPI-07042([69.74.75.18]) got connection on
> [69.60.11.122:25]
> 14:42:05.86 5 SMTPI-07042([69.74.75.18]) out: 220 terminate.net ESMTP
> CommuniGate Pro 4.2.8 is glad to see you!\r\n
> 14:42:05.88 5 SMTPI-07042([69.74.75.18]) inp: EHLO WinCE
> 14:42:05.88 5 SMTPI-07042([69.74.75.18]) out: 250-terminate.net we
> trust you
> WinCE\r\n250-HELP\r\n250-PIPELINING\r\n250-ETRN\r\n250-DSN\r\n250-TURN
> \r\n250-ATRN\r\n250-SIZE
> 31457280\r\n250-STARTTLS\r\n250 EHLO\r\n
> 14:42:05.89 3 SMTPI-07042([69.74.75.18]) read failed. Error
> Code=connection closed by peer
> 14:42:05.89 4 SMTPI-07042([69.74.75.18]) closing connection
> 14:42:05.89 4 SMTPI-07042([69.74.75.18]) releasing stream
> 14:42:20.00 5 SMTP stream thread finished
>