OK - fair point that many users won't understand / care and either do nothing or get it wrong!! However, it was the instructions at http://assp.sourceforge.net/fom/cache/14.html that partly attracted me to ASSP!

I also see the point about validating addresses in ASSP to save loading the server.

But this relative newbie still doesn't see why ASSP sees [EMAIL PROTECTED] but not [EMAIL PROTECTED]

Depending on validation, ASSP either says no such user as [EMAIL PROTECTED] and rejects it, or passes it to hMail flagged as spam (as I'm running under test)

I'm confused!!!

Thanks to Charles Marcus, Andrew Porter & Fritz Borgstedt for responses to thread.

Cheers,

Eddie

Charles Marcus wrote: (& tx to Andrew Porter & Fritz Borgstedt as well)
A shame as having users able to report is all that is needed to allow a 'go live' - I just can't switch on ASSP on the live server until I can solve this one.

Personally, I would never let ALL of my users manage the corpus. I always designate either just myself, or one or a few users that are both knowledgeable enough - and *care* enough - to do it right.

-------------------
I installed ASSP 1.2.6 alongside hMail 4.3-B248on a test email server prior to using it 'live' - it's running as a Service on W2K using Perl v5.8.8 I set it up initially for a single domain and seem to have everything working just fine. I then added a second domain, which again seems to be working just fine, apart from the problem below. In 'Relaying' I have set 'Local Domains' to 'file:LocalDomains.txt' which contains 2 lines - 'domain1.tld','domain2.tld' In 'Validate Local Addresses' I have set 'Local Addresses' to 'file:LocalAddresses.txt' which also contains 2 lines - '@domain1.tld','@domain2.tld' In 'Email Interface' I have set 'From Address for Reports' to '<[EMAIL PROTECTED]>' Apart from checking all of the 'Test' boxes the rest pretty well is as per the install defaults, only tweaked for the actual file locations. Now, if [EMAIL PROTECTED] forwards a spam email to '[EMAIL PROTECTED]' it all works a treat. However, if '[EMAIL PROTECTED]' forwards a spam to either '[EMAIL PROTECTED]' or '[EMAIL PROTECTED]' the email is treated as a normal email and flagged again as spam - so the email interface is missing it and not accepting it as 'not spam', just passing it straight to hMail. Apologies if this one is in the FAQ/Wiki/help etc - I couldn't find it. Any pointers/help gratefully received! Regards, Eddie

--
What I'm reading on the web: http://del.icio.us/stuarte

Eddie Stuart

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to