Hi Gary,
I am seeing a similar problem. Although my processor usage has been
abnormally high for a while the last few builds are significantly worse
to the point that sending a simple text message can take 10-20 seconds.
Did you keep any records of exactly what parts of the configuration you
Hi!
I'm starting to see a bunch of crap coming to my postmaster address.
Technically - this address shouldn't be terribly restrictive...
but the damn spammers are starting to use it.
Any suggestions to block the garbage
and still keep the communication lines open?
My method:
Currently running ASSP version 2.3.4(13157)
In Recipients/LocalDomains, localDomains I have entered:
IntlBridge.com=mail.myib.com:25|myib.com=mail.myib.com:25|parcelPool.com=mail.myib.com:25
I have checked the DoVRFY option.
I have checked the DisableVRFY option (do not want external clients to
I've started seeing this error occur several times a day, starting with build
13156 and continuing with 13157 and 13160.
ASSP will be running fine, with nothing out of the ordinary logged. All of a
sudden, all workers will fail consistently with the following error:
Jun-11-13 11:42:13
I think my problem was related to virus scanning. I have clam running on the
server plus trend micro on the network. I found that DoFileScan was set to
monitor which forced both virus scanners to run on every file in and out
multiple times.
-Original Message-
I am seeing a similar
Do you have DoNoSpoofing and DoDomainIP both set to block? And
SRSValidateBounce to score?
-Original Message-
I'm starting to see a bunch of crap coming to my postmaster address.
Technically - this address shouldn't be terribly restrictive...but the damn
spammers are starting to use it.
On 6/11/2013 3:39 PM, Gary Sunderland wrote:
Do you have DoNoSpoofing and DoDomainIP both set to block? And
SRSValidateBounce to score?
-Original Message-
I'm starting to see a bunch of crap coming to my postmaster address.
Technically - this address shouldn't be terribly
What do I need
to do to get ASSP to issue the VRFY command?
your MTA must offer 'VRFY' in the reply to 'EHLO' or in the reply to
'HELP'
Thomas
Von:Peter Hinman peter.hin...@myib.com
An: assp-test@lists.sourceforge.net,
Datum: 11.06.2013 20:16
Betreff:[Assp-test] SMTP VRFY
I think this has nothing to do with the assp version. The 'Bad file
descriptor' state comes from the Perl library talking with the OS CLIB.
There could be several reasons for this:
- internal Perl lib problem while copieing the sockets from the MainThread
to the workers
- firewall blocking
-
That would explain it. Thanks for the explanation!
Peter Hinman
International Bridge / ParcelPool.com
On 6/11/2013 10:33 PM, Thomas Eckardt wrote:
What do I need
to do to get ASSP to issue the VRFY command?
your MTA must offer 'VRFY' in the reply to 'EHLO' or in the reply to
'HELP'
10 matches
Mail list logo