Both messages are identical. It is actually an email notification service that comes from our physical access control system. There are options to enter email addresses to send the notifications to. Entering 1 address will return an error, while entering 2 addresses will work. Previously when I was using Exchange, entering just 1 address will work.
I'm aware of the CR/LF problem as I've faced that before. One of our notification services stopped working when we migrated from Exchange to Qmail. It is quite possible that its happening again here. I doubt there is anything wrong on the qmail side. I'll have to investigate further. Regards, Riezal Ross Network Engineer / Project Manager CIS (M) Engineering Division Clipsal Integrated Systems (M) Sdn Bhd Unit 3-2, CP Tower, No. 11, Jalan 16/11, Pusat Dagang Seksyen 16, 46350 Petaling Jaya, Selangor Darul Ehsan, Malaysia. Tel: (+603) 7665 3555 Fax: (+603) 7665 3155 Mobile: 012-6285210 E-mail: [EMAIL PROTECTED] http://www.cisasia.com.my http://www.clipsalportal.com -----Original Message----- From: Jake Vickers [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 8:14 PM To: [email protected] Subject: Re: [qmailtoaster] SMTP logs Riezal Ross wrote: > Above are 2 different log entries in my SMTP log file. For the first > entry, the mail does not get sent to the user. For the second entry, > when there are two recipients - the mail does actually get sent to the > user. I am not sure if it is a mail client error or something in > qmail. The only difference in those two log entries (besides the > number of recipients) is the line/ '@4000000043cc56e33777ab3c > tcpserver: end 16971 status 256'/. I noticed that if the mail is > successfully sent, it shows '/status 0'./ > > Could anyone briefly explain to me what is actually happening? What > does/ status 256/ represent? > I do not know why it exits with a 256. The 256 actually means that it exited with an error code of 1. Maybe they planned for future expansion? Anyway... Is the message the same both times? I've seen something similar with CR/LF problems. Oh, and if you show the logs via tai64nlocal, they'll make more sense: tail /var/log/qmail/smtp/current | tai64nlocal I would also check your spam and clamd logs to see if it maybe got bounced for being spam. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
