I actually don't have that much experience with Dovecot, but more than
Courier. I would vote in favor of using Dovecot for the following
reasons:
- It is part of the RHEL 4 distribution. It is already installed, and I
can trust the source. Patches are automatically available via up2date.
Hi,
I seem to be having a problem running fdr40-install-script.sh,
particularly at the qmail-toaster-1.03-1.3.5.src.rpm part of the
installation
Installing qmail-toaster-1.03-1.3.5.src.rpm
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.90167
+ umask 022
+ cd /usr/src/redhat/BUILD
+
On 27 Sep 2006, at 10:43, Alan Boyd wrote:
Hi,
I seem to be having a problem running fdr40-install-script.sh,
particularly at the qmail-toaster-1.03-1.3.5.src.rpm part of the
installation
[snip]
From a little googling, it seems to be that this is related to
openssl. I'm running
Hi all,
Could someone please elaborate what the Catchall option does ??
Recently I had changed catchall to deleted. I think from that time, chkuser
was not rejecting mails to non existant users ...
Thanx
Anand
-
So what happens if Catchall is set to bounced...It seems that when it is set
ot bounced, it bounces the mails. But when set to deleted, it seems to be
accepting mails..
The reason why I set it to deleted was that I was getting double bounces to
the postmaster account. I basically want to stop
K Anand wrote:
So what happens if Catchall is set to bounced...It seems that when it is set
ot bounced, it bounces the mails. But when set to deleted, it seems to be
accepting mails..
The reason why I set it to deleted was that I was getting double bounces to
the postmaster account. I basically
OK ..thanx for the confirmation...So how do I stop these double bounces from
filling up the mailbox of postmaster ??
Anand
- Original Message -
From: Jake Vickers [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, September 27, 2006 5:17 PM
Subject: Re:
George Sweetnam wrote:
You might also want to add some additional blacklists from orbs (don't
do
the all-in-one). Some like the dynamic shouldn't be used, but the
exploited
server rbl is very handy. I added 5 or 6 to my servers and it's helped
even more.
The content of my current blacklists
Jdow wrote:
Steve, it might help if you listed which rule sets. There are some
which are obscenely large and others that are obsolete. Maybe we
can prune the list for you a little.
As some have mentioned I may have too many rules. I would like to know
what is a must have and what I should not
Of course if one gets a lot, it could be a problem, one solution I use
is putting this type (once the
domain is confirmed and some whois data as well as who owns he IP
address space) in the badmailfrom
of qmail. Stearns Blacklist (if it wasn't so huge) stops a bunch of
this at connection time.
Quinn Comendant wrote:
Ok, ok...I see where this is going. I can do it on two machines. ;P
yeah, dude, your head will not fit through that hole!
stop it.
-
QmailToaster hosted by: VR Hosted http://www.vr.org
K Anand wrote:
OK ..thanx for the confirmation...So how do I stop these double bounces from
filling up the mailbox of postmaster ??
Anand
Don't bounce catchall email. IOW, set your catchall (postmaster or other)
account to standard routing.
BTW, how did you set your catchall account to
Steve Huff wrote:
On Sep 26, 2006, at 7:27 PM, Quinn Comendant wrote:
I will need to find _some_ solution. What are my options, as painful as
they might be?
so you have the old sendmail solution running on your production
hardware right now? here's my suggestion:
1) build another box
2)
I'm trying to track down a problem with a high volume server and would
appreciate any insights.
To begin with, there was a networking problem which I know nothing about
that apparently started this whole ordeal. The network problem is allegedly
fixed, but the email problem persists.
The
'yum update'
On 9/27/06, Alex [EMAIL PROTECTED] wrote:
Seems like new bug had been discovered in OpenSSL that makes it possible
to exploit some certificates and login as root without a password.
Does anyone know what is the safest way to patch openssl on qmailtoaster
without disrupting other
Here is the advisory
http://www.openssl.org/news/secadv_20060905.txt
-Original Message-
From: Alex [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 27, 2006 10:02 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] OpenSSL Vulerability
Seems like new bug had been
Anyone know (before I hose something) if adding the setgid bit on the
vchkpw group will effect mail
delivery on qmail? The reason, I am pondering the idea of moving
websites to the same directory
as the domains, I want to run httpd as vpopmail.vchkpw so it can access
this via apache.
Has
yum update openssl
I don't see how it would mess anything else up. But then again, i could be
wrong:-)
Seems like new bug had been discovered in OpenSSL that makes it possible
to exploit some certificates and login as root without a password.
Does anyone know what is the safest way to
Just so I understand you, you want to basically put the web sites in
the /home/vpopmail/domains directory?
Erik
On 9/27/06, Mark Samples [EMAIL PROTECTED] wrote:
Anyone know (before I hose something) if adding the setgid bit on the
vchkpw group will effect mail
delivery on qmail? The reason,
Erik Espinoza wrote:
Just so I understand you, you want to basically put the web sites in
the /home/vpopmail/domains directory?
That would be correct, i.e. make a directory in the 'domain.com'
directory called say 'web' and
point the we server to that directory to also serve web sites. The
That's just bad policy. One miscoding in apache, one badly written
cgi, one bug in your config and you're serving mail directories.
It can be done, sure, but I'd recommend against it.
Erik
On 9/27/06, Mark Samples [EMAIL PROTECTED] wrote:
Erik Espinoza wrote:
Just so I understand you, you
On Sep 27, 2006, at 3:26 PM, Erik Espinoza wrote:
That's just bad policy. One miscoding in apache, one badly written
cgi, one bug in your config and you're serving mail directories.
It can be done, sure, but I'd recommend against it.
mark,
are you doing this in an attempt to make mailing
Jimmy Smith wrote:
required_hits 3
report_safe 0
# report_header 1
# use_terse_report 1
# rewrite_subject 0
rewrite_header Subject ***SPAM***
Here, required_hits sets the threshold for what is marked and
considered
spam (score of 3). The report_safe is turned off, leaving the original
message
Eric (Shubes) wrote:
Caution: the contents of /var/qmail/control/blacklists must be on a
single
line (I think - you might be able to escape the newline (CR), but I'm
not
sure w/out testing it).
Eric, can you explain what you are referring to in your Caution
statement above? Do you mean that
Steve Ingraham wrote:
Eric (Shubes) wrote:
Caution: the contents of /var/qmail/control/blacklists must be on a
single
line (I think - you might be able to escape the newline (CR), but I'm
not
sure w/out testing it).
Eric, can you explain what you are referring to in your Caution
statement
Steve Ingraham wrote:
Luck appears to be what I am running out of. These email problems are
eating my lunch! I know everyone out there has been very helpful and I
appreciate the information. However, the suggestions do not seem to be
effective in my getting our email functional again. We
Hola lista , alguien conoce donde descargar themes para squirrelmail gratuitos?o modificar por lo menos la web de inicio?no puedo agrandar el cuadro de ingreso de ususario Gracias
Eric Shubes wrote:
I'm trying to track down a problem with a high volume server and would
appreciate any insights.
To begin with, there was a networking problem which I know nothing
about that apparently started this whole ordeal. The network problem
is allegedly fixed, but the email problem
Does this machine have a caching name server? What do the logs say?
Erik
On 9/27/06, Eric Shubes [EMAIL PROTECTED] wrote:
I'm trying to track down a problem with a high volume server and would
appreciate any insights.
To begin with, there was a networking problem which I know nothing about
Hello,
Attached is a snap shot of what I'm facing
now
Please advice on how to resolve.
Thanks
Gabriel
attachment: error_qmail.JPG
-
QmailToaster hosted by: VR Hosted http://www.vr.org
You have a database called vpopmail as We can see at the screenshot. If You **have never** used qmail + vpopmail You can just drop this database with the command mysqladmin drop vpopmail -p as root (where -p parameter asks for Your root password to access MySQL. After all You can be patiently and
Hi,
I have not set any account as catchall...From the qmailadin, I used the Set
Catchall bounced option. I'm running qmail-toaster-1.03-1.2.10 with
qmailadmin-toaster-1.2.9-1.2.11. Should I mark any account as a catchall
account or by default it is set to some account ?? I just saw that the
Thanks, Craig, SMTP is now working, with your
suggestion, we could solve the problem.
Sivaraman.
--- Craig Smith [EMAIL PROTECTED] wrote:
Hi There,
Check /var/qmail/supervise/smtp/run Part of the
smtp run file is the path
to rblsmtpd which is located in /usr/bin on mine and
I assume by
Craig, thanks again. Is there any compatibility
problem of ucspi-toaster with CentOS 4.3 x86_64
version of gcc? There was some comment on it sometime
back.
Please see the following the Note from
http://www.shupp.org/toaster/#ucspi-tcp
cd /var/src/
tar -xzf tar/ucspi-tcp-0.88.tar.gz
cd
Since it worked when you disabled simscan you should turn it back on again
and manually disable the spam and clam in the control file for it.
spam=no,clam=no
On the line above the default entry (it reads down from the top put a line
specific to your email address). Turn spam off for all
You need the -r which means to use as a rejection list -a is a white list
(don't run through an rbl). I don't have any problems using multiple lines
when entering then in the blacklists file... putting it directly into the
smtp/run file without a \ on the end of the line would be foolish
36 matches
Mail list logo
