List Info

Thread: Confirmed Non-Spam keeps getting marked Spam
Confirmed Non-Spam keeps getting marked Spam
user name
 2006-05-18 16:03:23 

  


  

    





Fixed the 
problem.


 


The downstream MTA is on the same machine, 
but I was using the FQDN of the machine as the downstream SMTP server 
address.  Once I changed that to "localhost" it fixed the problems.  I 
am sure the issue had to have been in my DNS, host file or something like 
that....


 


Thanks again for all your help and 
time!


 





From: David Morton 
[mailto:mortondadgrmm.net]
Sent: Thu 5/18/2006 9:39 AM
To: 
Scott Organ
Cc: maia-usersrenaissoft.com
Subject: Re: 
[Maia-users] Confirmed Non-Spam keeps getting marked Spam





-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott 
Organ wrote:

> If I mark a message as "non-spam" from the list of 
suspected spam and
> then hit the "Confirm the Status of these items" 
button, the entire text
> of the email appears at the top of the Maia 
screen, followed by a line
> that reads "550 Failed to connect to SMTP 
server: Failed to connect to
> socket: connection refused".  At this 
point Maia confirms the status of
> the marked spam items, and leaves the 
non-spam message in the suspected
> spam list.

Is your downstream 
MTA on a different host? ; You have to have it listen on an IP
address 
that is accessible (ie, not 127.0.0.1), and then make sure that the
ACL's are 
set to allow the web server to access it.  Check firewall 
rules.



- --
David Morton
Maia 
Mailguard  ;           ;           
- http://www.maiamailguard.com
Morton 
Software Design and Consulting - http://www.dgrmm.net
-----BEGIN PGP 
SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with 
Mozilla - http://enigmail.mozdev.org

iD8DBQFEbIc9SIxC85HZHLMRAvbGAKCXA68pmnSzJg3rfsRQ938AxZh8SACbBxmS
iIXNMiGrb9kQuckU6lwRDTY=
=cZzC
-----END 
PGP SIGNATURE-----



  

  
  
   
     
    

  

    Confirmed Non-Spam keeps getting marked
Spam
  


  

     user name

     2006-05-18 16:36:28
  


  

    
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Organ wrote:
> Fixed the problem.
>  
> The downstream MTA is on the same machine, but I was
using the FQDN of
> the machine as the downstream SMTP server address. 
Once I changed that
> to "localhost" it fixed the problems.  I am
sure the issue had to have
> been in my DNS, host file or something like that....

The MTA is probably set up to listen on 127.0.0.1 only; the
fqdn is the real IP
address, so it shouldn't respond on that IP.


- --
David Morton
Maia Mailguard                        - http://www.maiamailguard
.com
Morton Software Design and Consulting - http://www.dgrmm.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFEbKKLSIxC85HZHLMRArhbAKCgWaCTcneGWQdCaF7aWEPBeMLitgCf
TSZl
ha4SbGJv3VnGuzlv3RBw0pg=
=T7wX
-----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users


  


  

    
  

  
  
   
     
    






 [1-2]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )