Hi all,
I'd like to install qmailtoaster plus; done that a few times before, but...
The site is down? I get a server 500 error:
The server encountered an internal error or misconfiguration and was
unable to complete your request.
Please contact the server administrator, [no address given]
Very good. I saw the two posts this morning - it just looked so weird
to see total silence on the list. I'll look forward to the thread you
mention and will join the discussion then.
Thanks,
Martin
Von meinem iPhone gesendet
Am 03.06.2010 um 17:55 schrieb Eric Shubert e...@shubes.net:
Atul Paralikar wrote:
Even after applying all the recommendations for the problem addressing
2010 date. Mails are still marked as SPAM. Below is the part of the
header of a genuine email from a genuine user.
Have I missed anything? How to I check if the setting I applied are
indeed
My http.conf
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See URL:http://httpd.apache.org/docs/2.2/ for detailed information.
# In particular, see
#
I would like to setup Qmail Toaster to be a smart host for a clients domain.
Can anyone point me in the right direction to get Qmail Toaster configured to
forward our incoming email to a server behind the fire wall?
James
Hi,
Please check /var/qmail/control/smtprouts.
http://wiki.qmailtoaster.com/index.php/Smtproutes
-S.Senthilvel.
On Thu, Jun 3, 2010 at 10:02 PM, James Ecker jgeprogram...@hotmail.comwrote:
I would like to setup Qmail Toaster to be a smart host for a clients
domain. Can anyone point me in
I obviously replied to the wrong mail...
Sorry.
Von meinem iPhone gesendet
Am 03.06.2010 um 18:02 schrieb Martin Waschbuesch
mar...@waschbuesch.de:
Very good. I saw the two posts this morning - it just looked so
weird to see total silence on the list. I'll look forward to the
thread you
What is exactly what I am looking for, thank you. How long will it sit in the
queue if the receiving server is down and how often will it attempt to deliver
the queued email?
Date: Thu, 3 Jun 2010 22:07:56 +0530
From: senthilv...@gmail.com
To: qmailtoaster-list@qmailtoaster.com
Subject: Re:
It will keep mails in queue, until the queue life time expires. The file is
/var/qmail/control/queuelifetime.
http://wiki.qmailtoaster.com/index.php/Queuelifetime
-S.Senthilvel
On Thu, Jun 3, 2010 at 10:28 PM, James Ecker jgeprogram...@hotmail.comwrote:
What is exactly what I am looking
how often will it attempt to deliver the queued email?
does any one help us regarding this? can we change this interval? if so
where?
Thanks in advance...
On Thu, Jun 3, 2010 at 10:52 PM, senthil vel senthilv...@gmail.com wrote:
It will keep mails in queue, until the queue life time expires.
It appears as though you have a default configuration. Replace this
in your squirrelmail.conf file.
Directory /usr/share/squirrelmail
Options None
Order allow,deny
allow from all
/Directory
with this
Directory /usr/share/squirrelmail
RewriteEngine on
RewriteCond %{SERVER_PORT}
I found this using google:
http://www.lifewithqmail.org/lwq.html#retry-schedule
Would someone care to add it to the wiki?
Senthil, if you need to modify the schedule, it looks as though you'd
need to modify the qmail-send source code.
--
-Eric 'shubes'
senthil vel wrote:
how often will it
Maxwell Smart wrote:
It appears as though you have a default configuration. Replace this in
your squirrelmail.conf file.
Directory /usr/share/squirrelmail
Options None
Order allow,deny
allow from all
/Directory
with this
Directory /usr/share/squirrelmail
RewriteEngine on
That's exactly where I am having problems and that's the only way I
can get it to work. If I have the welcome.conf enabled it goes to the
apache welcome page instead of redirecting and the log file says
failed, reason: SSL connection required. If I disable the
welcome.conf and include
I'm not saying that ErrorDocument won't work, just that it's a bit of a
hack.
The conventional way (and 'better' for a number of reasons) is to use
the RewriteEngine. I seem to recall that there's a way to turn on
logging for the rewrite engine if you're having a problem with it.
Here's the
It doesn't work with the variable either. Quoting Maxwell Smart
c...@yother.com:
That's exactly where I am having problems and that's the only way I
can get it to work. If I have the welcome.conf enabled it goes to
the apache welcome page instead of redirecting and the log file says
Just a head's up... I just tried to do an update through qtp-menu (running
latest qtp) and it said no new packages available when running the up2date
script and Newer clamav-toaster-0.96.0-1.3.35 is already installed,
clamav-toaster-0.96.1-1.3.35 bypassed when trying through the newmodel
script.
Thomas M. Jaeger wrote:
Just a head’s up... I just tried to do an update through qtp-menu
(running latest qtp) and it said no new packages available when running
the up2date script and “Newer clamav-toaster-0.96.0-1.3.35 is already
installed, clamav-toaster-0.96.1-1.3.35 bypassed” when trying
I realize that it's a bit of a hack and I don't like it, but I cannot
get it to work correctly otherwise. I just tried your config and it
didn't work either.
You are using the webmail suffix where I am not. I am trying to get
mail.myserver.com to work using SNI. I should be able to have
Hi Maxwell and Eric,
Thanks for all the suggestions, I did try both your methods but only One
would work.
Maxwells :
I changed my squirrelmail.conf as you suggested after backing up original
Directory /usr/share/squirrelmail
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule
Nothing much out of the ordinary. I have a few hosts that rewrite is
working on.
For some reason the rewrite isn't working for you.
I think you're missing a '.' after 'webmail', as in:
RewriteRule ^(.*/webmail.*)$ https://%{SERVER_NAME}$1 [L,R]
--
-Eric 'shubes'
sysadmin wrote:
Hi Maxwell
One of the utilities that the QMT Admin has is a 'Send Email to Users
(Email Users-0.5)' button.
Does this email ALL users on ALL domains?
Thanks,
Scott
Yes, I am using Virtual hosts. I'll need to play with it more and
I'll report back.
My re direct issue is actually caused by the certificate it expects to
see at http://mail.myserver.com re directing to
https://mail.myserver.com If I go to http://mail.myserver.com/webmail
it works
Scott Hughes wrote:
I'm using the SSLRequireSSL / ErrorDocument 406 setup on my system for
my regular webmail and the new horde install I have and both are working
great.
Scott
That's nice to know, Scott.
I just want to be sure that people realize that the ErrorDocument
technique is a
24 matches
Mail list logo
