There is another log file that you haven't mentioned, the incoming SMTP
handler on the LISTSERV(tm) host server. Something on that server is
responsible for receiving inbound SMTP traffic and then placing the
messages in the LISTSERV spool directory.  If the message wasn't placed
in the spool then you will not find any mention of it in the LISTSERV
log file.

You need to identify that incoming SMTP handler and review the log file
it generates, to see what happened around the time of the event in your
message trace.

On 9/12/2014 2:23 PM, F J Kelley wrote:
> This is being sent to two different groups:
>
> Lstsrv-L the Listserv Site Administrator's Forum
>
> Office365 The Office 365 Discussion list.
>
> Perhaps some of you have seen this.
>
> We are using Office 365 for our mail service. Our listserver is R16-2014b.
>
> An administrator on campus posted a note to her department's faculty list.
>
> The message never showed up (she is a subscriber, with REPRO on, she
> would receive a copy of her post). She contacted me.
>
> Here is an edited version of what she sent:
>
>  > From: Department Administrator
>  > Sent: Friday, September 12, 2014 12:17 PM
>  > To: [log in to unmask]
> <mailto:[log in to unmask]>; other_address
>  > Subject: RE: Next Tuesday and Wednesday
>
> Checking the listserver log, there was nothing at that time; in fact, in
> the whole log, there was nothing to the list at all.
>
> I performed a message trace:
>
> [string]$DestinationAddress = "[log in to unmask]"
> [string]$OriginateAddress = "[log in to unmask]"
> #
> Get-MessageTrace -SenderAddress $OriginateAddress -RecipientAddress
> $DestinationAddress -StartDate 09/11/2014 -EndDate 09/13/2014 |
> Get-MessageTraceDetail | FL
> #
>
> The last step is below:
>
> Message Trace ID : 826a084b-bed3-474d-2eb5-08d19cbc2c92
> Message ID :
> <[log in to unmask]>
> Date : 9/12/2014 4:17:29 PM
> Event : SEND
> Action :
> Detail : Message transferred from: To_DefaultOpportunisticTLS
> Data : <root><MEP Name="ConnectorId"
> String="To_DefaultOpportunisticTLS"/><MEP Name="ServerIP"
> String="128.192.1.75"/><MEP Name="RecipientStatus" String="250 2.1.5
> Ok"/></root>
>
> The IP is the UGA Listserver.
>
> So it was delivered to the listserver, but never showed up in the
> listserver log. We had a rash of these problems in mid-summer, suspected
> the culprit was "opportunisticTLS" and had planned to turn that off.
> However, further testing did not confirm a problem with TLS and the
> project was deferred.
>
> Have others seen/encountered this? If so, how did you resolve it?
>
> Thanks,
>
> --Joe Kelley UGA/EITS

############################

To unsubscribe from the LSTSRV-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1