Re: [vps-mail] Sendmail - going from spammers.db to access.db

[Marjolein Katsma <tfyj8lv02@xxxxxxxxxxxxxx>]

At 12:23 2003-11-23, SikaSpam wrote:

>If you want to join us in authentic geekdom, look at the file ont he server with something like

Here's what I did before I saw your post:
- created and edited the file in UltraEdit; this not only supports Unix line endings, but I've set it to create files in that mode by default
- I worked in it with the setting to show me all "hidden" (i.e. whitespace) charatcers: I can see spaces, tabs and newlines each as a separate character
- I made sure the file was saved with no trailing spaces
- after the error message I looked at that (empty) line in UltraEdit and verified that it is, indeed, empty: it consists of nothing but a newline following the newline of the previous line
- I searched the whole file for leading spaces (using a POSIX RE) - none exist (again verfied by viewing with whitespace characters shown)
- I looked at the file in hex mode (in UE as well as with another hex-capable viewer) and verified that 1) line endings are indeed Unix (0a) and 2) the empty line is indeed empty (0a0a) (all empty lines are like that)
- my FTP clients are all set to transmit all files as "binary" to ensure that no conversion at all takes place, ever, when uploading or downloading; what's Unix line endings on my PC, ends up as Unix on the server, and vice versa.

It seems to me that what you are suggesting I do is in essence what I've already done: verify that line endings are Unix, and that an empty line is indeed an empty line...

I'm plenty geeky already, except my geekdom stems from mainframes with various OSs, assembler languages, DOS, Windows (to name just a tiny few in my IT history) - just not Unix. I wouldn't mind learning a bit more though :)

What's od, and what is the parameter -mx?
What's tail?

Meanwhile, looking yet again (I know you can get blind to your own code), I did notice a few other things:
- some error strings had a tab where a space was intended (should not matter, but...)
- one line (257, starting with tabs, not space!) had an ERROR:"" message without a domain before it (line 257 is nowhere near line 218, of course)
So let's see what fixing those does...

...

Bingo!

My guess is that the leading TABS on line 257 actually were the problem; but that's not the same as a leading SPACE on line 218, now is it? An error message that gives the wrong diagnostic for the wrong line isn't very helpful. Feels to me like there's a little buglet lurking in there.

Still, I'm glad that's out of the way. I hate it when a program tells me something is wrong that isn't. Especially when there is actually something else wrong! ;-)


-- 
Marjolein Katsma

======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
======================================================================