Yes, it is! Especially when one knows what to search for.
Thanks for your reply. I think the zmmsgtrace command is exactly what I'm looking for. But, for some reason it's not working like I would expect it to.
Code:
[zimbra@server log]$ grep sendername mailbox.log.2008-03-18
2008-03-18 09:31:15,213 INFO [LmtpServer-53965] [ip=XX.XX.XX.XX;] lmtp - Delivering message: size=56954 bytes, nrcpts=1, sender=sendername@domain.com, msgid=<026701c8890d$103ecb30$30bc6190$@com>
[zimbra@server log]$ zmmsgtrace -i '026701c8890d$103ecb30$30bc6190$@com'
Tracing messages
ID 026701c8890d$103ecb30$30bc6190$@com
0 messages found
[zimbra@server log]$ zmmsgtrace -s sender@domain.com -t 20080318
Tracing messages
from sender@domain.com
During 20080318
0 messages found I wondered if there was something wrong with my syntax, so I tried:
Code:
[zimbra@sender log]$ zmmsgtrace -s sender@domain.com
Tracing messages
from sender@domain.com
Message ID '006201c87dc2$5f9a6320$1ecf2960$@com'
sender@domain.com -->
someoneelse@domain2.com
Recipient someoneelse@domain2.com
2008-03-03 23:39:40 - incomingserver.domain.com (xx.xx.xx.xx) --> server
2008-03-03 23:39:41 - server --> 127.0.0.1 (127.0.0.1]:10024) status sent
Message ID '004b01c87edf$7d6c8590$784590b0$@com'
sender@domain.com -->
someoneelse@domain2.com
Recipient someoneelse@domain2.com
2008-03-05 09:40:11 - incomingserver.domain.com (xx.xx.xx.xx) --> server
2008-03-05 09:40:13 - server --> 127.0.0.1 (127.0.0.1]:10024) status sent
2 messages found Am I doing something wrong?