I managed to get sendmail sort of working on one of my vbox guest debian vms.
It was kind of rough sledding and still not really working properly. I use a smarthost from fastmail.fm where I have accounts. Finally seems to have gotten the auth working thru access.db. But an odd thing is happening. I've been using mail-x to test things and use a little wrapper script that does this: mailx -v -s "Subject" recipi...@some.com <txt_file The -v allows me to watch the smtp conversation as the mail gets processed. I'm going to post the smtp output shortly but first; a note of what I'm doing here; sending to mail to another domain where I have a shell account and am watching for my incoming tests by tailing the procmail.log. It's kind of a lot of smtp output but not sure what is pertinent to understanding why its leaving a dead litter on my end. I've sprinkled a few notes thru the output. ------- ------- ---=--- ------- ------- OK, here we go. mailx -v -s "TEST "141014_184452" 2xd1 rea...@jtan.com < /tmp/tstmsg.txt rea...@jtan.com,2xd1... Connecting to [127.0.0.1] via relay... 220 2xd1.local.lan ESMTP Sendmail 8.14.4/8.14.4/Debian-8; Tue, 14 Oct 2014 18:44:56 -0400; (No UCE/UBE) logging access from: 2xd1.local.lan(OK)-2xd1.local.lan [127.0.0.1] >>> EHLO 2xd1.local.lan 250-2xd1.local.lan Hello 2xd1.local.lan [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-EXPN 250-VERB 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-AUTH LOGIN PLAIN 250-STARTTLS 250-DELIVERBY 250 HELP >>> VERB 250 2.0.0 Verbose mode >>> STARTTLS 220 2.0.0 Ready to start TLS >>> EHLO 2xd1.local.lan 250-2xd1.local.lan Hello 2xd1.local.lan [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-EXPN 250-VERB 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-AUTH LOGIN PLAIN 250-DELIVERBY 250 HELP >>> VERB 250 2.0.0 Verbose mode >>> MAIL From:<ha...@2xd1.local.lan> SIZE=428 AUTH=ha...@2xd1.local.lan 250 2.1.0 <ha...@2xd1.local.lan>... Sender ok >>> RCPT To:<rea...@jtan.com> >>> RCPT To:<2...@2xd1.local.lan> >>> DATA 250 2.1.5 <rea...@jtan.com>... Recipient ok 550 5.1.1 <2...@2xd1.local.lan>... User unknown 354 Enter mail, end with "." on a line by itself Here the mail content is piped in >>> . 050 <rea...@jtan.com>... Connecting to mail.messagingengine.com. port 587 via relay... 050 220 mail.messagingengine.com ESMTP ready 050 >>> EHLO 2xd1.local.lan 050 250-mail.messagingengine.com 050 250-PIPELINING 050 250-SIZE 71000000 050 250-ENHANCEDSTATUSCODES 050 250-8BITMIME 050 250 STARTTLS 050 >>> STARTTLS 050 220 2.0.0 Start TLS 050 >>> EHLO 2xd1.local.lan 050 250-mail.messagingengine.com 050 250-PIPELINING 050 250-SIZE 71000000 050 250-ENHANCEDSTATUSCODES 050 250-8BITMIME 050 250-AUTH PLAIN LOGIN 050 250 AUTH=PLAIN LOGIN 050 >>> AUTH LOGIN 050 334 VXNlcm5hbWU6 050 >>> aHB1dDNAZmFzdG1haWwuZm0= 050 334 UGFzc3dvcmQ6 050 >>> aW5qeDAyMTc= 050 235 2.0.0 OK 050 >>> MAIL From:<ha...@newsguy.com> SIZE=662 AUTH=<> 050 250 2.1.0 Ok 050 >>> RCPT To:<rea...@jtan.com> 050 >>> DATA 050 250 2.1.5 Ok 050 354 End data with <CR><LF>.<CR><LF> 050 >>> . below jtan.com accepts 050 250 2.0.0 Ok: queued as 72F91C00012 050 <rea...@jtan.com>... Sent (Ok: queued as 72F91C00012) 250 2.0.0 s9EMiuN0027130 Message accepted for delivery Why does it go to a dead letter? rea...@jtan.com... Sent (s9EMiuN0027130 Message accepted for delivery) /home/harry/dead.letter... Saved message in /home/harry/dead.letter the message has showed up on jtan within seconds of mailxing I don't understand what happens here at the end. Closing connection to [127.0.0.1] >>> QUIT 221 2.0.0 2xd1.local.lan closing connection Another second or two pass and the message shows up at jtan.com in the procmail.log of incoming mail. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8738aqb642....@reader.local.lan