[vchkpw] vdominfo issue in 5.3.29

2003-10-21 Thread Trey Nolen
We just upgraded to the new 5.3.29 and are getting a weird issue with the
vdominfo command.
Here is a sample output:
mail:/home/vpopmail/bin# ./vdominfo ntsux.com
domain: ntsux.com
uid:89
gid:89
dir:/home/vpopmail/domains/ntsux.com
users:  2147483646


Notice the users line.  This domain only has about 5 users.  Not all of our
domains have this issue, but the ones that are wrong all give the exact same
large number.  We are using vpasswd files for authentication. Qmailadmin
shows the correct number of users even on the domains with the wrong number
displayed using vdominfo.   This is not a critical bug to us, but I thought
it was interesting.  Any ideas?

Trey Nolen





Re: [vchkpw] vdominfo issue in 5.3.29

2003-10-21 Thread Tom Collins
On Tuesday, October 21, 2003, at 08:06  AM, Trey Nolen wrote:
We just upgraded to the new 5.3.29 and are getting a weird issue with 
the
vdominfo command.
Here is a sample output:
mail:/home/vpopmail/bin# ./vdominfo ntsux.com
domain: ntsux.com
uid:89
gid:89
dir:/home/vpopmail/domains/ntsux.com
users:  2147483646
I suspect that previous versions would give you the same result.

If you're using the cdb backend, vdominfo uses the dircontrol to 
determine the number of users.  Take a look at 
~vpopmail/domains/ntsux.com/.dir-control and you'll find that the first 
line is 2147483646.  Change it to 5, and you'll be all set.

There's a bug somewhere in the vpopmail code that trashes that value.  
I suspect that it rolls backwards from zero to 2,147,483,648 instead of 
-1.  Somehow, it subtracts too often (or doesn't add often enough) when 
adding and deleting users.

--
Tom Collins  -  [EMAIL PROTECTED]
Note: The Tom Logic offices will be closed October 23 to November 18.
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



[vchkpw] adding domains error

2003-10-21 Thread Trey Nolen
After upgrading to 5.3.29, we are getting the following error when trying to
add a domain:
Error: (vadduser) can't read domain limits

We got the same problem wihen trying to add a user to an existing domain. We
fixed it by adding a .qmailadmin-limits file.  But, when adding a new a new
domain, we can't do that because the domain is not there.

I checked through the changelog and noticed that the vget_limits calls were
fixed.  Please break them again. :-)


Trey





Re: [vchkpw] adding domains error

2003-10-21 Thread Tom Collins
On Tuesday, October 21, 2003, at 09:11  AM, Trey Nolen wrote:
After upgrading to 5.3.29, we are getting the following error when 
trying to
add a domain:
Error: (vadduser) can't read domain limits
If you have a ~vpopmail/etc/vlimits.default file, it should work.

I'll look into having the install process create that file if it 
doesn't already exist.

Should we update the code so that it doesn't generate an error if 
neither .qmailadmin-limits or vlimits.default exist?

--
Tom Collins  -  [EMAIL PROTECTED]
Note: The Tom Logic offices will be closed October 23 to November 18.
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



Re: [vchkpw] adding domains error

2003-10-21 Thread X-Istence
Tom Collins wrote:

On Tuesday, October 21, 2003, at 09:11  AM, Trey Nolen wrote:

After upgrading to 5.3.29, we are getting the following error when 
trying to
add a domain:
Error: (vadduser) can't read domain limits


If you have a ~vpopmail/etc/vlimits.default file, it should work.

I'll look into having the install process create that file if it 
doesn't already exist.

Should we update the code so that it doesn't generate an error if 
neither .qmailadmin-limits or vlimits.default exist?

--
Tom Collins  -  [EMAIL PROTECTED]
Note: The Tom Logic offices will be closed October 23 to November 18.
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/
It shouldnt generate an error if either doesnt exist. As it would then 
make the admin freak.

Also in your post about the new release, i suggest you take a look at 
the problems the person had, and see how those happened :)




Re: [vchkpw] adding domains error

2003-10-21 Thread Trey Nolen


 If you have a ~vpopmail/etc/vlimits.default file, it should work.

 I'll look into having the install process create that file if it
 doesn't already exist.

 Should we update the code so that it doesn't generate an error if
 neither .qmailadmin-limits or vlimits.default exist?

That would be good because I'm sure there are a lot of servers like ours out
there that don't have either file in most of their existing domains.

Trey





Re: [vchkpw] adding domains error

2003-10-21 Thread Justin Heesemann
On Tuesday 21 October 2003 18:40, Trey Nolen wrote:
  Should we update the code so that it doesn't generate an error if
  neither .qmailadmin-limits or vlimits.default exist?

 That would be good because I'm sure there are a lot of servers like
 ours out
 there that don't have either file in most of their existing
 domains. 
Oh, and i forgot to mention:
you don't need an .qmailadmin-limits file for every domain, but just the 
vlimits.default file (in ~vpopmail/etc/) to make the error message 
disappear.

a vlimits.default file might look like

maxpopaccounts: -1
maxaliases: -1
maxforwards: -1
maxautoresponders: -1
maxmailinglists: -1
quota: 0
maxmsgcount: 0
default_quota: 0
default_maxmsgcount: 0
perm_account: 0
perm_alias: 0
perm_forward: 0
perm_autoresponder: 0
perm_maillist: 0
perm_quota: 0
perm_defaultquota: 0


(which ofcourse doesn't limit anything at all ;)

a better way would be to have vmoddomlimits create one for one domain of 
yours, and then copy that 
~vpopmail/domains/domain.com//.qmailadmin-limits file to 
~vpopmail/etc/vlimits.default


-- 
Mit internetten Grüßen / Best Regards
---
Justin Heesemannionium Technologies
[EMAIL PROTECTED]www.ionium.org



Re: [vchkpw] adding domains error

2003-10-21 Thread Jochen Schug
X-Istence wrote:

Tom Collins wrote:

On Tuesday, October 21, 2003, at 09:11  AM, Trey Nolen wrote:

After upgrading to 5.3.29, we are getting the following error when 
trying to
add a domain:
Error: (vadduser) can't read domain limits
If you have a ~vpopmail/etc/vlimits.default file, it should work.

Ok, this seems to be a new requirement for 5.3.29 - after creating the 
file with the default values Justin mentioned in another mail, it works 
now for me, too.

I'll look into having the install process create that file if it 
doesn't already exist.

Good idea :)

Should we update the code so that it doesn't generate an error if 
neither .qmailadmin-limits or vlimits.default exist?
It shouldnt generate an error if either doesnt exist. As it would then 
make the admin freak.
I see three possible solutions:
- Creating the missing file with the default values (i.e. no limits) if 
it doesn't exist.
- Don't create the file, but don't complain about it either. Just use 
the default values as with before 5.3.29
- Throw an error message, and point out how to fix it (i.e. provide a 
vlimits.default-example file with the installation)

Also in your post about the new release, i suggest you take a look at 
the problems the person had, and see how those happened :)
That was me ;) As mentioned above, creating the vlimits.default file 
solved the problems for me, too.

Regards
Jochen



Re: [vchkpw] adding domains error

2003-10-21 Thread Tom Collins
On Tuesday, October 21, 2003, at 11:28  AM, Jochen Schug wrote:
Is there a documentation about what these values mean? What's the 
difference between quota, default_quota, perm_quota and 
perm_defaultquota?
Here's the file I built for the distribution which includes some 
details on what everything means.

# Default limits file.  This file is used for domains without a
# .qmailadmin-limits file.
# maximums for each account type, -1 = unlimited
maxpopaccounts  -1
maxforwards -1
maxautoresponders   -1
maxmailinglists -1
# quota for entire domain, in megabytes
# example shows a domain with a 100MB quota and a limit of 10,000 
messages
#quota  100
#maxmsgcount1

# default quota for newly created users (in bytes)
# example shows a user with a 10MB quota and a limit of 1000 messages
#default_quota  10485760
#default_maxmsgcount1000
# uncomment the following lines to disable certain features
#disable_pop
#disable_imap
#disable_dialup
#disable_password_changing
#disable_external_relay
#disable_smtp
#disable_webmail
# Set bitflags on account management for non-postmaster admins.
# To disable certain features, add the following bits:
#   Create = 1, Modify = 2, Delete = 4
# So, to allow modification but not creation or deletion of
# POP/IMAP accounts, set perm_account to 5.
perm_account0
perm_alias  0
perm_forward0
perm_autoresponder  0
perm_maillist   0
perm_quota  0
perm_defaultquota   0
--
Tom Collins  -  [EMAIL PROTECTED]
Note: The Tom Logic offices will be closed October 23 to November 18.
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



Re: [vchkpw] adding domains error

2003-10-21 Thread Jochen Schug
Tom Collins wrote:

On Tuesday, October 21, 2003, at 11:28  AM, Jochen Schug wrote:

Is there a documentation about what these values mean? What's the 
difference between quota, default_quota, perm_quota and 
perm_defaultquota?
Here's the file I built for the distribution which includes some 
details on what everything means.
Thanks, Tom :)  That explains it well.

# Default limits file.  This file is used for domains without a
# .qmailadmin-limits file.
# maximums for each account type, -1 = unlimited
maxpopaccounts  -1
maxforwards -1
maxautoresponders   -1
maxmailinglists -1
# quota for entire domain, in megabytes
# example shows a domain with a 100MB quota and a limit of 10,000 
messages
#quota  100
Unless the behaviour changed, shouldn't this read 104857600 instead of 100?

A general question regarding domain limits: What would be the correct 
behaviour when I add a new domain and have the limits in 
~vpopmail/etc/vlimits.default? Should a .qmaladmin-limits under the new 
domain, with the data from the default file, be created? Or should such 
a domain automatically refer to the data from default file (- when I 
change the defaults, all existing domains with no .qmailadmin-limits are 
affected by the change)?

I noticed that there's no .qmailadmin-limits file created when I add a 
new domain, but when I check the domain limits with vmoddomlimits -S, 
the default values from the time when I added the domain are shown (even 
when I edit the vlimits-default file in the meantime). Where do these 
values come from?

Regards
Jochen



Re: [vchkpw] adding domains error

2003-10-21 Thread Tom Collins
On Tuesday, October 21, 2003, at 12:50  PM, Jochen Schug wrote:
# quota for entire domain, in megabytes
# example shows a domain with a 100MB quota and a limit of 10,000 
messages
#quota  100
Unless the behaviour changed, shouldn't this read 104857600 instead of 
100?
Actually, that's a little inconsistency we have right now.

maildirquota.c multiplies the number by 1024*1024, so it definitely 
considers it MB.

vmoddomlimits writes it out exactly as provided on the command line, 
which probably isn't a good idea now that we allow KB and MB modifiers 
(since if I say -Q 100M, I want 100MB, not 100TB).  The reason it's 
currently parsed, was in response to earlier bug reports that it wasn't 
(and it wasn't because it shouldn't have been).

I've updated vmoddomlimits to indicate that the -Q option is megabytes 
and -q is bytes.  The -S options adds MB after the domain quota and 
bytes after the default user quota when displaying the information.

A general question regarding domain limits: What would be the correct 
behaviour when I add a new domain and have the limits in 
~vpopmail/etc/vlimits.default? Should a .qmaladmin-limits under the 
new domain, with the data from the default file, be created? Or should 
such a domain automatically refer to the data from default file (- 
when I change the defaults, all existing domains with no 
.qmailadmin-limits are affected by the change)?
Current (and I think the expected) behavior is to not create a 
.qmailadmin-limits file.  For sites that don't have domain-specific 
limits, this allows for easy updating of limits.

I noticed that there's no .qmailadmin-limits file created when I add a 
new domain, but when I check the domain limits with vmoddomlimits -S, 
the default values from the time when I added the domain are shown 
(even when I edit the vlimits-default file in the meantime). Where do 
these values come from?
They come from ~vpopmail/etc/vlimits.default (not vlimits-default).  I 
checked on my system, and after modifying vlimits.default, 
vmoddomlimits -S reported the updated values.

--
Tom Collins  -  [EMAIL PROTECTED]
Note: The Tom Logic offices will be closed October 23 to November 18.
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/



Re: [vchkpw] adding domains error

2003-10-21 Thread Jochen Schug
Tom Collins wrote:

On Tuesday, October 21, 2003, at 12:50  PM, Jochen Schug wrote:

# quota for entire domain, in megabytes
# example shows a domain with a 100MB quota and a limit of 10,000 
messages
#quota  100


Unless the behaviour changed, shouldn't this read 104857600 instead 
of 100?
Actually, that's a little inconsistency we have right now.
I checked my existing .qmailadmin-limits file for the values that are 
written by vmoddomlimits, that's where I got the 104857600 from.

maildirquota.c multiplies the number by 1024*1024, so it definitely 
considers it MB.

vmoddomlimits writes it out exactly as provided on the command line, 
which probably isn't a good idea now that we allow KB and MB modifiers 
(since if I say -Q 100M, I want 100MB, not 100TB).  The reason it's 
currently parsed, was in response to earlier bug reports that it 
wasn't (and it wasn't because it shouldn't have been).

I've updated vmoddomlimits to indicate that the -Q option is megabytes 
and -q is bytes.  The -S options adds MB after the domain quota and 
bytes after the default user quota when displaying the information.
Ok, fair enough. But - again just my humble opinion - this introduces 
two different metrics the user/admin has to get right... changing the 
code in maildirquota.c so that it expects a value in bytes instead of 
megabytes, and consitent metrics for vmoddomlimits' -q and -Q options 
(incl. parsing of the latter) would be easier to handle.


A general question regarding domain limits: What would be the correct 
behaviour when I add a new domain and have the limits in 
~vpopmail/etc/vlimits.default? Should a .qmaladmin-limits under the 
new domain, with the data from the default file, be created? Or 
should such a domain automatically refer to the data from default 
file (- when I change the defaults, all existing domains with no 
.qmailadmin-limits are affected by the change)?
Current (and I think the expected) behavior is to not create a 
.qmailadmin-limits file.  For sites that don't have domain-specific 
limits, this allows for easy updating of limits.
Exactly... this can be good or bad, depending on whether or not this is 
desired by the user. I really don't know what's better :) Maybe giving 
the user the choice (by adding another option to vadddomain) to copy or 
symlink the defaults would be a convenient solution.

I noticed that there's no .qmailadmin-limits file created when I add 
a new domain, but when I check the domain limits with vmoddomlimits 
-S, the default values from the time when I added the domain are 
shown (even when I edit the vlimits-default file in the meantime). 
Where do these values come from?
They come from ~vpopmail/etc/vlimits.default (not vlimits-default).  I 
checked on my system, and after modifying vlimits.default, 
vmoddomlimits -S reported the updated values.
You're right - I tried it again, and it works as expected... don't know 
what I did before, I was pretty sure that I saw the behaviour as I 
stated above. Sorry for the false alarm.

Regards
Jochen




[vchkpw] My qmail server can't recieve from hotmail.com.

2003-10-21 Thread Songrit Srilasak



i try send message from hotmail.com 5 message my 
domain can't recieve any message. and when i try to send with mail.com my domain 
can recieve. help me !.


Songrit,



RE: [vchkpw] My qmail server can't recieve from hotmail.com.

2003-10-21 Thread Shane Chrisp
Title: Message



The 
people on this list, like me, are not mind readers. You will need to provide us 
with information
such 
as you run files for your qmail-smtpd, log file exerts and what system your 
running it on.
Any 
other pertanent information will also help. The problem could be qmail/vpopmail 
related or
it 
could even be dns related.

Shane

  
  -Original Message-From: Songrit Srilasak 
  [mailto:[EMAIL PROTECTED] Sent: Thursday, 23 October 2003 
  12:10 AMTo: [EMAIL PROTECTED]Subject: [vchkpw] My qmail 
  server can't recieve from hotmail.com.
  i try send message from hotmail.com 5 message my 
  domain can't recieve any message. and when i try to send with mail.com my 
  domain can recieve. help me !.
  
  
  Songrit,
  


Re: [vchkpw] My qmail server can't recieve from hotmail.com.

2003-10-21 Thread Songrit Srilasak
Title: Message



i use qmail-showctl this appear

qmail home directory: /var/qmail.user-ext 
delimiter: -.paternalism (in decimal): 2.silent concurrency limit: 
120.subdirectory split: 23.user ids: 101, 102, 103, 0, 104, 105, 106, 
107.group ids: 11, 16.

badmailfrom:[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM. ...

and more.
...
[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted 
in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] not 
accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
FROM.[EMAIL PROTECTED] not accepted in 
MAIL FROM.[EMAIL PROTECTED] 
not accepted in MAIL FROM.

bouncefrom: (Default.) Bounce user name is 
MAILER-DAEMON.

bouncehost: (Default.) Bounce host name is 
vmail.eguide.co.th.

concurrencylocal: (Default.) Local concurrency is 
10.

concurrencyremote: Remote concurrency is 
255.

databytes: SMTP DATA limit is 500 
bytes.

defaultdomain: Default domain name is 
vmail.eguide.co.th.

defaulthost: (Default.) Default host name is 
vmail.eguide.co.th.
defaulthost: (Default.) Default host name is 
vmail.eguide.co.th.

doublebouncehost: (Default.) 2B recipient host: 
vmail.eguide.co.th.

doublebounceto: (Default.) 2B recipient user: 
postmaster.

envnoathost: (Default.) Presumed domain name is 
vmail.eguide.co.th.

helohost: (Default.) SMTP client HELO host name is 
vmail.eguide.co.th.

idhost: (Default.) Message-ID host name is 
vmail.eguide.co.th.

localiphost: (Default.) Local IP address becomes 
vmail.eguide.co.th.

locals:Messages for localhost are delivered 
locally.Messages for vmail.eguide.co.th are delivered locally.Messages 
for ns2.eguide.co.th are delivered locally.

me: My name is vmail.eguide.co.th.

percenthack: (Default.) The percent hack is not 
allowed.

plusdomain: Plus domain name is co.th.

qmqpservers: (Default.) No QMQP 
servers.

queuelifetime: (Default.) Message lifetime in the 
queue is 604800 seconds.

rcpthosts:SMTP clients may send messages to 
recipients at localhost.SMTP clients may send messages to recipients at 
vmail.eguide.co.th.SMTP clients may send messages to recipients at 
ns2.eguide.co.th.SMTP clients may send messages to recipients at 
songngam.com.SMTP clients may send messages to recipients at 
prolanguage.co.th.SMTP clients may send messages to recipients at 
lertsiamsteel.com.SMTP clients may send messages to recipients at 
lertsiamsteel.co.th.SMTP clients may send messages to recipients at 

RE: [vchkpw] My qmail server can't recieve from hotmail.com.

2003-10-21 Thread Remo Mattei
Title: Message








What is the error you are getting? Explain
in details if you need help. I do not see anything wrong on these files.



Remo











From: Songrit Srilasak
[mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 22, 2003
10:54 AM
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [vchkpw] My qmail
server can't recieve from hotmail.com.







i use qmail-showctl this appear











qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 101, 102, 103, 0, 104, 105, 106, 107.
group ids: 11, 16.











badmailfrom:
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not
accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not
accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
 ...











and more.





...





[EMAIL PROTECTED] not
accepted in MAIL FROM.
[EMAIL PROTECTED] not
accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED] not
accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED]
not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED] not accepted in
MAIL FROM.
[EMAIL PROTECTED] not accepted in MAIL
FROM.
[EMAIL PROTECTED] not accepted
in MAIL FROM.











bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.











bouncehost: (Default.) Bounce host name is
vmail.eguide.co.th.











concurrencylocal: (Default.) Local concurrency is 10.











concurrencyremote: Remote concurrency is 255.











databytes: SMTP DATA limit is 500 bytes.











defaultdomain: Default domain name is vmail.eguide.co.th.











defaulthost: (Default.) Default host name is vmail.eguide.co.th.





defaulthost: (Default.) Default host name is
vmail.eguide.co.th.











doublebouncehost: (Default.) 2B recipient host:
vmail.eguide.co.th.











doublebounceto: (Default.) 2B recipient user: postmaster.











envnoathost: (Default.) Presumed domain name is
vmail.eguide.co.th.











helohost: (Default.) SMTP client HELO host name is
vmail.eguide.co.th.











idhost: (Default.) Message-ID host name is
vmail.eguide.co.th.











localiphost: (Default.) Local IP address becomes
vmail.eguide.co.th.











locals:
Messages for localhost are delivered locally.
Messages for vmail.eguide.co.th are delivered locally.
Messages for ns2.eguide.co.th are delivered locally.











me: My name is vmail.eguide.co.th.











percenthack: (Default.) The percent hack is not allowed.











plusdomain: Plus domain name is co.th.











qmqpservers: (Default.) No QMQP servers.











queuelifetime: 

RE: [vchkpw] My qmail server can't recieve from hotmail.com.

2003-10-21 Thread Paul Theodoropoulos


At 07:56 PM 10/21/2003, Remo Mattei wrote:
What
is the error you are getting? Explain in details if you need help. I do
not see anything wrong on these files.

Remo

please trim your replies. it's not necessary to forward 42k of previous
message for a one-liner response. thanks.


Paul Theodoropoulos
http://www.anastrophe.com




RE: [vchkpw] My qmail server can't recieve from hotmail.com.

2003-10-21 Thread Shane Chrisp
Title: Message



And 
please dont cc the message to me. I am on the list so i get the message. I dont 
need to get it 2 or 3 times.

Shane

  
  -Original Message-From: Paul 
  Theodoropoulos [mailto:[EMAIL PROTECTED] Sent: Wednesday, 22 
  October 2003 11:08 AMTo: [EMAIL PROTECTED]Subject: RE: 
  [vchkpw] My qmail server can't recieve from 
  hotmail.com.At 07:56 PM 10/21/2003, Remo Mattei 
wrote:
  What is the error you are getting? Explain in details if you need 
help. I do not see anything wrong on these 
files.Remoplease trim your replies. it's not necessary to 
  forward 42k of previous message for a one-liner response. 
  thanks.
  Paul Theodoropouloshttp://www.anastrophe.com


Re: [vchkpw] My qmail server can't recieve from hotmail.com.

2003-10-21 Thread Paul Theodoropoulos
this may or may not be related to your problem, but may i ask why you are 
blocking messages from postmaster and abuse at an assortment of ISPs?

This is a bad idea, but also suggests that if you receive that much mail 
from abuse addresses, perhaps hotmail has blocked your site?

At 09:54 AM 10/22/2003, Songrit Srilasak wrote:
badmailfrom:
mailto:[EMAIL PROTECTED]abusemailto:[EMAIL PROTECTED]@wideopenwest.com 
not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not 
accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in 
MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL 
FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in 
MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL 
FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not 
accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] 
not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.
mailto:[EMAIL PROTECTED][EMAIL PROTECTED] not accepted in MAIL FROM.





Re: [vchkpw] My qmail server can't recieve from hotmail.com.

2003-10-21 Thread Songrit Srilasak
Title: Message



I not appear any message return from hotmail,my 
mail server.
how can i check mail from hotmail is send to my 
server ?
or how to check hotmail known my 
domain?

Songrit,

  - Original Message - 
  From: 
  Remo Mattei 
  To: 'Songrit Srilasak' ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] 
  
  Sent: Wednesday, October 22, 2003 9:56 
  AM
  Subject: RE: [vchkpw] My qmail server 
  can't recieve from hotmail.com.
  
  
  What is the error you 
  are getting? Explain in details if you need help. I do not see anything wrong 
  on these files.
  
  Remo
  
  
  
  
  
  From: Songrit 
  Srilasak [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 
  10:54 AMTo: [EMAIL PROTECTED]; [EMAIL PROTECTED]Subject: Re: [vchkpw] My qmail server 
  can't recieve from hotmail.com.
  
  
  i use qmail-showctl this 
  appear
  
  
  
  qmail home directory: 
  /var/qmail.user-ext delimiter: -.paternalism (in decimal): 
  2.silent concurrency limit: 120.subdirectory split: 23.user ids: 
  101, 102, 103, 0, 104, 105, 106, 107.group ids: 11, 
  16.
  
  
  
  badmailfrom:[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not accepted 
  in MAIL FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not accepted in 
  MAIL FROM.[EMAIL PROTECTED] not accepted 
  in MAIL FROM.[EMAIL PROTECTED] not accepted in 
  MAIL FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
  MAIL FROM.[EMAIL PROTECTED] not accepted 
  in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
  MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM. ...
  
  
  
  and 
  more.
  
  ...
  
  [EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted 
  in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
  MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not 
  accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in 
  MAIL FROM.[EMAIL PROTECTED] not accepted 
  in MAIL FROM.[EMAIL PROTECTED] not accepted 
  in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not accepted 
  in MAIL FROM.[EMAIL PROTECTED] 
  not accepted in MAIL FROM.[EMAIL PROTECTED] not accepted in MAIL 
  FROM.[EMAIL PROTECTED] not accepted 
  in MAIL FROM.[EMAIL PROTECTED] not accepted in 
  MAIL FROM.
  
  
  
  bouncefrom: (Default.) Bounce user 
  name is MAILER-DAEMON.
  
  
  
  bouncehost: (Default.) Bounce host 
  name is vmail.eguide.co.th.
  
  
  
  concurrencylocal: (Default.) Local 
  concurrency is 10.
  
  
  
  concurrencyremote: Remote 
  concurrency is 255.
  
  
  
  databytes: SMTP DATA limit is 
  500 bytes.
  
  
  
  defaultdomain: Default domain name 
  is vmail.eguide.co.th.
  
  
  
  defaulthost: (Default.) Default 
  host name is vmail.eguide.co.th.
  
  defaulthost: (Default.) Default 
  host name is vmail.eguide.co.th.
  
  
  
  doublebouncehost: (Default.) 2B 
  recipient host: vmail.eguide.co.th.
  
  
  
  doublebounceto: (Default.) 2B 
  recipient user: postmaster.
  
  
  
  envnoathost: (Default.) Presumed 
  domain name is vmail.eguide.co.th.
  
  
  
  helohost: (Default.) SMTP