Re: [qmailtoaster] Multiple IPs on one machine

[curt . qt]

If possible, I'd rather not have another box to manage - physical or virtual. If
that's the route I have to go, then that's the route I'll go.



Does anyone have any other ideas?



perhaps a VPS using VMware server or OpenVPZ can do the trick...

but then you have scratch your box again..



[EMAIL PROTECTED] wrote:

> I already have several domains on the same IP - the problem is that we

> have a client who wants to send emails to a very large list. In the

> event that the process gets the server blacklisted, I don't want the

> other clients to be affected. If I can set up a domain on that machine

> to send from a different IP, that would do the trick.

>

> BTW, I googled this topic to death with no luck before posting here...

> I always do.  :)

>

> --

>

> I know theres been talk of it on the mailing list, have a search there.

> I started down that path on my first multidomain server... but because

> you can have MX records point to a domain and not an ip, its trivial

> (and standard) to just use a single IP address for all your domains.

> trwww

> - Original Message 

>

From: "[EMAIL PROTECTED]"

> To: qmailtoaster-list@qmailtoaster.com

> Sent: Wednesday, May 28, 2008 3:22:58 PM

> Subject: [qmailtoaster] Multiple IPs on one machine

>

> On a qmailtoaster box hosting several email domains, is it possible to

> assign a different IP address to one of the domains? I know how to set

> up multiple IP address on the linux box, but I'm not sure how to (or

> even if it's possible) to set up qmail to select the IP it sends from

> based on the sender's domain.





-

QmailToaster hosted by: VR Hosted 

-

To unsubscribe, e-mail: [EMAIL PROTECTED]

For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Multiple IPs on one machine

[curt . qt]

I already have several domains on the same IP - the problem
is that we have a client who wants to send emails to a very large list. In the
event that the process gets the server blacklisted, I don't want the other
clients to be affected. If I can set up a domain on that machine to send from a
different IP, that would do the trick.



BTW, I googled this topic to death with no luck before posting here... I always
do.  :)



--



I know theres been talk of it on the mailing list, have a search there.
 
I started down that path on my first multidomain server...
but because you can have MX records point to a domain and not an ip, its trivial
(and standard) to just use a single IP address for all your domains.
 
trwww


- Original Message 

From: "[EMAIL PROTECTED]" 

To: qmailtoaster-list@qmailtoaster.com

Sent: Wednesday, May 28, 2008 3:22:58 PM

Subject: [qmailtoaster] Multiple IPs on one machine



On a qmailtoaster box hosting several email domains, is it possible to assign a
different IP address to one of the domains? I know how to set up multiple IP
address on the linux box, but I'm not sure how to (or even if it's possible) to
set up qmail to select the IP it sends from based on the sender's domain.

[qmailtoaster] Multiple IPs on one machine

[curt . qt]

On a qmailtoaster box hosting several email domains, is it possible to assign a
different IP address to one of the domains? I know how to set up multiple IP
address on the linux box, but I'm not sure how to (or even if it's possible) to
set up qmail to select the IP it sends from based on the sender's domain.

Re: [qmailtoaster] How to not forward messages marked as spam

[curt . qt]

If I understand simscan / simcontrol functions, you can only specify global,
local domain, or specific user settings. There are many virtual domains hosted
on the server, and I don't want to just specify spam dropping for any single
domain - I want to be able to drop spam if any single account is set to forward
its email to an external domain.



In other words, for all local domains, I want to drop spam if any account is set
up to forward its email to an external server. Ideally, this would also be set
up for simple forwards as well.



So, I need to drop spam for:


Forwards (ideally, only forwards to external domains... [EMAIL PROTECTED],
[EMAIL PROTECTED], etc)
Standard accounts with the "Forward To:" radio button selected
in qmailadmin. (user's .qmail file = &[EMAIL PROTECTED])





You can specify only that domain in a separate record in simcontrol, with

the appropriate value for spam_hits so they'll be rejected.



[EMAIL PROTECTED] wrote:

> I would like to completely dump messages tagged as spam, but only for

> accounts set to forward to an external domain. Local spam should go to

> its normal .Spam folder.

> 

>

> What is it you'd like to do with messages tagged as spam?

>

> If you want to reject them, simply bring down the value for spam_hits in

> /var/qmail/simcontrol to equal the value of required_score in

> /etc/mail/spamassassin/local.cf. Then anything which would have been
tagged

> will be rejected up front.

>

> --

> -Eric 'shubes'

>

> 

>

> [EMAIL PROTECTED] wrote:

>> I've been having problems with accounts which are set up to simply to

> external

>> addresses. For a standard account, the

> /home/vpopmail/[domain]/[user]/.qmail

>> file contains the following:

>>

>> |/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter:

>> maildrop-toaster'

>> /etc/mail/mailfilter

>>

>> This works perfectly. For a forwarded account, the .qmail file simply

> contains

>>

>> &[address to forward to]

>>

>> While the email does get forwarded, the forwarding of tagged spam is

> causing

>> gray/blacklisting problems with recipient servers. Messages are still

>> processed

>> via spamassassin, and the subjects rewritten with ***SPAM***, but the

> messages

>> forward no matter what I try. I realize that this is by design and
that

> these

>> messages should be forwarded due to the possibility of false positives,
but

>> Yahoo keeps spitting out "451_Message_temporarily_deferred",
we get

> greylisted

>> some places, etc. The goal is to NOT forward messages tagged as spam
to

> Yahoo,

>> AOL, etc (along with a disclaimer published in the HTML of

> SquirrelMail), but

>> I

>> have no idea how to make this happen. Can I change the .qmail
"&" line

> to make

>> it pipe through an external process which checks the spam x-header?
Any

> help

>> would be greatly appreciated.

>>

>

> -

> QmailToaster hosted by: VR Hosted 

> -

> To unsubscribe, e-mail: [EMAIL PROTECTED]

> For additional commands, e-mail: [EMAIL PROTECTED]

>

>





--

-Eric 'shubes'



-

QmailToaster hosted by: VR Hosted 

-

To unsubscribe, e-mail: [EMAIL PROTECTED]

For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] How to not forward messages marked as spam

[curt . qt]

I would like to completely dump messages tagged as spam, but only for accounts 
set to forward to an
external domain. Local spam should go to its normal .Spam folder.



What is it you'd like to do with messages tagged as spam?



If you want to reject them, simply bring down the value for spam_hits in

/var/qmail/simcontrol to equal the value of required_score in

/etc/mail/spamassassin/local.cf. Then anything which would have been tagged

will be rejected up front.



--

-Eric 'shubes'





[EMAIL PROTECTED] wrote:

> I've been having problems with
accounts which are set up to simply to external> addresses. For a standard
account, the /home/vpopmail/[domain]/[user]/.qmail> file contains the
following:>> |/var/qmail/bin/preline /usr/bin/maildrop -A
'Content-Filter:> maildrop-toaster'> /etc/mail/mailfilter>> This works 
perfectly. For a forwarded account, the .qmail file
simply contains>> &[address to forward to]>> While the email does get 
forwarded, the forwarding of tagged spam
is causing> gray/blacklisting problems with recipient servers.
Messages are still> processed> via spamassassin, and the subjects rewritten
with ***SPAM***, but the messages> forward no matter what I try. I
realize that this is by design and that these> messages should be forwarded
due to the possibility of false positives, but> Yahoo keeps spitting out
"451_Message_temporarily_deferred", we get greylisted> some
places, etc. The goal is to NOT forward messages tagged as spam to
Yahoo,> AOL, etc (along with a disclaimer published in the HTML of
SquirrelMail), but> I> have no idea how to make this happen. Can I
change the .qmail "&" line to make> it pipe through an
external process which checks the spam x-header? Any help> would
be greatly appreciated.>



-

QmailToaster hosted by: VR Hosted 

-

To unsubscribe, e-mail: [EMAIL PROTECTED]

For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] How to not forward messages marked as spam

[curt . qt]

I've been having problems with accounts which are set up to simply to external
addresses. For a standard account, the /home/vpopmail/[domain]/[user]/.qmail
file contains the following:

|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter: maildrop-toaster'
/etc/mail/mailfilter

This works perfectly. For a forwarded account, the .qmail file simply contains

&[address to forward to]

While the email does get forwarded, the forwarding of tagged spam is causing
gray/blacklisting problems with recipient servers. Messages are still processed
via spamassassin, and the subjects rewritten with ***SPAM***, but the messages
forward no matter what I try. I realize that this is by design and that these
messages should be forwarded due to the possibility of false positives, but
Yahoo keeps spitting out "451_Message_temporarily_deferred", we get greylisted
some places, etc. The goal is to NOT forward messages tagged as spam to Yahoo,
AOL, etc (along with a disclaimer published in the HTML of SquirrelMail), but I
have no idea how to make this happen. Can I change the .qmail "&" line to make
it pipe through an external process which checks the spam x-header? Any help
would be greatly appreciated.


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

Re: [qmailtoaster] How to not forward messages marked as spam

[curt . qt]

I just tried changing "exit" to "exit 99" - stopped delivery of everything
completely... apparently, the exit command won't take arguments in this language

===

The .qmail file isn't a script, so you can't add logic there (that I'm aware
of). Sorry about that bit.

Have you tried
exit 99
in the maildrop script?

I don't see how the EXITCODE variable would be passed back to whatever's
calling maildrop, unless maildrop is 'sourced'. I don't know off hand how
the maildrop script is invoked.

[EMAIL PROTECTED] wrote:
> As I stated in the original request, there are apparently 0 options for a
> "forward"  line in the .qmail file. An account is set up to either forward
> using
> &[address], or to not forward at all.
>
> How might I go about "adding logic" to a & line? (That's really the root of
> the
> whole question)
>
> ===
>
> Sounds like you'll need to add logic in .qmail to check the exit code from
> mailfilter, and only do the forward if the exit code is 0.
>
> [EMAIL PROTECTED] wrote:
>> I already tried modifying /etc/mail/mailfilter to get it to
>> dump local spam and TRY to abort the procedure. Here's what I inserted
>> directly
>> after reading in
>> $VHOME/Maildir/.mailfilter. If the user's .mailfilter contains the line
>> SPAMFORWARDDROP=1, the following executes:
>>
>> if((/^X-Spam-Status: Yes/:h) && ($SPAMFORWARDDROP == 1))
>> {
>> log "Message deleted as specified by .mailfilter\n"
>> exception {
>> to "/home/vpopmail/domains/[the
>> domain]/postmaster/Maildir/.Spam/"
>> }
>> log "=== END ===\n"
>> EXITCODE=1
>> exit
>> }
>>
>> This works perfectly without having to modify the smtp delivery pipe, but the
>> next line in .qmail which contains the forward (&[address]) still executes.
>>
>> I've also tried setting EXITCODE=99 - no difference.
>>
>> =
>>
>>
>> I'd look into customizing the /etc/mail/mailfilter script. It's part of the
>> maildrop-toaster package, so if you change it, be sure to keep a backup copy
>> handy because any changes would probably be clobbered by an upgrade of that
>> package.
>>
>> --
>> -Eric 'shubes'
>>
>> =
>>
>> [EMAIL PROTECTED] wrote:
>>> Still no luck on this one - there are apparently 0 options for a "forward"
>>> line
>>> in the .qmail file. An account is set up to either forward using &[address],
>>> or
>>> to not forward at all.
>>>
>>> Is there no way to forward ONLY IF the message meets certain criteria? (i.e.
>>> $subject !~/\*\*\* SPAM \*\*\*/)
>>>
>>> This has become a huge issue, particularly for blackberry users.
>>>
>
>
>
> --
> -Eric 'shubes'
>


--
-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] How to not forward messages marked as spam

[curt . qt]

As I stated in the original request, there are apparently 0 options for a
"forward"  line in the .qmail file. An account is set up to either forward using
&[address], or to not forward at all.

How might I go about "adding logic" to a & line? (That's really the root of the
whole question)

===

Sounds like you'll need to add logic in .qmail to check the exit code from
mailfilter, and only do the forward if the exit code is 0.

[EMAIL PROTECTED] wrote:
> I already tried modifying /etc/mail/mailfilter to get it to
> dump local spam and TRY to abort the procedure. Here's what I inserted
> directly
> after reading in
> $VHOME/Maildir/.mailfilter. If the user's .mailfilter contains the line
> SPAMFORWARDDROP=1, the following executes:
>
> if((/^X-Spam-Status: Yes/:h) && ($SPAMFORWARDDROP == 1))
> {
> log "Message deleted as specified by .mailfilter\n"
> exception {
> to "/home/vpopmail/domains/[the
> domain]/postmaster/Maildir/.Spam/"
> }
> log "=== END ===\n"
> EXITCODE=1
> exit
> }
>
> This works perfectly without having to modify the smtp delivery pipe, but the
> next line in .qmail which contains the forward (&[address]) still executes.
>
> I've also tried setting EXITCODE=99 - no difference.
>
> =
>
>
> I'd look into customizing the /etc/mail/mailfilter script. It's part of the
> maildrop-toaster package, so if you change it, be sure to keep a backup copy
> handy because any changes would probably be clobbered by an upgrade of that
> package.
>
> --
> -Eric 'shubes'
>
> =
>
> [EMAIL PROTECTED] wrote:
>> Still no luck on this one - there are apparently 0 options for a "forward"
>> line
>> in the .qmail file. An account is set up to either forward using &[address],
>> or
>> to not forward at all.
>>
>> Is there no way to forward ONLY IF the message meets certain criteria? (i.e.
>> $subject !~/\*\*\* SPAM \*\*\*/)
>>
>> This has become a huge issue, particularly for blackberry users.
>>



--
-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] How to not forward messages marked as spam

[curt . qt]

I already tried modifying /etc/mail/mailfilter to get it to
dump local spam and TRY to abort the procedure. Here's what I inserted directly
after reading in
$VHOME/Maildir/.mailfilter. If the user's .mailfilter contains the line
SPAMFORWARDDROP=1, the following executes:

if((/^X-Spam-Status: Yes/:h) && ($SPAMFORWARDDROP == 1))
{
log "Message deleted as specified by .mailfilter\n"
exception {
to "/home/vpopmail/domains/[the 
domain]/postmaster/Maildir/.Spam/"
}
log "=== END ===\n"
EXITCODE=1
exit
}

This works perfectly without having to modify the smtp delivery pipe, but the
next line in .qmail which contains the forward (&[address]) still executes.

I've also tried setting EXITCODE=99 - no difference.

=


I'd look into customizing the /etc/mail/mailfilter script. It's part of the
maildrop-toaster package, so if you change it, be sure to keep a backup copy
handy because any changes would probably be clobbered by an upgrade of that
package.

--
-Eric 'shubes'

=

[EMAIL PROTECTED] wrote:
> Still no luck on this one - there are apparently 0 options for a "forward"
> line
> in the .qmail file. An account is set up to either forward using &[address],
> or
> to not forward at all.
>
> Is there no way to forward ONLY IF the message meets certain criteria? (i.e.
> $subject !~/\*\*\* SPAM \*\*\*/)
>
> This has become a huge issue, particularly for blackberry users.
>


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

[qmailtoaster] How to not forward messages marked as spam

[curt . qt]

Still no luck on this one - there are apparently 0 options for a "forward" line
in the .qmail file. An account is set up to either forward using &[address], or
to not forward at all.

Is there no way to forward ONLY IF the message meets certain criteria? (i.e.
$subject !~/\*\*\* SPAM \*\*\*/)

This has become a huge issue, particularly for blackberry users.


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

Re: [qmailtoaster] Drop SPAM to forwarded account

[curt . qt]

By the way, this is the modification I made to /etc/mail/mailfilter to get it to
dump local spam and TRY to abort the procedure, directly after reading in
$VHOME/Maildir/.mailfilter. If the user's .mailfilter contains the line
SPAMFORWARDDROP=1, the following executes:

if((/^X-Spam-Status: Yes/:h) && ($SPAMFORWARDDROP == 1))
{
log "Message deleted as specified by .mailfilter\n"
exception {
to "/home/vpopmail/domains/[the 
domain]/postmaster/Maildir/.Spam/"
}
log "=== END ===\n"
EXITCODE=1
exit
}

This works perfectly without having to modify the smtp delivery pipe, but the
next line in .qmail which contains the forward still executes. Any ideas?


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

Re: [qmailtoaster] Drop SPAM to forwarded account

[curt . qt]

I realize dumping these messages probably isn't the best alternative, but there
are users that insist (especially for info@ accounts which get bombarded, etc)

I've already successfully gotten qt to reroute / dump / not deliver LOCAL spam
messages via a modified spamfilter, but my problem is with messages which are to
be forwarded to an external domain. The goal is to not forward messages flagged
as spam.

In the .qmail file, the forwarding recipient is indicated by &[email] - is the
"&" line editable? Can I make force the script to abort before executing the
forward?



Most every SPAM filter I know will have SOME false-positives. It is
inevitable, since SPAMmers are constantly trying to make their sh*t look
like the REAL sh*t you WANT to receive.

So, you might want to consider changing the spamassassin processing to
move those messages marked as SPAM into a folder (eg: SPAM) rather than
deleting them.

However, if you're still getting tons of spam (just most of it marked SPAM
by spamassassin, you might also want to look into SpamDyke...
http://www.spamdyke.org)... I've had VERY GOOD luck with this add-on!

Finally, if you're committed to deleting the messages marked as SPAM by
spamassassin, then look into a pearl script called mailparser, found at:
http://cisu.net/files/mailparser.pl

This simple little script, when added to your smtp processing path AFTER
spamassassin, will route messages marked as SPAM to /dev/null (thus,
deleting them). But again, with the high probability of SOME level of
false positives, I DO NOT recommend this approach.

(To my kids, I relate this kind of warning to:
OK mister, here's your gun -- but be careful with it!
OK mister, here's your ammo -- but be VERY careful with it!
Now sir, you've got a loaded gun there... PLEASE be CAREFUL!
Excuse me SIR, but your gun is pointed right at your foot... PLEASE be
careful!
...
I'm very sorry you shot your foot off, sir. It'll be  to help you fix
it now! Will that be cash, or credit?)

In other words... YOU'VE BEEN WARNED!

I hope this helps... someone!

Dan

--

Dan McAllister, President
IT4SOHO, LLC

On Mon, February 18, 2008 1:47 pm, [EMAIL PROTECTED] wrote:
> I realize that the end-user SHOULD know how to assemble message rules etc,
> but
> there have been several occasions where users want to have ONLY CLEAN
> emails
> forwarded to an external account. Is this possible?
>
> Currently, all email is forwarded with some messages having a *** SPAM ***
> subject line. I would like to have the option (on a few accounts) to not
> forward
> these. How can this be accomplished?
>
>
> -
>  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] Drop SPAM to forwarded account

[curt . qt]

I realize that the end-user SHOULD know how to assemble message rules etc, but
there have been several occasions where users want to have ONLY CLEAN emails
forwarded to an external account. Is this possible?

Currently, all email is forwarded with some messages having a *** SPAM ***
subject line. I would like to have the option (on a few accounts) to not forward
these. How can this be accomplished?


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

Re: [qmailtoaster] Fw: ezmlm warning

[curt . qt]

Would you please explain to me how you use DK for signing outgoing only? I've
been through the WIKI and various other sources with no luck.

The only way I can get DK to even attempt to sign outgoing messages is by
setting QMAILQUEUE=/var/qmail/bin/qmail-dk in tcp.smtp AND using a symbolic link
to qmail-dk as qmail-queue in the bin directory. Wouldn't this pipe incoming
messages through qmail-dk too?

Even when I get qmail to attempt a DomainKeys signature, I get:

qmail-smtpd: qq hard reject (qmail-dk: Cannot sign message due to invalid
message syntax. (#5.3.0))

==
That's probably DK acting up, you should disable DK verifying on incoming
mail.

Personaly I use DK for signing and then Spamassassin for checking.

2007/7/2, Jim Shupert, Jr. <[EMAIL PROTECTED]>:
>
> Friends,
>
> I have been having a number of bounces from various mail groups
> In fact I have had a bounce from ' this qmail list ' ( see below )
> maybe , my difficulty is:
> host mailhost.pps-inc.com[208.233.14.222] said: 554
> DomainKeys verify status: bad format   (#5.3.0) (in reply to end of
> DATA
> command)
> What do you think?  and how might I remedy this?  Thanks!
>
> j
>



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

[qmailtoaster] DKSIGN help - updated

[curt . qt]

After doing some more digging, I discovered that qmail-dk needs to be assigned
to the QMAILQUEUE parameter in order to sign outgoing messages. When this is
set, the server will not send email at all. I get the following error message in
the smtp log when trying to send an email:
 qmail-smtpd: qq hard reject (qmail-dk: Cannot sign message due to invalid
message syntax. (#5.3.0))

What's more, having qmail-queue linked to qmail-dk instead of qmail-orig
obviously affects incoming messages. When qmail-dk is handling things, I
received this email from this very list:

Hi. This is the qmail-send program at ns2.qmailtoaster.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[EMAIL PROTECTED]>:
User and password not set, continuing without authentication.
<[EMAIL PROTECTED]> 205.241.238.170 failed after I sent the message.
Remote host said: 554 DomainKeys verify status: bad format   (#5.3.0)

Should I give up on DomainKeys entirely?

Below is my original plea for help...
==
Has anyone had any luck getting QT to sign outgoing messages with Domainkeys? I
read somewhere in the wiki that "domainkeys was broken",  but the instructions
regarding the issue point to incoming queue elements. I was able to create the
private/public key pair and update the zone file to reflect these values, but I
can't seem to get it to actually put the value in the header of outgoing emails.

I have been through the wiki as well as several other googled sources looking
for ideas, and the domain has SPF set up correctly.

Steps taken:

- created /var/qmail/control/domainkeys subdir (tried actual domain name, even
localhost.localdomain for fun)

- used dknewkey to create private/public key pair, changed ownership/permissions
on private key

- configured DNS with policy & selector records - verified via sourceforge,
yahoo, & skylist
Note: the domain I'm working on is agroupmail.com. I had to temporarily
(hopefully) disable the dk policy & selector entries in DNS until I can figure
out how to actually get the messages signed - otherwise, Yahoo will completely
reject all messages since it will be expecting the specified public key in the
email header.

- updated tcp.smtp with proper DKSIGN value and ran qmailctl cdb (tried both
with % and with absolute path for single domain)

Is there an error log somewhere that would show DKSIGN failing? Any ideas?

Getting the necessary DNS domainkey entries happening is not the problem - I
simply need to get Qmail to insert the key specified in tcp.smtp's DKSIGN
parameter into the header. Has anyone gotten this to work? If so, did you have
to take any special steps to get outgoing messages signed?



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

[qmailtoaster] DKSIGN help

[curt . qt]

Has anyone had any luck getting QT to sign outgoing messages with Domainkeys? I
read somewhere in the wiki that "domainkeys was broken",  but the instructions
regarding the issue point to incoming queue elements. I was able to create the
private/public key pair and update the zone file to reflect these values, but I
can't seem to get it to actually put the value in the header of outgoing emails.

I have been through the wiki as well as several other googled sources looking
for ideas, and the domain has SPF set up correctly.

Steps taken:

- created /var/qmail/control/domainkeys subdir (tried actual domain name, even
localhost.localdomain for fun)

- used dknewkey to create private/public key pair, changed ownership/permissions
on private key

- configured DNS with policy & selector records - verified via sourceforge,
yahoo, & skylist
Note: the domain I'm working on is agroupmail.com. I had to temporarily
(hopefully) disable the dk policy & selector entries in DNS until I can figure
out how to actually get the messages signed - otherwise, Yahoo will completely
reject all messages since it will be expecting the specified public key in the
email header.

- updated tcp.smtp with proper DKSIGN value and ran qmailctl cdb (tried both
with % and with absolute path for single domain)

Is there an error log somewhere that would show DKSIGN failing? Any ideas?

Getting the necessary DNS domainkey entries happening is not the problem - I
simply need to get Qmail to insert the key specified in tcp.smtp's DKSIGN
parameter into the header. Has anyone gotten this to work? If so, did you have
to take any special steps to get outgoing messages signed?



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

Re: [qmailtoaster] Outgoing Domainkeys

[curt . qt]

I am aware that the entries are not active. For starters, the domain I'm trying
to get dk working on is agroupmail.com. I had to temporarily (hopefully) disable
the dk policy & selector entries in DNS until I can figure out how to actually
get the messages signed - otherwise, Yahoo will completely reject all messages
since it will be expecting the specified public key in the email header.

I have been through the wiki as well as several other googled sources looking
for ideas, and the domain has SPF set up correctly.

As I said, getting the necessary DNS domainkey entries happening is not the
problem - I simply need to get Qmail to insert the key specified in tcp.smtp's
DKSIGN. Has anyone gotten this to work?

> [EMAIL PROTECTED] wrote:
>> Has anyone had any luck getting QT to sign outgoing messages with Domainkeys?
> Yup, I had
>> I read somewhere in the wiki that "domainkeys was broken",  but the
>> instructions
>> regarding the issue point to incoming queue elements. I was able to create 
>> the
>> private/public key pair and update the zone file to reflect these values, but
>> I
>> can't seem to get it to actually put the value in the header of outgoing
>> emails.
>>
>> Steps taken:
>> created /var/qmail/control/domainkeys subdir (tried actual domain name, even
>> localhost.localdomain for fun)
>> used dknewkey to create private/public key pair, changed 
>> ownership/permissions
>> on private key
>> configured DNS with policy & selector records - verified via sourceforge,
>> yahoo,
>> & skylist
>>
> the instruction for creating domainkeys is in here
> http://wiki.qmailtoaster.com/index.php/Domainkeys
> have you check them on http://www.dnsstuff.com/ ?
> on the hostname test column
> choose TXT type and enter the policy and selector records
> I get this output
>
> *No TXT records exist for _domainkey.agroup.com, and _domainkey.agroup.com 
> does
> not exist.* [Neg TTL=1800 seconds]
>
> have you tried spf for verification?
> it simple and qmt support it also. All you have to do is add spf records
> on you dns zone.
> for details and wizard creating spf record, you can go to openspf.org
> and maybe join their milist to consult
>> updated tcp.smtp with proper DKSIGN value (tried both with % and with 
>> absolute
>> path for single domain)
>>
>> Is there an error log somewhere that would show DKSIGN failing? Any ideas?
>>
>>
>
>
> -
>  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] Outgoing Domainkeys

[curt . qt]

Has anyone had any luck getting QT to sign outgoing messages with Domainkeys? I
read somewhere in the wiki that "domainkeys was broken",  but the instructions
regarding the issue point to incoming queue elements. I was able to create the
private/public key pair and update the zone file to reflect these values, but I
can't seem to get it to actually put the value in the header of outgoing emails.

Steps taken:
created /var/qmail/control/domainkeys subdir (tried actual domain name, even
localhost.localdomain for fun)
used dknewkey to create private/public key pair, changed ownership/permissions
on private key
configured DNS with policy & selector records - verified via sourceforge, yahoo,
& skylist
updated tcp.smtp with proper DKSIGN value (tried both with % and with absolute
path for single domain)

Is there an error log somewhere that would show DKSIGN failing? Any ideas?


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

Re: [qmailtoaster] Bayes gone wild

[curt . qt]

>> I recently had a very odd problem crop up - for some reason, BAYES_99 is
>> being
>> scored on every single incoming message, including messages sent from
>> myself
>> from an outside server which were absolutely clean. Keep in mind that
>> until now,
>> bayes filtering has been perfect and nothing (that I know of) has changed
>> in the
>> system.
>>
>> My first thought was that maybe bayes_seen or bayes_toks had been
>> corrupted, so
>> I did a "qmailctl stop" and restored them from a week-old backup. After
>> restarting, the problem persisted.
>>
>> The next step was wiping and rebuilding the bayes db manually using ham &
>> spam
>> folders with over 200 messages each - still, everything tagged with
>> BAYES_99.
>>
>> In an act of desperation, I did a "sa-learn --clear". At this point,
>> spamassassin --lint -D reports that there is no database to tie to, but
>> after
>> restarting qmail & spamassassin, messages continue to get tagged with a
>> BAYES_99
>> even though the db obviously doesn't contain the minimum 200 spam & ham to
>> be
>> active. The only cure I can find at the moment is to either re-score
>> BAYES_99 to
>> 0 in local.cf, or set use_bayes 0. (I did the latter)
>>
>> Does anyone have any idea what could be going on here?
>
> You didn't by chance upgrade to the new spamassassin did you?
> You may also post this on the spamassassin list. You may get some better
> answers there.
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

I did upgrade to 3.1.8-1.3.7 on 3/18, but everything functioned perfectly for
weeks after the upgrade.

BTW, what is the spamassassin list? The only one I could find was
spamassassin.apache.org which only seems to contain announcements about new
releases.


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

[qmailtoaster] Bayes gone wild

[curt . qt]

I recently had a very odd problem crop up - for some reason, BAYES_99 is being
scored on every single incoming message, including messages sent from myself
from an outside server which were absolutely clean. Keep in mind that until now,
bayes filtering has been perfect and nothing (that I know of) has changed in the
system.

My first thought was that maybe bayes_seen or bayes_toks had been corrupted, so
I did a "qmailctl stop" and restored them from a week-old backup. After
restarting, the problem persisted.

The next step was wiping and rebuilding the bayes db manually using ham & spam
folders with over 200 messages each - still, everything tagged with BAYES_99.

In an act of desperation, I did a "sa-learn --clear". At this point,
spamassassin --lint -D reports that there is no database to tie to, but after
restarting qmail & spamassassin, messages continue to get tagged with a BAYES_99
even though the db obviously doesn't contain the minimum 200 spam & ham to be
active. The only cure I can find at the moment is to either re-score BAYES_99 to
0 in local.cf, or set use_bayes 0. (I did the latter)

Does anyone have any idea what could be going on here?


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

[qmailtoaster] BAYES_99 always being triggered

[curt . qt]

I had a very odd problem crop up today - for some reason, BAYES_99 is being
scored on every single incoming message, including messages sent from myself
from an outside server which were absolutely clean.

My first thought was that maybe bayes_seen or bayes_toks had been corrupted, so
I did a "qmailctl stop" and restored them from a week-old backup. After
restarting, the problem persisted.

The next step was wiping and rebuilding the bayes db manually using ham & spam
folders with over 200 messages each - still, everything tagged with BAYES_99.

In an act of desperation, I did a "sa-learn --clear". At this point,
spamassassin --lint -D reports that there is no database to tie to, but after
restarting qmail & spamassassin, messages continue to get tagged with a BAYES_99
even though the db obviously doesn't contain the minimum 200 spam & ham to be
active. The only cure I can find at the moment is to either re-score BAYES_99 to
0 in local.cf, or set use_bayes 0. (I did the latter)

Does anyone have any idea what could be going on here?


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