Re: [qmailtoaster] Error receiving mail from 1 domain

[Peter Peltonen]

Hi,

On Tue, Feb 7, 2012 at 8:30 AM, Amit  wrote:

> :(*554, 'Your email was rejected
> because it contains the Heuristics.Phishing.Email.SpoofedDomain virus*')|
>
>
> 
>
> Normal mails are receiving properly but only attachment are getting
> blocked. How do I resolve the same.
>

Isn't the error quite obvious: The email the user tries to send contains an
attachment with a virus. Which is a bad thing and is therefore blocked.

So the answer is to not send attachments that contain viruses...?

Regards,
Peter

[qmailtoaster] check user 5.1.1 error

[nishant amin]

hi all
after a reboot i am encountering the following error on my qmailtoaster
mail server (centos 5.7)

Message not sent. Server replied: Unknown response
511 sorry, can't find a valid MX for sender domain (#5.1.1 - chkuser)

please point me in the right direction

Re: [qmailtoaster] check user 5.1.1 error

[Peter Peltonen]

Hi,

On Tue, Feb 7, 2012 at 1:30 PM, nishant amin  wrote:
> hi all
> after a reboot i am encountering the following error on my qmailtoaster mail
> server (centos 5.7)
>
> Message not sent. Server replied: Unknown response
> 511 sorry, can't find a valid MX for sender domain (#5.1.1 - chkuser)
>
> please point me in the right direction

This problem means:

You do not have an MX record set in your DNS for the domain you are
trying to send email from.

So fix the DNS for this domain and all should be well.

And please next time consider googling the error message first, as
this is the same information you have found quicker that way.

Regards,
Peter

-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.
 
  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] check user 5.1.1 error

[nishant amin]

hi
i know that its a dns error.and i did ask google.
any way i have sorted it out.it was a misconfigured dns server



On Tue, Feb 7, 2012 at 3:09 PM, Peter Peltonen wrote:

> Hi,
>
> On Tue, Feb 7, 2012 at 1:30 PM, nishant amin  wrote:
> > hi all
> > after a reboot i am encountering the following error on my qmailtoaster
> mail
> > server (centos 5.7)
> >
> > Message not sent. Server replied: Unknown response
> > 511 sorry, can't find a valid MX for sender domain (#5.1.1 - chkuser)
> >
> > please point me in the right direction
>
> This problem means:
>
> You do not have an MX record set in your DNS for the domain you are
> trying to send email from.
>
> So fix the DNS for this domain and all should be well.
>
> And please next time consider googling the error message first, as
> this is the same information you have found quicker that way.
>
> Regards,
> Peter
>
>
> -
> Qmailtoaster is sponsored by Vickers Consulting Group (
> www.vickersconsulting.com)
>Vickers Consulting Group offers Qmailtoaster support and installations.
>  If you need professional help with your setup, contact them today!
>
> -
> Please visit qmailtoaster.com for the latest news, updates, and
> packages.
>
>  To unsubscribe, e-mail:
> qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail:
> qmailtoaster-list-h...@qmailtoaster.com
>
>
>

[qmailtoaster] qtp-newmodel breaks on SpamAssassin install on CentOS 5.7

[Angus McIntyre]

I've worked past most of my previous problems trying to install QmailToaster 
(many of which seem to have been associated with making changes to the CentOS 
base install - apparently, Honey Badger don't like that). However, I've come up 
against another blocker.

While building spamassassin-toaster, the build errors out with:

+ chmod 755 '/var/tmp/spamassassin-toaster-root/usr/bin/*' 
chmod: cannot access `/var/tmp/spamassassin-toaster-root/usr/bin/*': No 
such file or directory error: 
Bad exit status from /var/tmp/rpm-tmp.28381 (%install) 

Checking on the sandbox, I see that there is indeed nothing at that path.

I see that this question has been asked before, but - as far as I can tell from 
the mailing lists - there's no resolution to the issue.

Looking at the full log, there are no obvious build errors (a few deprecated 
warnings, but that's all).

My guess is that this might be because I have done a source install of Perl to 
get a current version of Perl.

Is there any way that I can work around this? Can I skip the 
spamassassin-toaster component and then build it manually somehow later? Can I 
retrofit a toaster built without SA with a straight source-install of 
SpamAssassin?

Failing that, does anyone know of a source for a current Perl RPM?  (I know 
that we're not supposed to "play the numbers game" with CentOS", but Perl 5.8.8 
is not even maintained any longer). My experience has been that a lot of 
problems with QMT - and believe me, I _have_ had a lot of problems with QMT - 
can be resolved by doing things the CentOS way, with yum installs rather than 
source builds.

Thanks for any help,

Angus
-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.

  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] qtp-newmodel breaks on SpamAssassin install on CentOS 5.7

[Peter Peltonen]

Hi,

On Tue, Feb 7, 2012 at 4:00 PM, Angus McIntyre  wrote:
> My guess is that this might be because I have done a source install of Perl 
> to get a current version of Perl.

This is probably the cause, yes.


> Is there any way that I can work around this? Can I skip the 
> spamassassin-toaster component and then build it manually somehow later? Can 
> I retrofit a toaster built without SA with a straight source-install of 
> SpamAssassin?

I don't know the answer for this...


> Failing that, does anyone know of a source for a current Perl RPM?  (I know 
> that we're not supposed to "play the numbers game" with CentOS", but Perl 
> 5.8.8 is not even maintained any longer). My experience has been that a lot 
> of problems with QMT - and believe me, I _have_ had a lot of problems with 
> QMT - can be resolved by doing things the CentOS way, with yum installs 
> rather than source builds.

You should always stick to the RPMs provided by the CentOS repos.
Otherwise you will break things eventually.

Have you checked:

http://wiki.qmailtoaster.com/index.php/CentOS_5_QmailToaster_Install#cnt50-perl.sh_and_cnt5064-perl.sh

Perhaps the cnt50-perl.sh script could help you out?

Best,
Peter

-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.

  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Error receiving mail from 1 domain

[Bharath Chari]

On Tuesday 07 February 2012 04:19 PM, Peter Peltonen wrote:


Hi,

On Tue, Feb 7, 2012 at 8:30 AM, Amit > wrote:


:(*554, 'Your email was rejected
because it contains the Heuristics.Phishing.Email.SpoofedDomain
virus*')|


Normal mails are receiving properly but only attachment are
getting blocked. How do I resolve the same.


Isn't the error quite obvious: The email the user tries to send 
contains an attachment with a virus. Which is a bad thing and is 
therefore blocked.


So the answer is to not send attachments that contain viruses...?

As I understand, this is triggered off by many "legitimate" marketing 
emails where the underlying hyperlink does not match the text displayed 
eg : http://www.example.com actually links to 
http://www.someotherdomain.com - a classic phishing ploy.


It is possible to turn off checking for Phishing in the clamav 
configuration, but I wouldn't recommend that. In this case, I'd much 
rather live with false positives.


Bharath

[qmailtoaster] CentOS and Perl versions

[Dan McAllister]

If you want "bleeding edge" support for packages, you shouldn't be 
running CentOS because that runs counter to the very principles of that 
Linux Distribution.


Pick Ubuntu, Fedora, or another frequently updated release - but be 
aware that constant updates means constant repair of new mis-matches in 
software.


NOTE: Its not fair to say that Perl 5.8.8 is "unmaintained" -- Perl 5.8 
is the "supported" version of Perl for RHEL 5 (the CentOS upline) will 
not likely upgrade (heck, CentOS 6 only takes Perl to 5.10) -- and it 
will continue to be "maintained" (by Red Hat, if no one else) until 2017!


Please remember that Perl is a language, not an application... if you're 
trying to get the latest and greatest Perl add-ins (libraries, etc), 
know that many of them can be successfully added into Perl 5.8. Also, I 
believe that there is a regular update release -- so taking on "keep up 
with Perl" would be an endless project at this point.


ALL OF THAT being said, I can say that my experience with building QMT 
is that my most common mistake is that I fail to disengage SE-Linux 
(which is on by default).


Dan
IT4SOHO

On 2/7/2012 9:48 AM, Peter Peltonen wrote:

Hi,

On Tue, Feb 7, 2012 at 4:00 PM, Angus McIntyre  wrote:

My guess is that this might be because I have done a source install of Perl to 
get a current version of Perl.

This is probably the cause, yes.



Is there any way that I can work around this? Can I skip the 
spamassassin-toaster component and then build it manually somehow later? Can I 
retrofit a toaster built without SA with a straight source-install of 
SpamAssassin?

I don't know the answer for this...



Failing that, does anyone know of a source for a current Perl RPM?  (I know that we're not 
supposed to "play the numbers game" with CentOS", but Perl 5.8.8 is not even 
maintained any longer). My experience has been that a lot of problems with QMT - and believe 
me, I _have_ had a lot of problems with QMT - can be resolved by doing things the CentOS way, 
with yum installs rather than source builds.

You should always stick to the RPMs provided by the CentOS repos.
Otherwise you will break things eventually.

Have you checked:

http://wiki.qmailtoaster.com/index.php/CentOS_5_QmailToaster_Install#cnt50-perl.sh_and_cnt5064-perl.sh

Perhaps the cnt50-perl.sh script could help you out?

Best,
Peter

-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
 Vickers Consulting Group offers Qmailtoaster support and installations.
   If you need professional help with your setup, contact them today!
-
  Please visit qmailtoaster.com for the latest news, updates, and packages.

   To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
  For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Error receiving mail from 1 domain

[Dan McAllister]

My only comment is to say that, despite the fact that you might really 
WANT that marketing e-mail, the fact is that if they're doing what clam 
says they're doing (like the example below), then at best they're being 
deceitful... it may be a benign deceit, but it is deceit never the less.


Remember, about 20% of virus infections occur because the AV program 
pops up and says "Danger Will Robinson" and good old Will says "Shut up, 
Robot"... just before the alien takes him hostage.


That is, they're told it's dangerous, but they click "install anyway" or 
"allow" or whatever... and then they get mad that their AV didn't 
protect them... sigh


Really people, if we assume that every "hit" on a SPAM blocker or 
AntiVirus is a false positive, then why run one at all?


Dan McAllister
IT4SOHO

On 2/7/2012 11:01 AM, Bharath Chari wrote:

On Tuesday 07 February 2012 04:19 PM, Peter Peltonen wrote:


Hi,

On Tue, Feb 7, 2012 at 8:30 AM, Amit > wrote:


:(*554, 'Your email was
rejected because it contains the
Heuristics.Phishing.Email.SpoofedDomain virus*')|


Normal mails are receiving properly but only attachment are
getting blocked. How do I resolve the same.


Isn't the error quite obvious: The email the user tries to send 
contains an attachment with a virus. Which is a bad thing and is 
therefore blocked.


So the answer is to not send attachments that contain viruses...?

As I understand, this is triggered off by many "legitimate" marketing 
emails where the underlying hyperlink does not match the text 
displayed eg : http://www.example.com actually links to 
http://www.someotherdomain.com - a classic phishing ploy.


It is possible to turn off checking for Phishing in the clamav 
configuration, but I wouldn't recommend that. In this case, I'd much 
rather live with false positives.


Bharath

Re: [qmailtoaster] CentOS and Perl versions

[Angus McIntyre]

Dan McAllister wrote:
> If you want "bleeding edge" support for packages, you shouldn't be
> running CentOS because that runs counter to the very principles of that
> Linux Distribution.

So I have discovered.

Yes, the fault is mine because I didn't read the label on the tin that
said "Just do it our way and everyone will be happy". I'm actually
upgrading from a CentOS 5.2 system which - not knowing any better - I
filled with a whole raft of source-installed software. That ran quite
happily for years, with no mysterious conflicts, so I was fooled into
thinking that what I was doing was OK. My experience of trying to install
QMT on my new box has set me straight on that score in no uncertain terms.

> NOTE: Its not fair to say that Perl 5.8.8 is "unmaintained" -- Perl 5.8
> is the "supported" version of Perl for RHEL 5 (the CentOS upline) will
> not likely upgrade (heck, CentOS 6 only takes Perl to 5.10) -- and it
> will continue to be "maintained" (by Red Hat, if no one else) until 2017!

"unmaintained" is perhaps the wrong word, but it's end-of-life'd and
unsupported by the Perl porters. By any standards, it is a very very old
Perl.

Anyway, this is somewhat off-topic for QMT, so perhaps the lesson to take
home is:

Do things the CentOS way, or CentOS will _hurt_ you.

and this applies to installing QMT as much as (or more than) doing
anything else on CentOS.

Thanks for your help,

Angus


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.
 
  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

RE: [qmailtoaster] Re: Migrating to new server

[John Raley]

Natalio, thanks for the pointers. Your method is the one I used. On the 
Exchange side this is what I did :
Added an internal domain (domain.local) for a secondary email address. Added 
the email domain on Exchange as an Internal Relay and configured an SMTP 
Connector to the Qmail server. This way Exchange 2010 will forward any email it 
receives that it does not have a mailbox for to the Qmailtoaster server.

One fun fact I found out the hard way, do not remove mailboxes in Exchange! 
This will delete AD accounts with it. That is what I get for testing in a 
production environment.

From: Natalio Gatti [mailto:nga...@gmail.com]
Sent: Monday, February 06, 2012 2:47 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Migrating to new server


On Mon, Feb 6, 2012 at 4:53 PM, Eric Shubert 
mailto:e...@shubes.net>> wrote:
On 02/06/2012 12:03 PM, John Raley wrote:
How did you manage this?
I have a UTM device in front of both servers. It does call-out to verify the
account exists. I am guessing when the Qmail server says the account doesn't
exist, it move to the next email server.

Just some ideas:
1) Create a second domain in exchange, as an alias domain. Every exchange user 
will have two addresses (user@domain and user@secondarydomain).
2) Create an smtproute in your qmail box to forward all secondarydomain to your 
exchange box
3) Create forwards for the accounts you already have migrated, so as to forward 
the migrated user mail to the secondary domain.

This could solve one problem. All users in the qmail box can send mails to 
users in exchange box. Maybe you could do something similar to the reverse 
problem. I do not know if you are going to need a SMTP Connector in your 
exhchange box.

Salutti,

Natalio.

Re: [qmailtoaster] Re: Migrating to new server

[Natalio Gatti]

Glad to see that it helped.
I used that procedure in a similar migration. It is not the best method,
but it allowed me to migrate one account at a time. It was an exchange
2003, wich includes the SMTP Connector. I thought that exchange 2010 did
not include one.
Best of lucks in the microsoft world...

On Tue, Feb 7, 2012 at 6:35 PM, John Raley  wrote:

>  Natalio, thanks for the pointers. Your method is the one I used. On the
> Exchange side this is what I did :
>
> Added an internal domain (domain.local) for a secondary email address.
> Added the email domain on Exchange as an Internal Relay and configured an
> SMTP Connector to the Qmail server. This way Exchange 2010 will forward any
> email it receives that it does not have a mailbox for to the Qmailtoaster
> server. 
>
> ** **
>
> One fun fact I found out the hard way, do not remove mailboxes in
> Exchange! This will delete AD accounts with it. That is what I get for
> testing in a production environment. 
>
> ** **
>
> *From:* Natalio Gatti [mailto:nga...@gmail.com]
> *Sent:* Monday, February 06, 2012 2:47 PM
> *To:* qmailtoaster-list@qmailtoaster.com
> *Subject:* Re: [qmailtoaster] Re: Migrating to new server
>
> ** **
>
> ** **
>
> On Mon, Feb 6, 2012 at 4:53 PM, Eric Shubert  wrote:
>
> On 02/06/2012 12:03 PM, John Raley wrote:
>
> How did you manage this?
>
> I have a UTM device in front of both servers. It does call-out to verify
> the
> account exists. I am guessing when the Qmail server says the account
> doesn't
> exist, it move to the next email server.
>
> ** **
>
> Just some ideas: 
>
> 1) Create a second domain in exchange, as an alias domain. Every exchange
> user will have two addresses (user@domain and user@secondarydomain).
>
> 2) Create an smtproute in your qmail box to forward all secondarydomain to
> your exchange box
>
> 3) Create forwards for the accounts you already have migrated, so as to
> forward the migrated user mail to the secondary domain.
>
> ** **
>
> This could solve one problem. All users in the qmail box can send mails to
> users in exchange box. Maybe you could do something similar to the reverse
> problem. I do not know if you are going to need a SMTP Connector in your
> exhchange box.
>
> ** **
>
> Salutti, 
>
> ** **
>
> Natalio.
>

[qmailtoaster] Tracking qmailadmin logins?

[Casey Price]

One of my customers was asking if we had any way of tracking logins to 
qmailadmin for their domain...


The only thing I could think of is checking the access logs for httpd. 
If I remember correctly, vuserinfo only shows the last IP, time & date a 
user authenticated, but that doesn't necessarily imply they logged in 
via qmailadmin.


Any way of tracking logins, or determining who has logged in via qmailadmin?

Thanks,

--
Casey Price

Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com 

Follow us on Twitter 
Find us on Facebook 

[qmailtoaster] Re: Tracking qmailadmin logins?

[Eric Shubert]

On 02/07/2012 02:56 PM, Casey Price wrote:

One of my customers was asking if we had any way of tracking logins to
qmailadmin for their domain...

The only thing I could think of is checking the access logs for httpd.
If I remember correctly, vuserinfo only shows the last IP, time & date a
user authenticated, but that doesn't necessarily imply they logged in
via qmailadmin.

Any way of tracking logins, or determining who has logged in via qmailadmin?

Thanks,



apache logs show access, but not which domain or user. I think you're 
pretty much correct about vuserinfo too, but that shows various things 
depending on which service was authenticating, and doesn't appear to 
update when authenticating for qmailadmin.


Short answer: no.

--
-Eric 'shubes'


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Tracking qmailadmin logins?

[Casey Price]

On 2/7/12 3:41 PM, Eric Shubert wrote:

On 02/07/2012 02:56 PM, Casey Price wrote:

One of my customers was asking if we had any way of tracking logins to
qmailadmin for their domain...

The only thing I could think of is checking the access logs for httpd.
If I remember correctly, vuserinfo only shows the last IP, time & date a
user authenticated, but that doesn't necessarily imply they logged in
via qmailadmin.

Any way of tracking logins, or determining who has logged in via 
qmailadmin?


Thanks,



apache logs show access, but not which domain or user. I think you're 
pretty much correct about vuserinfo too, but that shows various things 
depending on which service was authenticating, and doesn't appear to 
update when authenticating for qmailadmin.


Short answer: no.
Damn. I figured that was the case, but was hoping someone might know of 
a way.


The customer is wanting to know if we can track who logs in, date/time, 
ip, and changes made...from the sounds of it, there isn't a mechanism 
for doing this as of yet - however it does seem to me that this could be 
a useful functionality (debugging, security-related, etc). Granted, 
tracking all the changes qmailadmin makes and logging it could lead to 
some huge logs, but it would be nice to have the ability to do so.


Going even further, it would be cool if somewhere in the admin toaster 
you could turn on "accounting" or domain logging on a per domain-basis, 
and maybe have a few configuration parameters, such as the size of logs, 
how long to keep them, etc. Maybe that is reaching too far, but its an 
idea at that.



Casey Price

Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com 

Follow us on Twitter 
Find us on Facebook 

[qmailtoaster] Re: CentOS and Perl versions

[Eric Shubert]

On 02/07/2012 10:29 AM, Angus McIntyre wrote:

Anyway, this is somewhat off-topic for QMT, so perhaps the lesson to take
home is:

 Do things the CentOS way, or CentOS will_hurt_  you.

and this applies to installing QMT as much as (or more than) doing
anything else on CentOS.



As Saint Ambrose is attributed to having first said (some time in the 
4th century AD), "When in Rome, do as the Romans do". One would do well 
to heed this advice in all of the various realms of *nix.


QMT has somewhat failed in this regard in the past (e.g. logging, init 
scripts). I hope that one day QMT may fall in line with the way distros 
have chosen to implement some common functionality. rsyslog and systemd 
look to me to be big improvements (although systemd is actually just 
catching up with daemontools if truth be told). While these new 
technologies are attractive, don't expect them to show up in QMT any 
time soon. In a couple years, perhaps. We've a long road to travel 
before that time comes. Stay tuned.


--
-Eric 'shubes'


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Dovecot 2.0.17

[Eric Shubert]

Rpms (i386 and x86_64 and source) for Dovecot 2.0.17 (current stable 
version) are available in the qtp repository for COS5.


NOTE: THESE HAVE NOT YET BEEN TESTED ON QMT. PLEASE READ RELEASE NOTES 
ON THE DOVECOT SITE THAT PERTAIN TO YOUR SITUATION BEFORE USING.


I've built them, and installed/upgraded them on test machines, but 
that's it so far. If someone can do some testing with them, we'd all be 
grateful.


To upgrade from a previous 2.0.x qtp release, simply:
# yum --enablerepo=qtp-CentOS update dovecot
That's all you should need to do. (Distro-specific repos are not enabled 
by default.)


If you're interested in giving dovecot a try, you can install it with 
yum in a similar fashion. Please follow the instructions on the wiki 
though, as there are several things you need to do when converting from 
courier.


Thanks for your participation.

--
-Eric 'shubes'


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] [Off-Topic] Need recommendations for cloud servers.

[P.V.Anthony]

Hi,

Currently I am co-locating my servers at a data center. I was thinking 
of moving onto cloud servers.


I am thinking that it would save me money and headache of maintaining 
the hardware.


Thinking of Voxel.com.

Currently I am very confused. Not sure if I should even use cloud 
servers. If I should use cloud, then which vendor?


I need advice.

Please share your thoughts.

P.V.Anthony

-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Error receiving mail from 1 domain

[Bharath Chari]

On Tuesday 07 February 2012 10:29 PM, Dan McAllister wrote:
My only comment is to say that, despite the fact that you might really 
WANT that marketing e-mail, the fact is that if they're doing what 
clam says they're doing (like the example below), then at best they're 
being deceitful... it may be a benign deceit, but it is deceit never 
the less.


I have seen some really ironical ones. My bank periodically sends me 
mail warning me against Phishing - Unfortunately the people who design 
the mail, have not the faintest idea what it means - so happily create 
spoofed links in the mail (ostensibly to make it prettier). And needless 
to say, ClamAV spits the mail out :).


Bharath


Remember, about 20% of virus infections occur because the AV program 
pops up and says "Danger Will Robinson" and good old Will says "Shut 
up, Robot"... just before the alien takes him hostage.


That is, they're told it's dangerous, but they click "install anyway" 
or "allow" or whatever... and then they get mad that their AV didn't 
protect them... sigh


Really people, if we assume that every "hit" on a SPAM blocker or 
AntiVirus is a false positive, then why run one at all?


Dan McAllister
IT4SOHO

[qmailtoaster] Reg:Server

[Raja Mani]

Dear All,



I getting a lot of spam mails from my qmail server on laster
2days.Its working before 2days why its happening.How to check my qmail
server.Spam control services are running or not.


-Rajamani

Re: [qmailtoaster] Reg:Server

[Carlos Herrera Polo]

You can check mail headers and search the line : spamassasin, if you
can see.. Then your spam filter is running.
You have spamdyke in your box ?

2012/2/7, Raja Mani :
> Dear All,
>
>
>
> I getting a lot of spam mails from my qmail server on laster
> 2days.Its working before 2days why its happening.How to check my qmail
> server.Spam control services are running or not.
>
>
> -Rajamani
>

-- 
Enviado desde mi dispositivo móvil

-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.

  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Question Regarding Internal Relay

[Domnick Eger]

I want to bypass the check so I can have my internal servers relay messages 
from sendmail to qmail. I set the following, but can't seems to get it too 
work. Am I missing something ?

127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",RBLSMTPD="",NOP0FCHECK="1"
10.1.5.:allow,RELAYCLIENT="",SENDER_NOCHECK="1"
:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"

[qmailtoaster] RE: Question Regarding Internal Relay

[Domnick Eger]

The specific error is

554 qmail-dk: Cannot sign message due to invalid message syntax. (#5.3.0)

When I do a telnet test from that server, is there a way to exclude an ip block 
from a domain key check ?

From: Domnick Eger [mailto:de...@cobercafe.net]
Sent: Tuesday, February 07, 2012 10:10 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] Question Regarding Internal Relay

I want to bypass the check so I can have my internal servers relay messages 
from sendmail to qmail. I set the following, but can't seems to get it too 
work. Am I missing something ?

127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",RBLSMTPD="",NOP0FCHECK="1"
10.1.5.:allow,RELAYCLIENT="",SENDER_NOCHECK="1"
:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"

[qmailtoaster] Re: Question Regarding Internal Relay

[Eric Shubert]

On 02/07/2012 10:23 PM, Domnick Eger wrote:

The specific error is

554 qmail-dk: Cannot sign message due to invalid message syntax. (#5.3.0)

When I do a telnet test from that server, is there a way to exclude an
ip block from a domain key check ?

*From:*Domnick Eger [mailto:de...@cobercafe.net]
*Sent:* Tuesday, February 07, 2012 10:10 PM
*To:* qmailtoaster-list@qmailtoaster.com
*Subject:* [qmailtoaster] Question Regarding Internal Relay

I want to bypass the check so I can have my internal servers relay
messages from sendmail to qmail. I set the following, but can’t seems to
get it too work. Am I missing something ?

127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",RBLSMTPD="",NOP0FCHECK="1"

10.1.5.:allow,RELAYCLIENT="",SENDER_NOCHECK="1"

:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"



Specific errors are informative. This one is indicative of a bug in the 
qmail-dk module which occurs occasionally.


I would remove use of qmail-dk entirely:
# cd /var/qmail/bin
# ln -sf qmail-queue.orig qmail-queue
# service qmail restart
Not sure if the restart is necessary or not, but it doesn't hurt.
This will effectively disable all domainkey processing.

Perhaps we should remove qmail-dk from the stock package, seeing that it 
has problems, and is being pretty much superceeded by dkim. Does anyone 
have any thoughts about this?


--
-Eric 'shubes'


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Question Regarding Internal Relay

[Domnick Eger]

I found that on a google search didn't think it was broken on qmail toaster 
since qmail rocks listed this as a solution.  

Sent from my iPhone

On Feb 7, 2012, at 10:55 PM, "Eric Shubert"  wrote:

> On 02/07/2012 10:23 PM, Domnick Eger wrote:
>> The specific error is
>> 
>> 554 qmail-dk: Cannot sign message due to invalid message syntax. (#5.3.0)
>> 
>> When I do a telnet test from that server, is there a way to exclude an
>> ip block from a domain key check ?
>> 
>> *From:*Domnick Eger [mailto:de...@cobercafe.net]
>> *Sent:* Tuesday, February 07, 2012 10:10 PM
>> *To:* qmailtoaster-list@qmailtoaster.com
>> *Subject:* [qmailtoaster] Question Regarding Internal Relay
>> 
>> I want to bypass the check so I can have my internal servers relay
>> messages from sendmail to qmail. I set the following, but can’t seems to
>> get it too work. Am I missing something ?
>> 
>> 127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",RBLSMTPD="",NOP0FCHECK="1"
>> 
>> 10.1.5.:allow,RELAYCLIENT="",SENDER_NOCHECK="1"
>> 
>> :allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"
>> 
> 
> Specific errors are informative. This one is indicative of a bug in the 
> qmail-dk module which occurs occasionally.
> 
> I would remove use of qmail-dk entirely:
> # cd /var/qmail/bin
> # ln -sf qmail-queue.orig qmail-queue
> # service qmail restart
> Not sure if the restart is necessary or not, but it doesn't hurt.
> This will effectively disable all domainkey processing.
> 
> Perhaps we should remove qmail-dk from the stock package, seeing that it has 
> problems, and is being pretty much superceeded by dkim. Does anyone have any 
> thoughts about this?
> 
> -- 
> -Eric 'shubes'
> 
> 
> -
> Qmailtoaster is sponsored by Vickers Consulting Group 
> (www.vickersconsulting.com)
>   Vickers Consulting Group offers Qmailtoaster support and installations.
> If you need professional help with your setup, contact them today!
> -
>Please visit qmailtoaster.com for the latest news, updates, and packages.
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 
> 
> 


-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.

  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: email account create date

[Pak Ogah]

On 02/06/12 13:10, Eric Shubert wrote:

On 02/05/2012 10:32 PM, Pak Ogah wrote:

Hi list,
Is there a way to find out when an email account created ?
I have look at account maildir folder but none of files can be used as
reference

- 



I don't know if the vpopmail database schema contains that or not. 
Probably should if it doesn't. You'd need to check.

No, it doesn't


The next best thing I can think of would be the date on the user's 
directory. The contents of that don't typically change much, unless 
the .qmail file is created or removed. It's no certain indication of 
when the account was create, but you know it's been around at least 
that long.

I have check it too but still it didn't provide the correct date
ps: is there a command hook on vpopmail/qmailadmin so that we can add a 
command when user created/deleted?



-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com