Duncan Sterling wrote:
Jake Vickers wrote:
Duncan Sterling wrote:
Greetings All,
Quick question: in the interest of redundancy and quick disaster
recovery, would it not make sense while running a production toaster
to:
1) Build an identically configured backup toaster
2) Run (Jakes?)
Hello John,
just replace /var/qmail/control/servercert.pem with your certificate and
restart qmail-toaster. Certificates for IMAPS/POP3S and SMTP/TLS are using this
certificate.
Johannes
Tek Support schrieb:
Hi, now that I'm strongly considering using port 587 for my staff, I
thought it
Thanks, I'll do that, and do I need a 3party signed cert (like HTTPS)?
Thanks
John
On Tue, Aug 26, 2008 at 1:41 AM, Johannes Weberhofer, Weberhofer GmbH
[EMAIL PROTECTED] wrote:
Hello John,
just replace /var/qmail/control/servercert.pem with your certificate and
restart qmail-toaster.
Tek Support wrote:
Thanks, I'll do that, and do I need a 3party signed cert (like HTTPS)?
The reason you're getting the other error is because the cert is not
signed by a trusted authority. If you don't have it signed by a trusted
authority, you'll be getting the same error unless you
You could also look at the qmail replication script which you can find in
the wiki. It automates the domain sync. We have 2 identical servers
running the script which runs every 15 minutes, so when if our primary
fails, we change ip's on the backup and we are back up and running with at
most 15
Taking a view into perl packages (classes) needed by spamassassin
(qmail-toaster package), I saw that there are a script that install the
classes using CPAN.
I discovered that CPAN installed packages goes into a diferent directory
that distro ones.
The workaround (solution) I found is rename
I can't upgrade the spamassassin in qtp-newmodel.
find dependency with perl module problem
. one module (xxx:ssl)can't complete the test.
what should i do?
thanks a lot~
On 8/26/08, Tek Support [EMAIL PROTECTED] wrote:
So for a 64bit system is qtp-newmodel worth trying? I'm a bit scared
Yep, seems like the same exact series of problems I ran into as well.
I ended up manually having to upgrade everything, including
dependencies, with Eric's help to isolate some of the issues.
Harry
On Aug 26, 2008, at 3:45 AM, gum trolium wrote:
I can't upgrade the spamassassin in
Let me try to explain something. The problems with upgrading spamassassin
lately have nothing to do with qtp-newmodel. These issues are the result of
changes in spamassassin packaging, and occur even when updating 'manually'.
qtp-newmodel has the advantage of letting you know that there's a
Absolutely. See my reply to Harry.
There have been several successful upgrades on 64bit machines using
qtp-newmodel. You might have some issues with dependencies for spamassassin,
but that has nothing to do with using qtp-newmodel or not.
Jake and I have tried to include these SA dependencies in
There are some more detailed instructions here:
http://wiki.qmailtoaster.com/index.php/Certificate
On 25-Aug-08, at 10:39 PM, Tek Support wrote:
Hi, now that I'm strongly considering using port 587 for my staff, I
thought it also a wise choice to make them use TLS. I am in my
thunderbird
gum trolium wrote:
I can't upgrade the spamassassin in qtp-newmodel.
Then you probably can't upgrade spamassassin manually either.
find dependency with perl module problem
. one module (xxx:ssl)can't complete the test.
what should i do?
Is this a build dependency or an install dependency?
Thanks for posting your solution, Arcos (or whatever your name is!). This
definitely clarifies things a bit.
ArcosCom Linux User wrote:
Taking a view into perl packages (classes) needed by spamassassin
(qmail-toaster package), I saw that there are a script that install the
classes using CPAN.
Tek Support wrote:
Hi all, recently I had asked if there was a reason to use the port 587
if I installed spamdyke (because spamdyke authenticated my dynamic
users and ignored the rbls). Well, maybe I've found something that
would still require me to use 587 instead of port 25. I would
Ok, I'll see if importing will work also. But initially it said I
needed to import it, and I did that, the error I get now is that the
name doesn't match. So if I create a new cert with the correct name,
then obviously import, that should be the end of the errors. So once
I get my staff's
Hi Eric, thanks for the quick reply. The reason I think it's doing
outbound scanning is a specific line in the header, maybe you can shed
some light on it. In an email sent from mydomain to my yahoo accout
these are in the headers. The line I'm interrested in, is possibly
added by yahoo, but I
That's great, that's exactly what I was looking for, thank you for the link.
Thanks
John
On Tue, Aug 26, 2008 at 9:07 AM, dnk [EMAIL PROTECTED] wrote:
There are some more detailed instructions here:
http://wiki.qmailtoaster.com/index.php/Certificate
On 25-Aug-08, at 10:39 PM, Tek
Yes, that should do it.
FWIW, you can use cacert.org to sign certificates for free. Unfortunately,
cacert.org isn't generally recognized (yet) at an authoritative CA. You can,
however, have your uses import cacert's root certificate, then any
certificate that you have cacert sign will be
Eric Shubert wrote:
Yes, that should do it.
FWIW, you can use cacert.org to sign certificates for free. Unfortunately,
cacert.org isn't generally recognized (yet) at an authoritative CA. You can,
however, have your uses import cacert's root certificate, then any
certificate that you have cacert
Simscan does scan outbound mail, but scans only for viruses (clamav), not
spam (spamassassin). This is consistent with the message you're seeing.
Adding the DK signature would (have to) happen after this scan.
Tek Support wrote:
Hi Eric, thanks for the quick reply. The reason I think it's
I got this from qtp-newmodel:
qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.14
qtp-build-rpms - see
/mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log
inside the build-recent.log:
Installing spamassassin-toaster-3.2.5-1.3.14 in the sandbox ...
error: Failed
I check the HTML::Parser again:
cpan[1] install HTML::Parser
CPAN: Storable loaded ok (v2.13)
Going to read /root/.cpan/Metadata
Database was generated on Tue, 26 Aug 2008 23:02:52 GMT
HTML::Parser is up to date (3.56).
On Wed, Aug 27, 2008 at 12:37 PM, gum trolium [EMAIL PROTECTED] wrote:
Don't use CPAN to update your perl modules. (I think I mentioned that in a
recent post).
Try this:
# yum install perl-HTML-Parser
If it doesn't find a new enough version (or no version at all), configure
your yum to use the RPMforge repository. For instructions on how to do that,
you can search
Dear Eric,
I change to install the repo and yum install perl-HTML-Parser
After complete with no error,
I go to qtp-newmodel again with new sandbox.
and it stopped with following this time:
Starting to build the binary rpms ...(pizza anyone?)
qtp-build-rpms v0.3
qtp-remove-pkgs v0.3.1
*** glibc
As you said (would have to), how do I determine the order they are
run? Is it simply that the DKIM header is added on top of the
simscan, thus simscan first and dkim 2nd?
Thanks
John
On Tue, Aug 26, 2008 at 2:14 PM, Eric Shubert [EMAIL PROTECTED] wrote:
Simscan does scan outbound mail, but
Good plan, I'll see if the Mac program (Mail) will accept cacert.org
root cert and see what we get.
Thanks a lot,
John
On Tue, Aug 26, 2008 at 12:58 PM, Eric Shubert [EMAIL PROTECTED] wrote:
Yes, that should do it.
FWIW, you can use cacert.org to sign certificates for free. Unfortunately,
26 matches
Mail list logo
