Ben Rometsch wrote:
> OK - I have fixed the issue of the whitelist file not being written
> to - I needed to change the permissions of the ASSP directory itself.
> Now the whitelist is added to when I send an email to a contact that
> is not currently in the whitelist.
>
> However the email interface is still not working. If I send an email
> to my whitelist address with the address to be whitelisted in the
> body of the email nothing happens. I see this in the logs:
>
> Jul-5-07 13:34:39 Connected: 87.194.120.42:53723 -> 85.118.234.21:25
> -> 127.0.0.1:10025
> Jul-5-07 13:34:39 87.194.120.42 <[EMAIL PROTECTED]> email
> whitelist addition
> Jul-5-07 13:34:39 87.194.120.42 <> is disconnected
Here's an old thread about this issue; maybe you have the same problem
that
I did:
Kevin wrote:
> Dave Emory wrote:
>> Dave Emory wrote:
>>> Version 1.3.0 has these lines in the log when it receives a
>>> whitelist addition message:
>>>
>>> May-20-07 12:30:58 Connected: 192.168.0.6:2210 -> 192.168.0.5:25 ->
>>> 192.168.0.1:25
>>> May-20-07 12:30:59 192.168.0.6 <[EMAIL PROTECTED]> email whitelist
>>> addition May-20-07 12:30:59 Email whitelist addition:
>>> [EMAIL PROTECTED]
>>> May-20-07 12:30:59 192.168.0.6 <> is disconnected
>>>
>>> Version 1.3.2(52) just has these lines, and the address was never
>>> added to the whitelist:
>>>
>>> May-20-07 13:24:21 Connected: 192.168.0.6:2276 -> 192.168.0.5:25 ->
>>> 192.168.0.1:25
>>> May-20-07 13:24:21 192.168.0.6 <[EMAIL PROTECTED]> email whitelist
>>> addition May-20-07 13:24:21 192.168.0.6 <> is disconnected
>>
>> I found the solution.
>
> Care to share it with the rest of the class?
>
> Kevin
Sure 8-). I had an obsolete URIBLCCTLDS.txt file from some past
installation. Sometime after the 1.3.0 release, code was added to use
the
contents of the file to verify that the whitelist (and maybe other
lists)
had valid domains. The invalid file didn't have one-level names (com,
org,
etc.) in it, thus adding [EMAIL PROTECTED] did not actually add the
address
to the whitelist. The code doesn't write a log line when this happens.
It
does send an email saying the whitelist addition was completed.
I got the current file from Fritz's site, and all is well. It took a
while
to figure this out because I had two URIBLCCTLDS.txt files in different
paths. The one that was not being read would have worked because it had
the
one-level domains names in it. Stuff like that happens when the
directory
structure changes and manual intervention is required to fix it.
Dave
-----------
Hmmm - that didn't help. Is there any way I can get some more logging
out of the application in this area?
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
