Matti Haack wrote:
>> their source in the local server. And these mails should be accepted
>> since web services could want to write mails to users etc.
> The Webservices cansendto LOCAL users without
> authentification!
But local webservices can also send to external destina
In Testmode settings: Prepend Spam Subject.
Obviously you have to have the relevant test modes configured.
If you missed that one, you probably didn't read enough as its right
there in the GUI!
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of James
McGuinness
Sent: Thursd
I took out the spaces, does it matter ?
Why are here these spaces, why are not
>globalmailer.net|global411.net|globalftp.net
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 e
Erick <[EMAIL PROTECTED]> schreibt:
>localDomains -- Local Domains*: globalmailer.net | global411.net |
>globalftp.net |
Why are here these spaces, why are not
>globalmailer.net|global411.net|globalftp.net
???
-
Thi
>Is there some assp setting to avoid this as it is, it defeats the
>purpose of using BCC.
section spamcontrol: Add Envelope-Recipient Header',
'Adds a line to the email header "X-Assp-Intended-For: [EMAIL PROTECTED]
Default is "off".
--
Skip Local Domain Check
Has to be check to get mail from the outside world or it responds relaying not
allowed to everything.
but it will also accept mail from any email even if spoofed.
what to do ?
-
This SF.net email is
Also would not send out unless I DID CHECK the "Skip Local Domain Check" then
the mails seem to send
ok, before I just got this with it NOT checked
Sorry, your message from <[EMAIL PROTECTED]> to
could not be delivered. The specific error is:
550-Verification failed for <[EMAIL PROTECTED]>
55
Hello
I was recently found that whenever I send email to a list of BCC
recipients, the entire list of BCC recipients is added to the visible
headers of the email. The header contains the string
"Intended-For" followed by all the BCC recipients, right out there in plain
text.
Is there some assp s
Was not sure will this prevent the relaying ?
and keep me off the open relay lists ?
S e c t i o n: Relaying
acceptAllMail -- Accept All Mail* :
localDomains -- Local Domains*: globalmailer.net | global411.net |
globalftp.net |
nolocalDomains -- Skip Local Domain Check:
ldLDAP -- Do LDA
Erick <[EMAIL PROTECTED]> schreibt:
>NOLOCALDOMAINS -- Skip Local Domain Check: 1
You set "Skip Local Domain Ckeck" to 1 , why ?
If you provide the local domains and set
>Skip Local Domain Check
to its default (0), ASSP will prevent relaying and will do it on the
spot.
-
Hello All,
Boy do I appreciate all the help and it is very useful,
Yes MailMax 5.5 , also I have not changed any settings in the mailmax other
than taking the tarpitting off
as it kept banning 127.0.0.1 for to many connection "of course" and changing
the SMTP port
So ASSP is on port 25 listen
Fritz Borgstedt wrote:
> The rbl-cache checks are done prior to greylisting
i see - as almost always my findings are not a bug but a feature :-)
thx for your response!
--
View this message in context:
http://www.nabble.com/-v1.3.2%28final.5%29--rbl-check-prior-to-greylisting--tf3877905
Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
schreibt:
>according to the logs the rbl-checks are done prior to greylisting
The rbl-cache checks are done prior to greylisting .
-
This SF.net email is
How can I add SPAM to the Subject of a spammed mail passed on my ASSP? I am
testing the toolbar for a few users and want to add this tag.
James McGuinness
Network Administrator
Stelvio Inc.
514.281.8570 x257
-
This
> their source in the local server. And these mails should be accepted
> since web services could want to write mails to users etc.
The Webservices cansendto LOCAL users without
authentification!
Local delivery is always allowed (otherwise, all sending SMTP-Server would
>
> >Microsoft Virtual Server
>
> That would explain everything ))).
>
We've been running ASSP on VMware ESX Server for 2 years now and it has
been running perfectly fine all the time. Clock syncing is however
important on both real and physical servers, especially if you're trying
to resolve is
> I disagree, in part. You should always allow relaying for your internal LAN
> clients ~= local users.
I disagree, in part, but this is admittedly a personal preference.
Personally, I *never* allow unauthenticated senders to relay without
authenticating, period - and I enforce TLS as well, even
according to the logs the rbl-checks are done prior to greylisting
Jun-6-07 15:20:45 id-11360454 220.166.52.16 <[EMAIL PROTECTED]>
RBLCache:scoring - 220.166.52.16 rejected by bl.spamcop.net (07-06-06/12:57)
> Jun-6-07 15:20:45 id-11360454 220.166.52.16
> <[EMAIL PROTECTED]> Message-Score: 0+45 (
I know this is old, but I had similar results after I had my primary DNS
server fail.
Im on Windows 2003, assp 1.3.0 with perl 5.8 and Net::DNS 0.59.
To fix, I had to change my primary dns server on the assp system and
restart assp (to reload perl, and have Net::DNS pick up the new server
addres
[EMAIL PROTECTED] wrote:
> but as it is the ASSP will accept any mail to
> it then the smartmax will reject yes, but ASSP accepting right from the start
> is making it look like an open relay.
It looks like smartmax accepts all mails from 127.0.0.1. ASSP runs on
the same server as smartmax, so for
On 5 Jun 2007 at 8:28, Charles Marcus wrote:
> Verify Sender != Verify Recpient
>
> Which is being discussed??
You're right - I was answering a different
question! Must have been too late for me.
Anyhow, I see this has moved on to several
other threads now.
paul
Set it up like that:
1) Disable ASSP and switch your MTAs listen port to 25
2) set up your MTA that it will not relay for anybody except for
authenticated users
3) set up your MTA that it will accept all mail to local adresses
(without smtp-auth)
4) set up your MTA that it will NOT all
[EMAIL PROTECTED] schreibt:
>2 Allow relaying by your ASSP implementation (127.0.0.1 in your case,
why? That would exactly define an open relay.
>
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C
I think that I might have uncovered a possible source of confusion in
terminology about SmartMax's product, MailMax 5.5, which I presume is what
Erick is using.
Generally speaking, an MTA is configured to allow relaying (outgoing SMTP
messages) from local clients within its own LAN, and to deny i
Hello,
as ASSP is an PROXY, it will only accept mails which your MTA accepts!
egu> Currently the smartmax requires an auth before it will accept a mail from
a user
egu> to be sent out, I was hopping I could get the ASSP to do this or pass it
to the smartmax
egu> for this to continue to be the c
25 matches
Mail list logo
