Como continuación deesta pregunta, investigué un poco más y encontréesta respuesta en SuperUserlo que parece haber resuelto mi problema de que sendmail no pudiera escribir un archivo en particular. Específicamente, detener sendmail, verificar los procesos en curso, eliminarlos y luego reiniciar sendmail solucionó esa parte de mi problema.
Como prueba, intenté enviarme otro correo electrónico desde la línea de comando: . El correo electrónico no se envió correctamente, peroecho "Subject: sendmail test" | sudo sendmail /usr/sbin/sendmail -v [email protected]hizoRecibe un correo electrónico devuelto del propio sendmail con los errores:
From MAILER-DAEMON Tue Jul 23 12:44:30 2019
Return-Path: <MAILER-DAEMON>
Received: from major-productions.com (localhost [127.0.0.1])
by major-productions.com (8.15.2/8.15.2/Debian-12) with ESMTP id x6NGiUQO012820
for <[email protected]>; Tue, 23 Jul 2019 12:44:30 -0400
Received: from localhost (localhost)
by major-productions.com (8.15.2/8.15.2/Submit) id x6NGiUSL012819;
Tue, 23 Jul 2019 12:44:30 -0400
Date: Tue, 23 Jul 2019 12:44:30 -0400
From: Mail Delivery Subsystem <MAILER-DAEMON@debian>
Message-Id: <[email protected]>
To: [email protected]
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="x6NGiUSL012819.1563900270/major-productions.com"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message
--x6NGiUSL012819.1563900270/major-productions.com
The original message was received at Tue, 23 Jul 2019 12:44:30 -0400
from root@localhost
----- The following addresses had permanent fatal errors -----
/usr/sbin/sendmail
(reason: 550 5.7.1 </usr/sbin/[email protected]>... Cannot mail directly to files)
(expanded from: /usr/sbin/sendmail)
-v
(reason: 550 5.1.1 <[email protected]>... User unknown)
(expanded from: -v)
----- Transcript of session follows -----
... while talking to [127.0.0.1]:
>>> DATA
<<< 550 5.1.1 <[email protected]>... User unknown
550 5.1.1 -v... User unknown
<<< 550 5.7.1 </usr/sbin/[email protected]>... Cannot mail directly to files
550 5.1.1 /usr/sbin/sendmail... User unknown
--x6NGiUSL012819.1563900270/major-productions.com
Content-Type: message/delivery-status
Reporting-MTA: dns; major-productions.com
Arrival-Date: Tue, 23 Jul 2019 12:44:30 -0400
Final-Recipient: RFC822; /usr/sbin/[email protected]
Action: failed
Status: 5.7.1
Remote-MTA: DNS; [127.0.0.1]
Diagnostic-Code: SMTP; 550 5.7.1 </usr/sbin/[email protected]>... Cannot mail directly to files
Last-Attempt-Date: Tue, 23 Jul 2019 12:44:30 -0400
Final-Recipient: RFC822; [email protected]
Action: failed
Status: 5.1.1
Remote-MTA: DNS; [127.0.0.1]
Diagnostic-Code: SMTP; 550 5.1.1 <[email protected]>... User unknown
Last-Attempt-Date: Tue, 23 Jul 2019 12:44:30 -0400
--x6NGiUSL012819.1563900270/major-productions.com
Content-Type: message/rfc822
Return-Path: <me>
Received: (from root@localhost)
by major-productions.com (8.15.2/8.15.2/Submit) id x6NGiUSK012819;
Tue, 23 Jul 2019 12:44:30 -0400
Date: Tue, 23 Jul 2019 12:44:30 -0400
From: Dude Guy <me>
Message-Id: <[email protected]>
Subject: sendmail test
--x6NGiUSL012819.1563900270/major-productions.com--
Supongo que es un error de configuración, pero no tengo idea de dónde buscar ni qué cambiar.
Respuesta1
Llamó a sendmail, pero le dijo que quería entregar el correo a /usr/sbin/sendmail, luego -vy luego [email protected]. Sólo parece que se ha enviado el último correo electrónico; los otros dos obviamente rebotaron.
No está claro por qué escribiste la línea de comando de esa manera, pero supongo que es simplemente un error. Deberías haber escrito o algo similar.sendmail -v [email protected]