Odd item stuck in SMTP relay queue, wont delete.

Simon,

get the message ID and search the corresponding
files in /var/chroot-smtp/spool/input, delete it
manually!

read you
o|iver

Simon,

get the message ID and search the corresponding
files in /var/chroot-smtp/spool/input, delete it
manually!

read you
o|iver

There is no message ID that I can see.

 1864Qm-0003Fr-00  OK 
  [bounce] -> *** spool format error: size=80 *** 

Is 1864 the ID ?

Hello again,

cd to the given directory and enter

 

code:

---

  rm -f 1864Qm-0003Fr-00* 

---

read you
o|iver

Thanks.

Did that, deleted it.  Refreshed screen and it's gone, now it's back again  [:)]h.

Was there anything that resolved this issue as I've had one in me queue for ages and can't get rid of it.

[ QUOTE ]

 19DUIt-0004EU-00  INTERCEPTED unknown reason 
  [bounce] -> *** spool format error: size=130 *** 


[/ QUOTE ]

but 

[ QUOTE ]

asl:/var/chroot-smtp/spool/input # ls 19DUIt-0004EU-00*
ls: 19DUIt-0004EU-00*: No such file or directory


[/ QUOTE ] 

But I can view it by going to:

https://firewall/showmail.pl?SID=1938606459721&id=19DUIt-0004EU-00

Basically it looks like this:

[ QUOTE ]

--C3w982m44wV4T5G 
Content-Type: text/html; 
Content-Transfer-Encoding: quoted-printable 

 
 
 
 

--C3w982m44wV4T5G 
Content-Type: audio/x-midi; 
name=quotechartnews[1].exe 
Content-Transfer-Encoding: base64 
Content-ID:  

TVqQAAMAAAAEAAAA//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 
AAAAAAAA2AAAAA4fug4AtAnNIbgBTM0hVGhpcyBwcm9ncmFtIGNhbm5vdCBiZSBydW4gaW4g 
RE9TIG1vZGUuDQ0KJAAAAAAAAAAYmX3gXPgTs1z4E7Nc+BOzJ+Qfs1j4E7Pf5B2zT/gTs7Tn 
GbNm+BOzPucAs1X4E7Nc+BKzJfgTs7TnGLNO


[/ QUOTE ]

Any help in getting rid of this little blighter? [:S]
  

I had this problem recently, tried everything, even restoring to factory settings and restoring a backup with no luck (in hindsight I realised I should have exported / imported settings, but I had solved it by then)

After restoring the backup, I logged on locally to the terminal session (same as SSH) and selected 5. Advanced -> 4. Flush Device Reports

Oddly that fixed it for me!