Anti-Spam SMTP Proxy Server

Den share Befehl kann ich doch getrst weglassen, oder?

sub syncLoadConfigFile {

    my $RCF;
    
#    share %ConfigSync unless is_shared(%ConfigSync);

Ja klar.




Von:    "Fritz Borgstedt" <fb@...>
An:     "ASSP development mailing list" <assp-test@...>
Datum:  30.08.2010 17:02
Betreff:        [Assp-test] syncLoadConfigFile




Den share Befehl kann ich doch getrst weglassen, oder?

sub syncLoadConfigFile {

    my $RCF;
 
#    share %ConfigSync unless is_shared(%ConfigSync);

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 

speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

Scott MacLean wrote:
> My problem is that my status checker connects, and looks for a preset 
> response. If it sees the response, great. If it doesn't see it, it 
> knows there is a problem. Obviously, I have it connect and look for 
> the response "healthy". However, the response when there is a problem 
> is "unhealthy" - which also contains the word "healthy" - so my 
> status checker thinks things are fine.

Or you could just change your status checker to look for the word 'un',
and act accordingly if it is detected...

-- 

Best regards,

Charles

At 07:05 AM 8/26/2010, Charles Marcus wrote:

>Scott MacLean wrote:
> > My problem is that my status checker connects, and looks for a preset
> > response. If it sees the response, great. If it doesn't see it, it
> > knows there is a problem. Obviously, I have it connect and look for
> > the response "healthy". However, the response when there is a problem
> > is "unhealthy" - which also contains the word "healthy" - so my
> > status checker thinks things are fine.
>
>Or you could just change your status checker to look for the word 'un',
>and act accordingly if it is detected...

That would be great...except the status checker app checks for 
successful connections. It assumes if it DOESN'T see what you tell it 
is a "success" response, that something has gone wrong. There's no 
way to tell it to look for a failure response.

I'll try to make this configurable - but the state (healthy/not healthy) 
is not only used for the output of a status request inside the code. If 
someone would use any word, that is part of the complete status output, 
this could lead in a unexpected behavior of assp. - Let' see.

Thomas




Von:    Scott MacLean <assp@...>
An:     ASSP development mailing list <assp-test@...>
Datum:  26.08.2010 13:51
Betreff:        Re: [Assp-test] Healthy/Unhealthy response request




At 07:05 AM 8/26/2010, Charles Marcus wrote:

>Scott MacLean wrote:
> > My problem is that my status checker connects, and looks for a preset
> > response. If it sees the response, great. If it doesn't see it, it
> > knows there is a problem. Obviously, I have it connect and look for
> > the response "healthy". However, the response when there is a problem
> > is "unhealthy" - which also contains the word "healthy" - so my
> > status checker thinks things are fine.
>
>Or you could just change your status checker to look for the word 'un',
>and act accordingly if it is detected...

That would be great...except the status checker app checks for 
successful connections. It assumes if it DOESN'T see what you tell it 
is a "success" response, that something has gone wrong. There's no 
way to tell it to look for a failure response. 
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 

speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

>I'm wondering if the "Healthy" and "Unhealthy" responses from the 
>stat port could be made configurable?

2.0.2_1.2.03 - has it!

Thomas



Von:    Scott MacLean <assp@...>
An:     ASSP development mailing list <assp-test@...>
Datum:  25.08.2010 17:38
Betreff:        [Assp-test] Healthy/Unhealthy response request




I'm wondering if the "Healthy" and "Unhealthy" responses from the 
stat port could be made configurable? I wouldn't want you to change 
them at this point, as that would break people who have systems set 
up to use those responses now.

My problem is that my status checker connects, and looks for a preset 
response. If it sees the response, great. If it doesn't see it, it 
knows there is a problem. Obviously, I have it connect and look for 
the response "healthy". However, the response when there is a problem 
is "unhealthy" - which also contains the word "healthy" - so my 
status checker thinks things are fine. It would be great to be able 
to change it to "sick" or anything else that doesn't contain 
"healthy". I know it's a minor thing, just hoping it might be added 
in some future version.

Thanks!
------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 

speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

Thanks, Thomas!

At 04:04 AM 8/30/2010, Thomas Eckardt wrote:

> >I'm wondering if the "Healthy" and "Unhealthy" responses from the
> >stat port could be made configurable?
>
>2.0.2_1.2.03 - has it!
>
>Thomas
>
>
>
>Von:    Scott MacLean <assp@...>
>An:     ASSP development mailing list <assp-test@...>
>Datum:  25.08.2010 17:38
>Betreff:        [Assp-test] Healthy/Unhealthy response request
>
>
>
>
>I'm wondering if the "Healthy" and "Unhealthy" responses from the
>stat port could be made configurable? I wouldn't want you to change
>them at this point, as that would break people who have systems set
>up to use those responses now.
>
>My problem is that my status checker connects, and looks for a preset
>response. If it sees the response, great. If it doesn't see it, it
>knows there is a problem. Obviously, I have it connect and look for
>the response "healthy". However, the response when there is a problem
>is "unhealthy" - which also contains the word "healthy" - so my
>status checker thinks things are fine. It would be great to be able
>to change it to "sick" or anything else that doesn't contain
>"healthy". I know it's a minor thing, just hoping it might be added
>in some future version.
>
>Thanks!
>------------------------------------------------------------------------------
>Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
>Be part of this innovative community and reach millions of netbook users
>worldwide. Take advantage of special opportunities to increase revenue and
>
>speed time-to-market. Join now, and jumpstart your future.
>http://p.sf.net/sfu/intel-atom-d2d
>_______________________________________________
>Assp-test mailing list
>Assp-test@...
>https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
>DISCLAIMER:
>*******************************************************
>This email and any files transmitted with it may be confidential, legally
>privileged and protected in law and are intended solely for the use of the
>
>individual to whom it is addressed.
>This email was multiple times scanned for viruses. There should be no
>known virus in this email!
>*******************************************************
>
>
>
>------------------------------------------------------------------------------
>Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
>Be part of this innovative community and reach millions of netbook users
>worldwide. Take advantage of special opportunities to increase revenue and
>speed time-to-market. Join now, and jumpstart your future.
>http://p.sf.net/sfu/intel-atom-d2d
>_______________________________________________
>Assp-test mailing list
>Assp-test@...
>https://lists.sourceforge.net/lists/listinfo/assp-test

# Error: Sequence (?|...) not recognized in regex; marked by <-- HERE in 
m/(?| <-- HERE 

 (?|...) - is only supported under Perl 5.10 or higher - try to use an 
older version of that module or install Perl 5.10 or higher.

Thomas





Von:    "dreamservice@..." <dreamservice@...>
An:     assp-test@...
Datum:  30.08.2010 08:35
Betreff:        Re: [Assp-test] MIME encoding for our ASSP header lines 
failed





as it seems the problem is related with Email::Address (and not with 
MIME::
Tools) which does not compile in RHEL5x32 (and Centos 5.5 32bit)
https://rt.cpan.org/Public/Bug/Display.html?id=60765

(I am trying to  find source of Email::Address with a version lower than 
1.890 
so I can test if it works)


Graziano



Hello

I have a linux server returning following error when starting ASSP

Aug-27-10 11:41:26 Warning: MIME encoding for our ASSP header lines failed 
-
- **** please install the Perl module MIME::Tools (includes MIME::Words) 
via
'cpan install MIME::Tools' (on nix/mac) or 'ppm install MIME-Tools' (on
win32);

I tried

- installed and reinstalled MIME::Tools (it is up to date 5.428) , 
MIME::Words
, Email::MIME::Modifier
- reinstalled perl 5.8.8

nothing to do , the error does not go away . Which could be the problem ?

Thank you
Graziano




------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 

speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test



------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 

speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

I have perl 5.8.8

I uninstalled Email::Address 1.890 and installed 1.889 http://search.cpan.
org/~rjbs/Email-Address-1.889/lib/Email/Address.pm
from source and Email:Address was compiled correctly , now ASSP can work fine 
anf the Mime::Tools errors stopped .
Fixed

Graziano

ASSP development mailing list <assp-test@...>
schreibt:
>
>> It looks like the cleanup process triggered it.

Check the setting of LDAPcrossCheckInterval

> 
> Check the setting of LDAPcrossCheckInterval
> 
It's set to 24.

Hill, Brett wrote:
> Just happened to look at the Maillog tail in the GUI at the right time
> >  to notice a whole bunch of entries like this:
> >  
> >  Aug-24-10 12:23:29 Saving ldap records;
> >    Aug-24-10 12:23:30 Saving ldap records;
>    

This seems to have been fixed it 0.0.07

Doug


-- 
Ben Franklin quote:

"Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."

Dale,

this is imlemented in your running version - look at the changelog.txt at 
SF-CVS

Thomas




Von:    "Dale" <dbritt@...>
An:     "ASSP development mailing list" <assp-test@...>
Datum:  26.08.2010 18:59
Betreff:        Re: [Assp-test] Further problems with Block-reports




Hi Thomas

We are running ASSP version 2.0.2(1.2.02) and the Block Reports still 
appear 
the same as before.

When do you expect to have a solution as discussed below implemented?

Not rushing, just curious

Thanks

Dale


----- Original Message ----- 
From: "Thomas Eckardt" <Thomas.Eckardt@...>
To: "ASSP development mailing list" <assp-test@...>
Sent: Wednesday, August 18, 2010 12:58 PM
Subject: Re: [Assp-test] Further problems with Block-reports


>
> Zrin,
>
>>I mean subjects of the blocked e-mails, in each entry in the report,
> like with
>> $line =~ s/\[([^\]]+)\] ;/<br\/>[<strong>$1<\/strong>]/;
>
>
> Next version will do something similar.
>
>
>
>>>> 1) The markup für the icon in the html part of the block report
>> sometimes gets splitted within the cid: number, like
>
> Next version will wrap the HTML code in lines with max 76 characters.
>
> Thomas
>
>
>
> Von:    Zrin Ziborski <zrin+assp@...>
> An:     ASSP development mailing list <assp-test@...>
> Datum:  18.08.2010 12:55
> Betreff:        Re: [Assp-test] Further problems with Block-reports
>
>
>
>
> Am 18.08.2010 09:33, schrieb Thomas Eckardt:
>>> Error: syntax error in report address in
>>> /usr/share/assp/files/blockreportuser.txt in entry
>>> *@non_local_domain=>admin@...
>>> According to help text that should be a valid entry (?)
> >
>> ??  - replace  'non_local_domain' with the ('non local') domain name 
you
>> want to search for.
>>
> I see... I wanted to see what a report for all non-local domains would
> look like
> (since *@*=>... is for all local domains)
>
>>> I'd suggest to make subject bold ("strong")
>> Edit the 'blockreport_sub.txt' to do this.
>>
> I mean subjects of the blocked e-mails, in each entry in the report,
> like with
>> $line =~ s/\[([^\]]+)\] ;/<br\/>[<strong>$1<\/strong>]/;
>> to getBlockReasons just before "$line = Encode::encode("utf-8", $line)
>> ...", but I guess there's a cleaner solution.
>
>
>>> 1) The markup für the icon in the html part of the block report
>> sometimes gets splitted within the cid: number, like
>>
>> ASSP is not doing this nor should this be done by the HTML-Browser. It
>> could be happen that a source viewer shows the HTML source this way, 
but
>> this could be ignored.
>
> Probably the e-mail client or MTA are doing that, somwhere
> there is a line lenght limit (it is not the viewer - for sure).
> Note that the whole html part of a block report was in one line.
> The splitted markup does break the html structure - it
> is mostly visible as missing icon or distorted table structure,
> sometimes as a broken link.
>
> Inserting a newline "now and then" prevents building overlong lines
> and thus prevents this problem, like with
>
> $line =~
> s/(.*)/\n<tr bgcolor="$bgcolor"><td WIDTH="20px" valign="MIDDLE"
> align="center" style="border-bottom: 1px solid
> #C0C0C0">\n$leftbut<\/td><td WIDTH="94%" style="border-bottom: 1px solid
> #C0C0C0;"><br \/>$1<br \/><\/td><td align="center" valign="MIDDLE"
> WIDTH="3%" style="border-bottom: 1px solid
> #C0C0C0;">\n$rightbut<\/td><\/tr>/;
>
> in sub getBlockReasons (added \n at the start of replacement part).
> I've also added \n in front of every icon link to be sure.
> With that change long reports are not distorted any more.
>
> best regards,
> Zrin
>
>
> 
------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, 
legally
> privileged and protected in law and are intended solely for the use of 
the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
> 
------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Assp-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test 


------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 

speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

> Analyze which check generates the penalty points for 
> 'gmail.com' - exclude the gmail IP's or domain from 
> this check. 

Heh... easy to say, not so easy to do on a box which
handles some hundreds of thousands emails <g>
ok... I'll try grepping and wading through the logs