[qmailtoaster] SMTP Log Error

[Gabriel Lai]

Hi all,

When I test to send a mail from my QT mail server to another new setup QT Mail 
Server, I found the below error message at the new QT Mail Server:

@40004608e6b005ef18ac tcpserver: pid 26687 from 63.208.196.171
@40004608e6b005ef1c94 tcpserver: ok 26687 
mail.palmoleo.com.my:192.168.1.199:25 :63.208.196.171::4364
@40004608e6bb27d0489c CHKUSER accepted sender: from <[EMAIL PROTECTED]::> 
remote  rcpt <> : sender accepted
@40004608e6bb2826a214 CHKUSER accepted rcpt: from <[EMAIL PROTECTED]::> 
remote  rcpt <[EMAIL PROTECTED]> : 
found existing recipient
@40004608e6bc340c1e9c simscan:[26687]:CLEAN 
(0.90/12.00):1.1990s::63.208.196.171:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
@40004608e6bc343833c4 qmail-smtpd: qq hard reject (DomainKeys verify 
status: no key   (#5.3.0)): MAILFROM:<[EMAIL PROTECTED]> RCPTTO:[EMAIL 
PROTECTED]
@40004608e6bd16463f64 tcpserver: end 26687 status 0
@40004608e6bd1646c04c tcpserver: status: 0/100

How can I resolve this problem?

Thanks




 

No need to miss a message. Get email on-the-go 
with Yahoo! Mail for Mobile. Get started.
http://mobile.yahoo.com/mail 

Re: [qmailtoaster] SMTP Log Error

[Janno Sannik]

Someody else should veify it, but seems like it's problem with domain keys.
Best would be to disable domain keys (Erik's quote):

The only way to truly disable it is to do the following:
# cd /var/qmail/bin
# ln -sf qmail-queue.orig qmail-queue

This will be done on the next qmail-toaster release.


Gabriel Lai wrote:

Hi all,

When I test to send a mail from my QT mail server to another new setup 
QT Mail Server, I found the below error message at the new QT Mail Server:


@40004608e6b005ef18ac tcpserver: pid 26687 from 63.208.196.171
@40004608e6b005ef1c94 tcpserver: ok 26687 
mail.palmoleo.com.my:192.168.1.199:25 :63.208.196.171::4364
@40004608e6bb27d0489c CHKUSER accepted sender: from 
<[EMAIL PROTECTED]::> remote 
 rcpt <> : sender accepted
@40004608e6bb2826a214 CHKUSER accepted rcpt: from 
<[EMAIL PROTECTED]::> remote 
 rcpt 
<[EMAIL PROTECTED]> : found existing recipient
@40004608e6bc340c1e9c simscan:[26687]:CLEAN 
(0.90/12.00):1.1990s::63.208.196.171:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
@40004608e6bc343833c4 qmail-smtpd: qq hard reject (DomainKeys 
verify status: no key   (#5.3.0)): 
MAILFROM:<[EMAIL PROTECTED]> RCPTTO:[EMAIL PROTECTED]

@40004608e6bd16463f64 tcpserver: end 26687 status 0
@40004608e6bd1646c04c tcpserver: status: 0/100

How can I resolve this problem?

Thanks


Don't get soaked. Take a quick peek at the forecast 

with theYahoo! Search weather shortcut. 




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] SMTP Log Error

[PakOgah]

It seems your new mailserver rejecting email from domain which dont
DomainKeys. On your new QT server please check /etc/tcprules.d/tcp.smtp
for DKVERIFY option

mine (which is default by QT) is DKVERIFY="DEGIJKfh"

on http://wiki.qmailtoaster.com/index.php/Domainkeys is explained what the
meaning of those letter

What I don't understand why DomainKeys should disabled on next release ??
for me it just working fine ?

did I miss-understood something??

> Hi all,
>
> When I test to send a mail from my QT mail server to another new setup QT
> Mail Server, I found the below error message at the new QT Mail Server:
>
> @40004608e6b005ef18ac tcpserver: pid 26687 from 63.208.196.171
> @40004608e6b005ef1c94 tcpserver: ok 26687
> mail.palmoleo.com.my:192.168.1.199:25 :63.208.196.171::4364
> @40004608e6bb27d0489c CHKUSER accepted sender: from
> <[EMAIL PROTECTED]::> remote
>  rcpt <> : sender accepted
> @40004608e6bb2826a214 CHKUSER accepted rcpt: from
> <[EMAIL PROTECTED]::> remote
>  rcpt
> <[EMAIL PROTECTED]> : found existing recipient
> @40004608e6bc340c1e9c simscan:[26687]:CLEAN
> (0.90/12.00):1.1990s::63.208.196.171:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
> @40004608e6bc343833c4 qmail-smtpd: qq hard reject (DomainKeys verify
> status: no key   (#5.3.0)): MAILFROM:<[EMAIL PROTECTED]>
> RCPTTO:[EMAIL PROTECTED]
> @40004608e6bd16463f64 tcpserver: end 26687 status 0
> @40004608e6bd1646c04c tcpserver: status: 0/100
>
> How can I resolve this problem?
>
> Thanks
>
>
>
>
>
> 
> No need to miss a message. Get email on-the-go
> with Yahoo! Mail for Mobile. Get started.
> http://mobile.yahoo.com/mail



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] smtproutes for single domain

[mahesh wadekar]

Hi List,

I want relay one domain mail's to another domain.
I am trying following entry but that not working.

abc.com:mx.domain.com username password

but if give follwing entry then that works but all
other domains mails also realy that dont want.

:mx.domain.com username password

What may be the problem.
Please help.

Mahesh


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] smtproutes for single domain

[Jake Vickers]

mahesh wadekar wrote:

Hi List,

I want relay one domain mail's to another domain.
I am trying following entry but that not working.

abc.com:mx.domain.com username password

but if give follwing entry then that works but all
other domains mails also realy that dont want.

:mx.domain.com username password

What may be the problem.
Please help.
  
Are both domains on the same machine, or is the destination domain on a 
different machine?

If they're on the same, just use an alias domain.
Otherwise use abc.com:192.168.1.1
Change the IP address to the machine you want to receive the emails for 
abc.com

I don't think authentication is applicable in this case.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qmailtoaster] smtproutes for single domain

[mahesh wadekar]

I have two differnt mx server with smtpauth and
without smtpauth.

I have tried for without smtpauth auth server as :- 

abc.com:[xxx.xxx.xxx.xxx]
and for smtpauth server with username password as :-

abc.com:[xxx.xxx.xxx.xxx] username password
but both not working

Thanks

mahesh

--- Jake Vickers <[EMAIL PROTECTED]> wrote:

> mahesh wadekar wrote:
> > Hi List,
> >
> > I want relay one domain mail's to another domain.
> > I am trying following entry but that not working.
> >
> > abc.com:mx.domain.com username password
> >
> > but if give follwing entry then that works but all
> > other domains mails also realy that dont want.
> >
> > :mx.domain.com username password
> >
> > What may be the problem.
> > Please help.
> >   
> Are both domains on the same machine, or is the
> destination domain on a 
> different machine?
> If they're on the same, just use an alias domain.
> Otherwise use abc.com:192.168.1.1
> Change the IP address to the machine you want to
> receive the emails for 
> abc.com
> I don't think authentication is applicable in this
> case.
> 


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] smtproutes for single domain

[Jake Vickers]

mahesh wadekar wrote:

I have two differnt mx server with smtpauth and
without smtpauth.

I have tried for without smtpauth auth server as :- 


abc.com:[xxx.xxx.xxx.xxx]
and for smtpauth server with username password as :-

abc.com:[xxx.xxx.xxx.xxx] username password
but both not working

  
So you're trying to send from a server that has SMTP-AUTH enabled to a 
server that does not?
I'm not understanding what your end goal is here. Do you want machine A 
to accept emails for domain B, and relay them to machine B?




smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qmailtoaster] Qmail Package and svscan

[Ryan Gibbons]

Just for grins, I tried it again, from the same server, and it worked 
this time around.  So I am feeling better now, thanks.


Janno Sannik wrote:
if you telnet to smtp port then wait for a while (up to 5 minutes). if 
you have dns issues then it will take a long time to do a dns lookup 
for ip from where are you connecting from.


be patient and see if you get a greeting.


Ryan Gibbons wrote:

So, it seems I found the problem.

The RPM install does funny things with permissions, and I didn't 
realize it until just now.  I fixed the permission issues and it 
seems to run now, I can telnet to port 25, but don't get the smtp 
greeting, but looking at the pid file the init script creates that 
pid is still running and I can see all the supervise and multilog 
services.


I think this is good enough for me to go on, thanks Janno for making 
me look a bit harder.


Ryan Gibbons wrote:
Quick Question, If I have just installed qmail-toaster (not courier 
or anything else, just qmail-toaster and its 3 or 4 deps).  Should I 
not be able to start svscan in the supervise dir?


I am trying to test some things out, and I don't know if I need to 
troubleshoot this further, or if this will be taken care of by 
completeling the entire QmailToaster install.


Here is the error message I am getting

 * Starting qmail-toaster: svscan ...
multilog: fatal: unable to switch to current directory: access denied
multilog: fatal: unable to switch to current directory: access denied
multilog: fatal: unable to switch to current directory: access denied
multilog: fatal: unable to switch to current directory: access denied
multilog: fatal: unable to switch to current directory: access denied
multilog: fatal: unable to switch to current directory: access denied




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] qmailtoaster package problem

[Brian Trudeau]

It looks like a lot of things got deinstalled after running the upgrade.sh
script. Is there anyway I can just install everything again without
overwriting settings(currently toaster admin is not working, but webmail and
qmailadmin are fine)? This is on a live server, so I do not want to guess
that it'll work. I want to know it will work if you know what I mean.

 

-- 
Brian Trudeau,  Network Administrator
Eastek International Corporation
330 Hastings Drive,   Buffalo Grove, IL 60089
Tel: (847) 353-8300 Ext. 213   Fax: (847) 353-8900
Web: http://www.eastek-intl.com Email:
[EMAIL PROTECTED]

The information contained in this electronic mail transmission is
intended by Eastek International for the use of the named individual
or entity to which it is directed and may contain information that
is confidential or privileged.
 
If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this email without the author's prior
permission. We have taken precautions to minimize the risk of
transmitting software viruses, but we advise you to carry out your
own virus checks on any attachment to this message. We cannot
accept liability for any loss or damage caused by software viruses
or other attachments.
 
If you have received this electronic mail transmission in error,
please delete it from your system without copying or forwarding it,
and notify the sender of the error by reply email so that the
sender's address records can be corrected. Thank you.

 

Re: [qmailtoaster] qmailtoaster package problem

[Eric "Shubes"]

I'd try re-installing just control-panel-toaster (that's what gives you
toaster admin). You'll need to reset the toaster admin password (it will be
the default), but I think that's all. It's kinda hard to tell w/out seeing
what you have presently installed (rpm -qa | grep toaster). ;)

Brian Trudeau wrote:
> It looks like a lot of things got deinstalled after running the
> upgrade.sh script. Is there anyway I can just install everything again
> without overwriting settings(currently toaster admin is not working, but
> webmail and qmailadmin are fine)? This is on a live server, so I do not
> want to guess that it’ll work. I want to know it will work if you know
> what I mean.
> 
>  
> 
> -- 
> 
> Brian Trudeau,  Network Administrator
> 
> Eastek International Corporation
> 
> 330 Hastings Drive,   Buffalo Grove, IL 60089
> 
> Tel: (847) 353-8300 Ext. 213   Fax: (847) 353-8900
> 
> Web: http://www.eastek-intl.com    Email: [EMAIL 
> PROTECTED] 
> 
> 
> 
> The information contained in this electronic mail transmission is
> 
> intended by Eastek International for the use of the named individual
> 
> or entity to which it is directed and may contain information that
> 
> is confidential or privileged.
> 
>  
> 
> If you are not the intended recipient, you must not keep, use,
> 
> disclose, copy or distribute this email without the author's prior
> 
> permission. We have taken precautions to minimize the risk of
> 
> transmitting software viruses, but we advise you to carry out your
> 
> own virus checks on any attachment to this message. We cannot
> 
> accept liability for any loss or damage caused by software viruses
> 
> or other attachments.
> 
>  
> 
> If you have received this electronic mail transmission in error,
> 
> please delete it from your system without copying or forwarding it,
> 
> and notify the sender of the error by reply email so that the
> 
> sender's address records can be corrected. Thank you.
> 
>  
> 


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] qmailtoaster package problem

[Brian Trudeau]

[EMAIL PROTECTED] ~]# rpm -qa | grep toaster
libdomainkeys-toaster-0.68-1.3.2
ezmlm-toaster-0.53.324-1.3.2
qmailmrtg-toaster-4.2-1.3.2
vqadmin-toaster-2.3.4-1.3.2
ripmime-toaster-1.4.0.6-1.3.2
qmail-toaster-1.03-1.3.13
clamav-toaster-0.90-1.3.10
spamassassin-toaster-3.1.7-1.3.6
daemontools-toaster-0.76-1.3.2
vpopmail-toaster-5.4.13-1.3.3
libsrs2-toaster-1.0.18-1.3.2
courier-imap-toaster-4.1.2-1.3.6
qmailadmin-toaster-1.2.9-1.3.3
ucspi-tcp-toaster-0.88-1.3.4
maildrop-toaster-2.0.3-1.3.4
isoqlog-toaster-2.1-1.3.2
squirrelmail-toaster-1.4.9a-1.3.5
simscan-toaster-1.3.1-1.3.4
qmail-pop3d-toaster-1.03-1.3.13
autorespond-toaster-2.0.4-1.3.2
ezmlm-cgi-toaster-0.53.324-1.3.2
maildrop-toaster-devel-2.0.3-1.3.4
courier-authlib-toaster-0.59.1-1.3.5

 
-- 
Brian Trudeau,  Network Administrator
Eastek International Corporation
330 Hastings Drive,   Buffalo Grove, IL 60089
Tel: (847) 353-8300 Ext. 213   Fax: (847) 353-8900
Web: http://www.eastek-intl.com   Email: [EMAIL PROTECTED]

-Original Message-
From: Eric "Shubes" [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, March 27, 2007 8:48 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] qmailtoaster package problem

I'd try re-installing just control-panel-toaster (that's what gives you
toaster admin). You'll need to reset the toaster admin password (it will be
the default), but I think that's all. It's kinda hard to tell w/out seeing
what you have presently installed (rpm -qa | grep toaster). ;)

Brian Trudeau wrote:
> It looks like a lot of things got deinstalled after running the
> upgrade.sh script. Is there anyway I can just install everything again
> without overwriting settings(currently toaster admin is not working, but
> webmail and qmailadmin are fine)? This is on a live server, so I do not
> want to guess that it'll work. I want to know it will work if you know
> what I mean.
> 
>  
> 
> -- 
> 
> Brian Trudeau,  Network Administrator
> 
> Eastek International Corporation
> 
> 330 Hastings Drive,   Buffalo Grove, IL 60089
> 
> Tel: (847) 353-8300 Ext. 213   Fax: (847) 353-8900
> 
> Web: http://www.eastek-intl.com    Email:
[EMAIL PROTECTED] 
> 
> 
> 
> The information contained in this electronic mail transmission is
> 
> intended by Eastek International for the use of the named individual
> 
> or entity to which it is directed and may contain information that
> 
> is confidential or privileged.
> 
>  
> 
> If you are not the intended recipient, you must not keep, use,
> 
> disclose, copy or distribute this email without the author's prior
> 
> permission. We have taken precautions to minimize the risk of
> 
> transmitting software viruses, but we advise you to carry out your
> 
> own virus checks on any attachment to this message. We cannot
> 
> accept liability for any loss or damage caused by software viruses
> 
> or other attachments.
> 
>  
> 
> If you have received this electronic mail transmission in error,
> 
> please delete it from your system without copying or forwarding it,
> 
> and notify the sender of the error by reply email so that the
> 
> sender's address records can be corrected. Thank you.
> 
>  
> 


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] qmailtoaster package problem

[Eric "Shubes"]

Brian Trudeau wrote:
> [EMAIL PROTECTED] ~]# rpm -qa | grep toaster
> libdomainkeys-toaster-0.68-1.3.2
> ezmlm-toaster-0.53.324-1.3.2
> qmailmrtg-toaster-4.2-1.3.2
> vqadmin-toaster-2.3.4-1.3.2
> ripmime-toaster-1.4.0.6-1.3.2
> qmail-toaster-1.03-1.3.13
> clamav-toaster-0.90-1.3.10
> spamassassin-toaster-3.1.7-1.3.6
> daemontools-toaster-0.76-1.3.2
> vpopmail-toaster-5.4.13-1.3.3
> libsrs2-toaster-1.0.18-1.3.2
> courier-imap-toaster-4.1.2-1.3.6
> qmailadmin-toaster-1.2.9-1.3.3
> ucspi-tcp-toaster-0.88-1.3.4
> maildrop-toaster-2.0.3-1.3.4
> isoqlog-toaster-2.1-1.3.2
> squirrelmail-toaster-1.4.9a-1.3.5
> simscan-toaster-1.3.1-1.3.4
> qmail-pop3d-toaster-1.03-1.3.13
> autorespond-toaster-2.0.4-1.3.2
> ezmlm-cgi-toaster-0.53.324-1.3.2
> maildrop-toaster-devel-2.0.3-1.3.4
> courier-authlib-toaster-0.59.1-1.3.5
> 
> 
Looks like you have everything except control-panel-toaster (which includes
send-emails-toaster).

I'd remove vqadmin-toaster unless you need it for viewing. It's broken and
is being deprecated.

You might consider getting qmailtoaster-plus (see wiki). It includes some
handy tools, although none of them are required.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] Spam detection--now I get it... maybe

[John]

   I'm the one that has been trying to get answers as to why the 
infamous .Spam box gets created when I send the sample spam text to a 
user with spam detection enabled. Thanks to those who tried to help out.
   In the end, I had to just keep reading on my own, and reverse 
engineering Qmailtoaster in order to gain a better understanding of how 
it all fits together. I've learned that Simscan rejects spam before it 
ever reaches the Qmail queue for processing. My user's .Spam box never 
gets created because the mailfilter script doesn't get called unless 
Simscan passes it through. So the point of the infamous "spambox" 
is...what, exactly?
   I.e., Qmailtoaster is working exactly as it was intended after all. 
But, while I can see the advantage of having multiple spam filters, if 
users--or System Administrators new to Simscan--want proof that it's not 
rejecting valid email, the Spam box functionality should work at the 
door, shouldn't it? Otherwise, the multiple tutorials on "how to create 
spam folders so users can double-check that nothing useful is being 
thrown away" seems like a false sense of security.

   Am I wrong about any of this?
-John B.


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Spam detection--now I get it... maybe

[Jake Vickers]

John wrote:
   I'm the one that has been trying to get answers as to why the 
infamous .Spam box gets created when I send the sample spam text to a 
user with spam detection enabled. Thanks to those who tried to help out.
   In the end, I had to just keep reading on my own, and reverse 
engineering Qmailtoaster in order to gain a better understanding of 
how it all fits together. I've learned that Simscan rejects spam 
before it ever reaches the Qmail queue for processing. My user's .Spam 
box never gets created because the mailfilter script doesn't get 
called unless Simscan passes it through. So the point of the infamous 
"spambox" is...what, exactly?
   I.e., Qmailtoaster is working exactly as it was intended after all. 
But, while I can see the advantage of having multiple spam filters, if 
users--or System Administrators new to Simscan--want proof that it's 
not rejecting valid email, the Spam box functionality should work at 
the door, shouldn't it? Otherwise, the multiple tutorials on "how to 
create spam folders so users can double-check that nothing useful is 
being thrown away" seems like a false sense of security.

   Am I wrong about any of this?

Sorry to jump in so late.
the spambox option was added due to many users requesting it (myself 
being one of the more vocal ones).
Toaster is not, by default, configured to utilize it. This was decided 
by Nick and Erik.  Mark Samples and myself wanted to keep the 
functionality (it was removed due to a bug in the script) so we got it 
put back in as an option.
If you want to use it, you'll need to change the default in simscan, or 
it will be deleting it before mailfilter can get it. What I've done is 
put my scoring at 5.0 (in my local.cf), my mailfilter score at 10.0, and 
my simscan score at 18.0.  That allows me to drop the mail that is 
blatantly spam, while still training my Bayes for stuff that is spam but 
still "sneaky".
If you leave simscan where it's at, you will never get your Bayes 
trained unless you physically go in and train it by hand.

Does that make sense?


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qmailtoaster] Spam detection--now I get it... maybe

[Philip Nix Guru]

Hello
if you have a standard installation (no modded spec files )
a message tagged as SPAM will be rejected if it reaches a spam level of 
12 ( :clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif)
but it is compiled with s spam-level of 20  ... so if no set in your 
simcontrol file, it is 20 ..


So below 12, it is delivered, if you have a .qmail with the
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter: 
maildrop-toaster' /etc/mail/mailfilter
it will check if the .Spam Box is created, if not create it and do its 
"magic"
if you want I can detail you the complete process, on a quota and a non 
quota account
you may check one option:  cc "|sa-learn --spam" adn comment it if your 
server loads or if it gets very busy ...


Then of course, in your mail client, outlook,thunderbird,eudora .. 
register your new Folder ... if you use imap

It really works without any special configuration

I tweaked mine for personal reasons but the toaster out of the box works 
nicely


check your simcontrol and tcp.smtp files

Cheers
-P


John wrote:
   I'm the one that has been trying to get answers as to why the 
infamous .Spam box gets created when I send the sample spam text to a 
user with spam detection enabled. Thanks to those who tried to help out.
   In the end, I had to just keep reading on my own, and reverse 
engineering Qmailtoaster in order to gain a better understanding of 
how it all fits together. I've learned that Simscan rejects spam 
before it ever reaches the Qmail queue for processing. My user's .Spam 
box never gets created because the mailfilter script doesn't get 
called unless Simscan passes it through. So the point of the infamous 
"spambox" is...what, exactly?
   I.e., Qmailtoaster is working exactly as it was intended after all. 
But, while I can see the advantage of having multiple spam filters, if 
users--or System Administrators new to Simscan--want proof that it's 
not rejecting valid email, the Spam box functionality should work at 
the door, shouldn't it? Otherwise, the multiple tutorials on "how to 
create spam folders so users can double-check that nothing useful is 
being thrown away" seems like a false sense of security.

   Am I wrong about any of this?
-John B.


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Spam detection--now I get it... maybe

[Erik A. Espinoza]

Hi John,

Simscan + SpamAssassin rejects spam above 12 hits (by default) before
it hits the qmail-queue (hard reject). This is very obvious spam and
it is usually safe to reject at this many hits, as it is very unlikely
to be legitimate at this number of hits. SpamAssassin will also label
5-11.9 as ***SPAM***. The QmailAdmin spambox puts everything from
5-11.9 hits in the Spam folder for users. This is likely spam, but
without whitelists it can result in the occasional false positive.

For example, I use the QmailToaster at work for a local site of a
large megacorp. When we first migrated to the QmailToaster, the first
corporate e-mail going to all users came in, formatted all nasty in
outlook with images and lots of caps, SpamAssassin saw that as 5.1
hits (without a whitelist). Our users got the e-mail, albeit rewritten
as ***SPAM***, I added the corp to the whitelist and all has been well
since.

Spambox would have moved this over to the Spam folder, making the
users inbox easier to follow.

Thanks,
Erik

On 3/27/07, John <[EMAIL PROTECTED]> wrote:

I'm the one that has been trying to get answers as to why the
infamous .Spam box gets created when I send the sample spam text to a
user with spam detection enabled. Thanks to those who tried to help out.
In the end, I had to just keep reading on my own, and reverse
engineering Qmailtoaster in order to gain a better understanding of how
it all fits together. I've learned that Simscan rejects spam before it
ever reaches the Qmail queue for processing. My user's .Spam box never
gets created because the mailfilter script doesn't get called unless
Simscan passes it through. So the point of the infamous "spambox"
is...what, exactly?
I.e., Qmailtoaster is working exactly as it was intended after all.
But, while I can see the advantage of having multiple spam filters, if
users--or System Administrators new to Simscan--want proof that it's not
rejecting valid email, the Spam box functionality should work at the
door, shouldn't it? Otherwise, the multiple tutorials on "how to create
spam folders so users can double-check that nothing useful is being
thrown away" seems like a false sense of security.
Am I wrong about any of this?
-John B.


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Spam detection--now I get it

[John]

   Erik, Jake, and Philip, thank you immensely for the details! I 
really needed it. It probably would have taken me another two days to 
figure all that out, if not more. Perhaps a statement in the FAQ (3.6) 
as to why the sample-spam.txt included with Spamassassin is a poor test 
of the spambox function could save others a lot of hair-pulling...

   Thank you!
John

Erik A. Espinoza wrote:

Hi John,

Simscan + SpamAssassin rejects spam above 12 hits (by default) before
it hits the qmail-queue (hard reject). This is very obvious spam and
it is usually safe to reject at this many hits, as it is very unlikely
to be legitimate at this number of hits. SpamAssassin will also label
5-11.9 as ***SPAM***. The QmailAdmin spambox puts everything from
5-11.9 hits in the Spam folder for users. This is likely spam, but
without whitelists it can result in the occasional false positive.

For example, I use the QmailToaster at work for a local site of a
large megacorp. When we first migrated to the QmailToaster, the first
corporate e-mail going to all users came in, formatted all nasty in
outlook with images and lots of caps, SpamAssassin saw that as 5.1
hits (without a whitelist). Our users got the e-mail, albeit rewritten
as ***SPAM***, I added the corp to the whitelist and all has been well
since.

Spambox would have moved this over to the Spam folder, making the
users inbox easier to follow.

Thanks,
Erik

On 3/27/07, John <[EMAIL PROTECTED]> wrote:


I'm the one that has been trying to get answers as to why the
infamous .Spam box gets created when I send the sample spam text to a
user with spam detection enabled. Thanks to those who tried to help out.
In the end, I had to just keep reading on my own, and reverse
engineering Qmailtoaster in order to gain a better understanding of how
it all fits together. I've learned that Simscan rejects spam before it
ever reaches the Qmail queue for processing. My user's .Spam box never
gets created because the mailfilter script doesn't get called unless
Simscan passes it through. So the point of the infamous "spambox"
is...what, exactly?
I.e., Qmailtoaster is working exactly as it was intended after all.
But, while I can see the advantage of having multiple spam filters, if
users--or System Administrators new to Simscan--want proof that it's not
rejecting valid email, the Spam box functionality should work at the
door, shouldn't it? Otherwise, the multiple tutorials on "how to create
spam folders so users can double-check that nothing useful is being
thrown away" seems like a false sense of security.
Am I wrong about any of this?
-John B.


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Spam detection--now I get it

[Erik A. Espinoza]

Feel free to add it to the wiki.

On 3/27/07, John <[EMAIL PROTECTED]> wrote:

Erik, Jake, and Philip, thank you immensely for the details! I
really needed it. It probably would have taken me another two days to
figure all that out, if not more. Perhaps a statement in the FAQ (3.6)
as to why the sample-spam.txt included with Spamassassin is a poor test
of the spambox function could save others a lot of hair-pulling...
Thank you!
John

Erik A. Espinoza wrote:
> Hi John,
>
> Simscan + SpamAssassin rejects spam above 12 hits (by default) before
> it hits the qmail-queue (hard reject). This is very obvious spam and
> it is usually safe to reject at this many hits, as it is very unlikely
> to be legitimate at this number of hits. SpamAssassin will also label
> 5-11.9 as ***SPAM***. The QmailAdmin spambox puts everything from
> 5-11.9 hits in the Spam folder for users. This is likely spam, but
> without whitelists it can result in the occasional false positive.
>
> For example, I use the QmailToaster at work for a local site of a
> large megacorp. When we first migrated to the QmailToaster, the first
> corporate e-mail going to all users came in, formatted all nasty in
> outlook with images and lots of caps, SpamAssassin saw that as 5.1
> hits (without a whitelist). Our users got the e-mail, albeit rewritten
> as ***SPAM***, I added the corp to the whitelist and all has been well
> since.
>
> Spambox would have moved this over to the Spam folder, making the
> users inbox easier to follow.
>
> Thanks,
> Erik
>
> On 3/27/07, John <[EMAIL PROTECTED]> wrote:
>
>> I'm the one that has been trying to get answers as to why the
>> infamous .Spam box gets created when I send the sample spam text to a
>> user with spam detection enabled. Thanks to those who tried to help out.
>> In the end, I had to just keep reading on my own, and reverse
>> engineering Qmailtoaster in order to gain a better understanding of how
>> it all fits together. I've learned that Simscan rejects spam before it
>> ever reaches the Qmail queue for processing. My user's .Spam box never
>> gets created because the mailfilter script doesn't get called unless
>> Simscan passes it through. So the point of the infamous "spambox"
>> is...what, exactly?
>> I.e., Qmailtoaster is working exactly as it was intended after all.
>> But, while I can see the advantage of having multiple spam filters, if
>> users--or System Administrators new to Simscan--want proof that it's not
>> rejecting valid email, the Spam box functionality should work at the
>> door, shouldn't it? Otherwise, the multiple tutorials on "how to create
>> spam folders so users can double-check that nothing useful is being
>> thrown away" seems like a false sense of security.
>> Am I wrong about any of this?
>> -John B.
>>
>>
>> -
>>  QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Spam detection--now I get it

[John]

Looks like somebody somebody has already added the gist of this. I added 
the detail about sample-spam.txt.

john

Erik A. Espinoza wrote:

Feel free to add it to the wiki.

On 3/27/07, John <[EMAIL PROTECTED]> wrote:


Erik, Jake, and Philip, thank you immensely for the details! I
really needed it. It probably would have taken me another two days to
figure all that out, if not more. Perhaps a statement in the FAQ (3.6)
as to why the sample-spam.txt included with Spamassassin is a poor test
of the spambox function could save others a lot of hair-pulling...
Thank you!
John

Erik A. Espinoza wrote:
> Hi John,
>
> Simscan + SpamAssassin rejects spam above 12 hits (by default) before
> it hits the qmail-queue (hard reject). This is very obvious spam and
> it is usually safe to reject at this many hits, as it is very unlikely
> to be legitimate at this number of hits. SpamAssassin will also label
> 5-11.9 as ***SPAM***. The QmailAdmin spambox puts everything from
> 5-11.9 hits in the Spam folder for users. This is likely spam, but
> without whitelists it can result in the occasional false positive.
>
> For example, I use the QmailToaster at work for a local site of a
> large megacorp. When we first migrated to the QmailToaster, the first
> corporate e-mail going to all users came in, formatted all nasty in
> outlook with images and lots of caps, SpamAssassin saw that as 5.1
> hits (without a whitelist). Our users got the e-mail, albeit rewritten
> as ***SPAM***, I added the corp to the whitelist and all has been well
> since.
>
> Spambox would have moved this over to the Spam folder, making the
> users inbox easier to follow.
>
> Thanks,
> Erik
>
> On 3/27/07, John <[EMAIL PROTECTED]> wrote:
>
>> I'm the one that has been trying to get answers as to why the
>> infamous .Spam box gets created when I send the sample spam text to a
>> user with spam detection enabled. Thanks to those who tried to help 
out.

>> In the end, I had to just keep reading on my own, and reverse
>> engineering Qmailtoaster in order to gain a better understanding of 
how

>> it all fits together. I've learned that Simscan rejects spam before it
>> ever reaches the Qmail queue for processing. My user's .Spam box never
>> gets created because the mailfilter script doesn't get called unless
>> Simscan passes it through. So the point of the infamous "spambox"
>> is...what, exactly?
>> I.e., Qmailtoaster is working exactly as it was intended after 
all.

>> But, while I can see the advantage of having multiple spam filters, if
>> users--or System Administrators new to Simscan--want proof that 
it's not

>> rejecting valid email, the Spam box functionality should work at the
>> door, shouldn't it? Otherwise, the multiple tutorials on "how to 
create

>> spam folders so users can double-check that nothing useful is being
>> thrown away" seems like a false sense of security.
>> Am I wrong about any of this?
>> -John B.
>>
>>
>> -
>>  QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: 
[EMAIL PROTECTED]

>>
>>
>
> -
> QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: 
[EMAIL PROTECTED]

>
>
>
>


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Spam detection--now I get it

[Jake Vickers]

John wrote:
Looks like somebody somebody has already added the gist of this. I 
added the detail about sample-spam.txt.

john
That was me. Realized it was something important that should be in 
there, so I roughed it out.

Thanks.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qmailtoaster] smtproutes for single domain

[mahesh wadekar]

Sorry for confusing mail

simply I want only this.
I have ten domain in our server in which abc.com mail
i want to forward or relay to xyz.com server. xyz.com
is on another location or server.
But using following line in smtproutes that not work.
abc.com:[xxx.xxx.xxx.xxx]

But if i use 
:[xxx.xxx.xxx.xxx] 

Then all our domains mail's forward to xyz.com server.
That i dont want.



--- Jake Vickers <[EMAIL PROTECTED]> wrote:

> mahesh wadekar wrote:
> > I have two differnt mx server with smtpauth and
> > without smtpauth.
> >
> > I have tried for without smtpauth auth server as
> :- 
> >
> > abc.com:[xxx.xxx.xxx.xxx]
> > and for smtpauth server with username password as
> :-
> >
> > abc.com:[xxx.xxx.xxx.xxx] username password
> > but both not working
> >
> >   
> So you're trying to send from a server that has
> SMTP-AUTH enabled to a 
> server that does not?
> I'm not understanding what your end goal is here. Do
> you want machine A 
> to accept emails for domain B, and relay them to
> machine B?
> 
> 


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] smtproutes for single domain

[Dean Mumby]

mahesh wadekar wrote:

Sorry for confusing mail

simply I want only this.
I have ten domain in our server in which abc.com mail
i want to forward or relay to xyz.com server. xyz.com
is on another location or server.
But using following line in smtproutes that not work.
abc.com:[xxx.xxx.xxx.xxx]

But if i use 
:[xxx.xxx.xxx.xxx] 


Then all our domains mail's forward to xyz.com server.
That i dont want.

  
if abc.com is a virtual domain ie has a folder 
/home/vpopmail/domains/abc.com then it will never get sent to xyz.com , 
it cant be a local domain and sent to a relay. If you want to relay for 
a domain just add abc.com to rcpthosts and your smtpoutes rule will work 
but you must delete it from vpopmail. add it before the 
:[xxx.xxx.xxx.xxx] entry if you have one. I hope that makes sense.


dean



--- Jake Vickers <[EMAIL PROTECTED]> wrote:

  

mahesh wadekar wrote:


I have two differnt mx server with smtpauth and
without smtpauth.

I have tried for without smtpauth auth server as
  
:- 


abc.com:[xxx.xxx.xxx.xxx]
and for smtpauth server with username password as
  

:-


abc.com:[xxx.xxx.xxx.xxx] username password
but both not working

  
  

So you're trying to send from a server that has
SMTP-AUTH enabled to a 
server that does not?

I'm not understanding what your end goal is here. Do
you want machine A 
to accept emails for domain B, and relay them to

machine B?






-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] smtproutes for single domain

[Erik A. Espinoza]

sounds like you want domain aliases rather than smtp routes.

Erik

On 3/27/07, Dean Mumby <[EMAIL PROTECTED]> wrote:

mahesh wadekar wrote:
> Sorry for confusing mail
>
> simply I want only this.
> I have ten domain in our server in which abc.com mail
> i want to forward or relay to xyz.com server. xyz.com
> is on another location or server.
> But using following line in smtproutes that not work.
> abc.com:[xxx.xxx.xxx.xxx]
>
> But if i use
> :[xxx.xxx.xxx.xxx]
>
> Then all our domains mail's forward to xyz.com server.
> That i dont want.
>
>
if abc.com is a virtual domain ie has a folder
/home/vpopmail/domains/abc.com then it will never get sent to xyz.com ,
it cant be a local domain and sent to a relay. If you want to relay for
a domain just add abc.com to rcpthosts and your smtpoutes rule will work
but you must delete it from vpopmail. add it before the
:[xxx.xxx.xxx.xxx] entry if you have one. I hope that makes sense.

dean

>
> --- Jake Vickers <[EMAIL PROTECTED]> wrote:
>
>
>> mahesh wadekar wrote:
>>
>>> I have two differnt mx server with smtpauth and
>>> without smtpauth.
>>>
>>> I have tried for without smtpauth auth server as
>>>
>> :-
>>
>>> abc.com:[xxx.xxx.xxx.xxx]
>>> and for smtpauth server with username password as
>>>
>> :-
>>
>>> abc.com:[xxx.xxx.xxx.xxx] username password
>>> but both not working
>>>
>>>
>>>
>> So you're trying to send from a server that has
>> SMTP-AUTH enabled to a
>> server that does not?
>> I'm not understanding what your end goal is here. Do
>> you want machine A
>> to accept emails for domain B, and relay them to
>> machine B?
>>
>>
>>
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] spamd memory hog

[John]

Check these VSZ's out: # ps aux |grep spamd
root 13967  0.0  0.0  2236  204 pts/1S00:19   0:00 supervise 
spamd
root 13989  7.1 30.7 156556 153488 pts/1 S00:19   0:07 
/usr/bin/perl -T -w /usr/bin/spamd -x -u vpopmail -s stderr
qmaill   13990  0.0  0.0  2932  212 pts/1S00:19   0:00 
/usr/bin/multilog t s100 n100 /var/log/qmail/spamd

vpopmail 14109  0.0 30.3 156556 151864 pts/1 S00:20   0:00 spamd child
vpopmail 14110  0.0 30.3 156556 151816 pts/1 S00:20   0:00 spamd child
root 14118  0.0  0.1  5016  644 pts/1R+   00:21   0:00 grep spamd

Another box shows about 28000 for VSZ, compared to 156556 here. Any 
suggestions on why it's taking so much memory? Any suggested solutions?


Thanks,
John B.


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] spamd memory hog

[Erik A. Espinoza]

Another box shows about 28000 for VSZ, compared to 156556 here. Any
suggestions on why it's taking so much memory? Any suggested solutions?


Does one have a higher load due to more e-mail being processed than the other?
Do the machines have a different OS?
Do they have a different architecture?
Do they have different SpamAssassin plugins?
Are they the same version of SpamAssassin?

All of these are reasons why one machine would show different memory
usage on SpamAssassin

Erik

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]