-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Uncaught Python 2.2.2 Exception (Mon Feb 3 21:47:27 2003):
- -----------------------------------------------------------
Traceback (most recent call last):
File "/usr/local/tmda-0.65/bin/tmda-filter", line 53, in ?
execfile(os.path.join(execdir, 'tmda-rfilter'))
File "/usr/local/tmda-0.65/bin/tmda-rfilter", line 771, in ?
main()
File "/usr/local/tmda-0.65/bin/tmda-rfilter", line 766, in main
do_default_action(default_action, 'action_incoming', bouncetext)
File "/usr/local/tmda-0.65/bin/tmda-rfilter", line 392, in
do_default_action
bouncegen('request')
File "/usr/local/tmda-0.65/bin/tmda-rfilter", line 669, in
bouncegen
send_bounce(bounce_message, mode)
File "/usr/local/tmda-0.65/bin/tmda-rfilter", line 366, in
send_bounce
ar.record()
File "./TMDA/AutoResponse.py", line 223, in record
IOError: [Errno 36] File name too long:
'/home/abc/.tmda/responses/1044308847.23217.simon.waters%40wretched.demon.co.uk%20%20%20%20%20
%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20
[EMAIL PROTECTED]'
I wasn't planning on stopping spam by not being able to deliver
it to the incoming filters ;-)
(NB: I have a copy of the original spam lurking in the Postfix
mailq, I don't think it is needed here though).
What is the right way to handle such rubbish - I'm happy to
bounce or refuse mail at MTA with excessive subject lines - just
what is excessive?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+PvnFGFXfHI9FVgYRAiYRAJ9yU85JxVD3FVyVq8MeGB4R3cODHwCgxmDE
4ZxoPT8i/1G02B0rPwLce7E=
=Wnmh
-----END PGP SIGNATURE-----
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
