Hi there,
Yes I am creating a .qmail for every real user, if I don't then mail doesn't
route to them. As I said this in itself
isn't a huge problem, but the name.surname was. I'm not entirely sure why I
need the .qmail for each user, but for some
reason I do.
I renamed the files to
Aside from a bad install or a major misconfiguration, no idea.
Just as a guess though, make sure /var/qmail/control/locals doesn't
have anything that's in /var/qmail/control/virtualdomains
On 7/28/06, Craig Smith [EMAIL PROTECTED] wrote:
Hi there,
Yes I am creating a .qmail for every real
Well, the install was done with the qmailtoaster script files for fc5.
Configuration appears to be the same as
our other servers. the locals file only has localhost and the actual
hostname in it. For the life of me I couldn't
find any reason for the need for .qmail for each user. The
Our Domain name is host by other supplier and they host our website.
They point the mx record to our mail server with fix ip.
We only need to use their DNS by only fill in our mail server.
Should I need to setup a DNS server and domainkey by following the
instruction of Qmailtoaster?
Una consulta massupongamo que el archivo tiene estas lineasusuario contraseña nombre_real(pepe) 1234 Ariel fernandezque lineas agrego al script para que me pase lo nombres reales tambien ??
Gracias2006/7/27, Ariel [EMAIL PROTECTED]:
Muchisimas gracias.. lo voy a probar y te avisoSaludosEl día
Please fix the date on your server/PC
first. You're way ahead of us ...
;-)
Manny wrote:
Is there a way I can exlude certain ip blocks(RELAYCLIENT)
defined in my =
tcp.smtp from being blocked based n the settings of my =
/var/qmail/simcontrol/blacklist
Regards,
Manny
El parámetro necesario del vadduser, no lo sé ahora, pero tendrás que
añadirle un parámetro para indicar el nombre real.
Ahora bien, para pillar el tercer campo y meterlo en nombre te tiene que
quedar algo como:
usuario=`echo ${linea} | cut -d , -f 1`;
clave=`echo ${linea} | cut -d , -f
Ho wrote:
Our Domain name is host by other supplier and they host our website.
They point the mx record to our mail server with fix ip.
We only need to use their DNS by only fill in our mail server.
Should I need to setup a DNS server and domainkey by following the
instruction of
Jake Vickers wrote:
You have to set up at least a caching name server on your mail server to
run the new version.
Why? This is important to me because I use toaster on machines that run
mydns, which only serves as a primary source nameserver and does not
return records for other domains. Is
Warren (mailing lists) wrote:
Jake Vickers wrote:
You have to set up at least a caching name server on your mail server to
run the new version.
Why? This is important to me because I use toaster on machines that run
mydns, which only serves as a primary source
Jake Vickers wrote:
The domainkeys function requires at least a caching DNS server on the
mail server itself to help speed up the requests. I believe (someone
correct me if I'm wrong) this is for answering requests by other
machines, not for local requests.
So then any requests made of this
Jake Vickers wrote:
Warren (mailing lists) wrote:
Jake Vickers wrote:
You have to set up at least a caching name server on your mail server to
run the new version.
Why? This is important to me because I use toaster on machines that run
mydns, which only serves as a primary source
Eric Shubes wrote:
I think we need Nick to chime in here with the definitive answer.
That being said, here's my (mis?)understanding.
Yes, you need a *caching* nameserver with the new version that supports
domain keys. This is so that the mail server isn't querying the
nameserver(s)
Hey Jake,
I have a script I run nightly which removes mail in the spam folders older
than 10 days. It gives users a chance to review or move to their ham folder
if needed. I've added this script to run from cron and every night it
executes and sends me an email of what was removed (cron
George wrote:
Hey Jake,
I have a script I run nightly which removes mail in the spam folders older
than 10 days. It gives users a chance to review or move to their ham folder
if needed. I've added this script to run from cron and every night it
executes and sends me an email of what was
Was doing
some expirements with the mailing list so I can learn how to teach our email
clients how to use it, and I went to delete one of my test email mailing lists,
and it bugged out and deleted the entire folder structure for our domain (the
domain housing the list, didn't touch the
Warren (mailing lists) wrote:
Eric Shubes wrote:
I think we need Nick to chime in here with the definitive answer.
That being said, here's my (mis?)understanding.
Yes, you need a *caching* nameserver with the new version that supports
domain keys. This is so that the mail server isn't
I'm not Nick, but I'll chime in. You are correct.
On 7/28/06, Eric Shubes [EMAIL PROTECTED] wrote:
Jake Vickers wrote:
Warren (mailing lists) wrote:
Jake Vickers wrote:
You have to set up at least a caching name server on your mail server to
run the new version.
Why? This is important
But then if what you are saying is true, then a caching name server is
not *needed* but is a good thing to have to stop inefficiencies. Again,
I say this because I have setups that only have an authoritative name
server on them and the caching name server is the machine immediately
below it in
Erik Espinoza wrote:
Aside from a bad install or a major misconfiguration, no idea.
Just as a guess though, make sure /var/qmail/control/locals doesn't
have anything that's in /var/qmail/control/virtualdomains
I've been trying to fix an apparent domain name issue, and (foolishly)
modified
I finally was able to transfer my domain, so now my qmail-toaster is
handling email directly from everywhere, instead of forwarded emails
from my old (hosted) server.
On the old server, as with the toaster, I have an account designated as
the catch-all for names that aren't defined, as I like
21 matches
Mail list logo
