On Mon, Jun 17, 2013 at 1:47 PM, David Blanton <[email protected]> wrote: > maillog is now showing it! > > ossec-server sendmail[2652: XXXXX: to=<##########@txt.att.net>, > ctladdr=<[email protected]> (0,0), delay=00:00:06, > xdelay=00:00:06, mailer=esmtp, pri=120388, relay=mx.cingularme.com. > [209.183.32.63], dns=2.0.0, stat=Sent (Message received: > xxxxxxxxx.0vvr17378.schemailedgegx04.cingularme....@ossec-server.ect.na.companyname.com) > > Unfortunately, it did not get to my phone though. One step closer... >
Check for other related log messages. This might be where the tcpdump would be useful, it would present any possible error messages (I thought the response code would be in the log message, but I don't see it off hand). Once that message is accepted by a remote mail server, there isn't a whole lot you can do. Call their support for help maybe? If they're accepting the messages and silently dropping them, they should be flogged. > -- > > --- > You received this message because you are subscribed to the Google Groups > "ossec-list" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
