[qmailadmin] [SPAM] important message

[Mail Daemon]

Hello!

 

New message, please read 

 

Mail Daemon



---
El software de antivirus Avast ha analizado este correo electrónico en busca de 
virus.
http://www.avast.com


!DSPAM:5628553041554230013988!

[qmailadmin] important message

[Gilchrist Roldan]

Hello!

 

New message, please read 

 

Gilchrist Roldan



---
Este mensaje no contiene virus ni malware porque la protección de avast! 
Antivirus está activa.
https://www.avast.com/antivirus


!DSPAM:5628557241558349517510!

[qmailadmin] Qmailadmin: check if password is strong enough

[Nikolay Mitev]

Hi Team,

I need a little help on the restriction on the implementation and change
password qmailadmin-1.2.16-0.el6.x86_64. I tried this patch (
http://mugurel.sumanariu.ro/qmail/qmailadmin-check-if-password-is-strong-enough/)
no problems during the build and installation but then does not work for
password protection, I can change the password by typing only two
characters.

Best regards,
Nikolay


!DSPAM:545509eb26512745791880!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:545509fd26512109417208!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:54550a2326511191144102!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:54550a1526515817892821!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:54550a0b26511933518104!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:54550a2f26511741619920!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:54550a3c26512003475680!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:54550a4926516704816328!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:54550a6326511001276033!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:54550a7126518209919201!

[qmailadmin] unable to login

[francis drake]

Hi all,

After more than 10 years my qmail, vpopmail, and qmailadmin setup died 
catastrophicly.  qmailadmin was the core part of administering everything.

I now have a new install of that setup. Mail delivery works and I can retrieve 
email from the postmaster and user accounts.

However, loggin into qmailadmin's postmaster account using
   postmaster
   my.domain
   password
results in Invalid Login. I also tried postmaster@my.domain but that 
doesn't work either.

I reinstalled both vpopmail and qmailadmin but that didn't fix the problem.  
Also tried both 1.2.15 and 1.2.16.

I checked the mail archives and even poked around in qmailadmin.c but am pretty 
lost when it comes to c programming.

The o/s is fedora 20.

Any help with this will be greatly appreciated, especially tips on how to debug 
this situation (didn't have much luck trying various printf instructions in the 
source).

Looking forward to hearing from you,
Mike Wright

!DSPAM:544402c726511227814814!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:544402fb26512074196910!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444031426511732612370!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444032126516503210799!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444030626511555187320!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444036126517155543457!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444032d26517112610752!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444033a26514078573801!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444034726511404216977!

Re: [qmailadmin] unable to login

[Bob Miller]

Hi,

 I now have a new install of that setup. Mail delivery works and I can 
 retrieve email from the postmaster and user accounts.
 
 However, loggin into qmailadmin's postmaster account using
postmaster
my.domain
password
 results in Invalid Login. I also tried postmaster@my.domain but that 
 doesn't work either.

Based on the info given my best guess would be that you do not have
permissions set correctly on the qmailadmin executable.  I use mpm-itk
so I can configure apache to run the virtual host as vpopmail:vchkpw,
maybe that helps...

 Any help with this will be greatly appreciated, especially tips on how to 
 debug this situation (didn't have much luck trying various printf 
 instructions in the source).
 
 Looking forward to hearing from you,
 Mike Wright
 
 
 


!DSPAM:54440d0026517105823324!

Re: [qmailadmin] unable to login

[francis drake]

Thanks for getting back to me, Derek.

It's a .gz install.  I'm using daemontools and checked all the qmail logs.  I'm 
not getting any logs from pop3d.  I'll have to look into that.




On Sunday, October 19, 2014 12:09 PM, da...@nyi.net da...@nyi.net wrote:
How did you install, from source or RPMs?  IIRC when I last dealt with 
qmailadmin/vpopmail, qmailadmin had to be told about vpopmail with a 
flag.  As for logging in, you should be able to log in as any user that 
vpopmail is aware of.

Also, check your logs.  Location depends on how you're running qmail 
(daemontools, etc).





On 19.10.2014 14:28, francis drake wrote:
 Hi all,

 After more than 10 years my qmail, vpopmail, and qmailadmin setup
 died catastrophicly.  qmailadmin was the core part of administering
 everything.

 I now have a new install of that setup. Mail delivery works and I can
 retrieve email from the postmaster and user accounts.

 However, loggin into qmailadmin's postmaster account using
postmaster
my.domain
password
 results in Invalid Login. I also tried postmaster@my.domain but
 that doesn't work either.

 I reinstalled both vpopmail and qmailadmin but that didn't fix the
 problem.  Also tried both 1.2.15 and 1.2.16.

 I checked the mail archives and even poked around in qmailadmin.c but
 am pretty lost when it comes to c programming.

 The o/s is fedora 20.

 Any help with this will be greatly appreciated, especially tips on
 how to debug this situation (didn't have much luck trying various
 printf instructions in the source).

 Looking forward to hearing from you,
 Mike Wright

 




!DSPAM:5444121426519460012690!

Re: [qmailadmin] unable to login

[Darek M.]

If you have the compile directory from the old setup, I would look at 
'config.log' for the configure script arguments.


Maybe you can post your configure command for the current qmailadmin 
install.  Vpopmail should also have its own logfile.  It's usually very 
informative.  Anything in /var/log/maillog ?



On 10/19/2014 3:31 PM, francis drake wrote:

Thanks for getting back to me, Derek.

It's a .gz install.  I'm using daemontools and checked all the qmail logs.  I'm 
not getting any logs from pop3d.  I'll have to look into that.




On Sunday, October 19, 2014 12:09 PM, da...@nyi.net da...@nyi.net wrote:
How did you install, from source or RPMs?  IIRC when I last dealt with
qmailadmin/vpopmail, qmailadmin had to be told about vpopmail with a
flag.  As for logging in, you should be able to log in as any user that
vpopmail is aware of.

Also, check your logs.  Location depends on how you're running qmail
(daemontools, etc).





On 19.10.2014 14:28, francis drake wrote:

Hi all,

After more than 10 years my qmail, vpopmail, and qmailadmin setup
died catastrophicly.  qmailadmin was the core part of administering
everything.

I now have a new install of that setup. Mail delivery works and I can
retrieve email from the postmaster and user accounts.

However, loggin into qmailadmin's postmaster account using
postmaster
my.domain
password
results in Invalid Login. I also tried postmaster@my.domain but
that doesn't work either.

I reinstalled both vpopmail and qmailadmin but that didn't fix the
problem.  Also tried both 1.2.15 and 1.2.16.

I checked the mail archives and even poked around in qmailadmin.c but
am pretty lost when it comes to c programming.

The o/s is fedora 20.

Any help with this will be greatly appreciated, especially tips on
how to debug this situation (didn't have much luck trying various
printf instructions in the source).

Looking forward to hearing from you,
Mike Wright











!DSPAM:544412b326512822510196!

Re: [qmailadmin] unable to login

[francis drake]

On Sunday, October 19, 2014 12:12 PM, Bob Miller b...@computerisms.ca wrote:
Hi,

 I now have a new install of that setup. Mail delivery works and I can 
 retrieve email from the postmaster and user accounts.
 
 However, loggin into qmailadmin's postmaster account using
postmaster
my.domain
password
 results in Invalid Login. I also tried postmaster@my.domain but that 
 doesn't work either.

Based on the info given my best guess would be that you do not have
permissions set correctly on the qmailadmin executable.  I use mpm-itk
so I can configure apache to run the virtual host as vpopmail:vchkpw,
maybe that helps...


Hi Bob,

qmailadmin's cgi perms are 89:89.  Your idea that apache is not using the right 
perms sounds like the right direction.  I don't remember having to setup suid 
stuff in apache before but that was a long time ago.  I'll get into the apache 
manual.


Checking the apache logs does show an error whenever I try logging in but the 
error seems screwy: Domain theorb.net was not found in the assign file

!DSPAM:544412e926511777515667!

Re: [qmailadmin] unable to login

[francis drake]

OK.  Never thought to look in log/maillog.  It's informative here: vpopmail 
user not found ...

Bob suggested a permission problem with apache.  I'll try setting up suid and 
getting back.

I think we're on the right track.




On Sunday, October 19, 2014 12:36 PM, Darek M. da...@nyi.net wrote:
If you have the compile directory from the old setup, I would look at 
'config.log' for the configure script arguments.

Maybe you can post your configure command for the current qmailadmin 
install.  Vpopmail should also have its own logfile.  It's usually very 
informative.  Anything in /var/log/maillog ?





On 10/19/2014 3:31 PM, francis drake wrote:
 Thanks for getting back to me, Derek.

 It's a .gz install.  I'm using daemontools and checked all the qmail logs.  
 I'm not getting any logs from pop3d.  I'll have to look into that.




 On Sunday, October 19, 2014 12:09 PM, da...@nyi.net da...@nyi.net wrote:
 How did you install, from source or RPMs?  IIRC when I last dealt with
 qmailadmin/vpopmail, qmailadmin had to be told about vpopmail with a
 flag.  As for logging in, you should be able to log in as any user that
 vpopmail is aware of.

 Also, check your logs.  Location depends on how you're running qmail
 (daemontools, etc).





 On 19.10.2014 14:28, francis drake wrote:
 Hi all,

 After more than 10 years my qmail, vpopmail, and qmailadmin setup
 died catastrophicly.  qmailadmin was the core part of administering
 everything.

 I now have a new install of that setup. Mail delivery works and I can
 retrieve email from the postmaster and user accounts.

 However, loggin into qmailadmin's postmaster account using
 postmaster
 my.domain
 password
 results in Invalid Login. I also tried postmaster@my.domain but
 that doesn't work either.

 I reinstalled both vpopmail and qmailadmin but that didn't fix the
 problem.  Also tried both 1.2.15 and 1.2.16.

 I checked the mail archives and even poked around in qmailadmin.c but
 am pretty lost when it comes to c programming.

 The o/s is fedora 20.

 Any help with this will be greatly appreciated, especially tips on
 how to debug this situation (didn't have much luck trying various
 printf instructions in the source).

 Looking forward to hearing from you,
 Mike Wright





 





!DSPAM:544413ef26512142328780!

Re: [qmailadmin] unable to login

[Darek M.]

You should always copy and paste the exact data.

vpopmail user not found is different than vpopmail: user not found

It would speed up getting a meaningful/helpful reply if you provided 
relevant (and accurate) info, like snippets from logs, your 'configure' 
arguments, etc.


On 10/19/2014 3:41 PM, francis drake wrote:

OK.  Never thought to look in log/maillog.  It's informative here: vpopmail 
user not found ...

Bob suggested a permission problem with apache.  I'll try setting up suid and 
getting back.

I think we're on the right track.




On Sunday, October 19, 2014 12:36 PM, Darek M. da...@nyi.net wrote:
If you have the compile directory from the old setup, I would look at
'config.log' for the configure script arguments.

Maybe you can post your configure command for the current qmailadmin
install.  Vpopmail should also have its own logfile.  It's usually very
informative.  Anything in /var/log/maillog ?





On 10/19/2014 3:31 PM, francis drake wrote:

Thanks for getting back to me, Derek.

It's a .gz install.  I'm using daemontools and checked all the qmail logs.  I'm 
not getting any logs from pop3d.  I'll have to look into that.




On Sunday, October 19, 2014 12:09 PM, da...@nyi.net da...@nyi.net wrote:
How did you install, from source or RPMs?  IIRC when I last dealt with
qmailadmin/vpopmail, qmailadmin had to be told about vpopmail with a
flag.  As for logging in, you should be able to log in as any user that
vpopmail is aware of.

Also, check your logs.  Location depends on how you're running qmail
(daemontools, etc).





On 19.10.2014 14:28, francis drake wrote:

Hi all,

After more than 10 years my qmail, vpopmail, and qmailadmin setup
died catastrophicly.  qmailadmin was the core part of administering
everything.

I now have a new install of that setup. Mail delivery works and I can
retrieve email from the postmaster and user accounts.

However, loggin into qmailadmin's postmaster account using
 postmaster
 my.domain
 password
results in Invalid Login. I also tried postmaster@my.domain but
that doesn't work either.

I reinstalled both vpopmail and qmailadmin but that didn't fix the
problem.  Also tried both 1.2.15 and 1.2.16.

I checked the mail archives and even poked around in qmailadmin.c but
am pretty lost when it comes to c programming.

The o/s is fedora 20.

Any help with this will be greatly appreciated, especially tips on
how to debug this situation (didn't have much luck trying various
printf instructions in the source).

Looking forward to hearing from you,
Mike Wright
















!DSPAM:544417bb26514350843407!

Re: [qmailadmin] unable to login

[francis drake]

Thanks for your help Bob.  Messing with suexec made things much worse.  A break 
from the desk and breakfast at 2 this afternoon cleared my head a bit.

Turned out to be an selinux restriction.

I forgot to ask Derek this.  Do you know just what I need to do to get this to 
fly with selinux set in enforcing mode?


!DSPAM:54442adb26511498718639!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:544456fb26511511913959!

Re: [qmailadmin] unable to login

[Darek M.]

I usually just set it to 'permissive'.  I imagine you'll have to be 
making adjustments and allowing things as you discover more and more 
things not working.



On 10/19/2014 5:19 PM, francis drake wrote:


Thanks for your help Bob.  Messing with suexec made things much worse.  A break 
from the desk and breakfast at 2 this afternoon cleared my head a bit.

Turned out to be an selinux restriction.

I forgot to ask Derek this.  Do you know just what I need to do to get this to 
fly with selinux set in enforcing mode?







!DSPAM:544456dd26511922410443!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:544456ed26519266811703!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444570626511891679854!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444571f26511136330469!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444571326511409586260!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444573926511790617535!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444572c26511564715522!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444574626519948211551!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444575126513598210540!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:5444575f26511689651378!

[qmailadmin] Qmail install guide for Debian 7.6 Wheezy

[Thibault Richard]

Hello,

FYI, I’ve recently updated my Qmail install guide for Debian Wheezy.

The guide is available on http://qmailrocks.thibs.com/

Feel free to test and comment it

Best Regards

Thibault

!DSPAM:53e7a68b81087502117647!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:53e7a6ad81081703845105!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:53e7a6bb81081844613337!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:53e7a6d481085282217774!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:53e7a6c781088773942290!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:53e7a6e081081662117367!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:53e7a6ed81081137018214!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:53e7a6fb81081791012093!

[qmailadmin] offices closed / kantoren gesloten

[support]

Dear,

We have well received your email.
Our offices are open every workingday between 09.00 and 18.00. At that time a 
ticket will be created or your reply to an existing ticket will be added.

your dommel.com support department

-

Geachte,

We hebben uw email goed ontvangen.
Onze kantoren zijn elke werkdag geopend tussen 09.00 en 18.00 uur. Op dat 
moment zal er een ticket worden opgemaakt voor uw vraag of zal uw update op een 
bestaand ticket worden toegevoegd.

uw dommel.com support afdeling



!DSPAM:53e7a71481087610784892!

[qmailadmin] [SPAM] autoresponder don't replaces header

[Daniel Hauck]

Hey there,

I got a mailserver running with qmail 1.06 and vpopmail 5.4.33.

For administration we use qmailadmin 1.2.1 with autorespond 2.0.2

Now we got the problem if I configure an autoresponder with qmailadmin, 
there's one line too much.

So the header isn't overwritten and the header part is in the message like:

From: f...@bar.tld
Subject: Something 

Message ... ... .. 

I can't figure out, where the newline is coming from, I read the c source, 
but I'm not able to find it.

Thanks in advance!

Best regards, Daniel


!DSPAM:534f95c134261437428759!

[qmailadmin] [SPAM] Send Vacation Auto-Response

[Allan Dukat]

Hi list

My users have discovered a problem when setting a Send Vacation Auto- 
Response in lang da the mail seems to miss a charset header.


With the result that mail client do not properly display the special danish  
letters.


How do I configure autorespond to use the right charset?

I use vpopmail-5.4.33, autorespond-2.0.4 and qmailadmin-1.2.16.

Thanks in advance.

Best regards,
Allan Dukat

!DSPAM:52e29a0634269240316538!

[qmailadmin] [SPAM] qmailadmin and maillist editing not working

[Mesut GULNAZ]

i installed a fresh install on my server
which is centos 6 x64.

other package's versions are like that.

vpopmail-5.4.33
ezmlm-idx-7.1.1
qmailadmin-1.2.16

all is fine but.
when i try to edit a maillist config like:

- remote management
- subscription methods
- message archiving
etc...

and then click on save then i am back to main maillist screen.
when i check the settings, i see that nothing has been changed.

what can i do to solve this?

thanks...


!DSPAM:52964c1d34262313391301!

Re: [qmailadmin] [SPAM] qmailadmin and maillist editing not working

[Johannes Weberhofer]

A while ago I have prpeared a patch which you can find in 
https://build.opensuse.org/package/show/home:weberho:qmailtoaster/qmailadmin . 
I think I have also uploaded the patch to the sourceforge repository, but there 
is no further development.

Best regards,
Johannes

Am 27.11.13 20:46, schrieb Mesut GULNAZ:

i installed a fresh install on my server
which is centos 6 x64.

other package's versions are like that.

vpopmail-5.4.33
ezmlm-idx-7.1.1
qmailadmin-1.2.16

all is fine but.
when i try to edit a maillist config like:

- remote management
- subscription methods
- message archiving
etc...

and then click on save then i am back to main maillist screen.
when i check the settings, i see that nothing has been changed.

what can i do to solve this?

thanks...



--
Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna

!DSPAM:52967bf334261895514238!

Re: [qmailadmin] [SPAM] qmailadmin 1.2.16 questions

[Tom Collins]

You might need to recompile vpopmail and install that without the install-strip 
option, since qmailadmin statically links libvpopmail (IIRC).

-Tom


On May 21, 2013, at 9:11 AM, Eric Shubert wrote:
 I agree that the error is probably somewhere else.
 You might try the vpopmail list. I believe there are a few folks there who 
 have successfully built on debian. I wouldn't expect there to be much 
 difference on Ubuntu, but who knows.
 Good luck!


!DSPAM:519ecb0134131985948399!

[qmailadmin] Re: [SPAM] qmailadmin 1.2.16 questions

[Allan Dukat]

Eric Shubert writes: 


On 05/17/2013 05:12 AM, Allan Dukat wrote:



OK, then I have a problem with qmailadmin-1.2.16, configured like this:
./configure \
  --enable-vpopmaildir=/home/vpopmail \
  --enable-htmldir=/usr/local/apache2/htdocs \
  --enable-cgibindir=/usr/local/apache2/cgi-bin \
  --enable-imageurl=/images/qmailadmin \
  --enable-imagedir=/usr/local/apache2/htdocs/images/qmailadmin \
  --enable-qmaildir=/var/qmail \
  --enable-ezmlmdir=/usr/local/bin/ezmlm \
  --enable-cgipath=/cgi-bin/qmailadmin \
  --enable-autoresponder-path=/usr/local/bin \
  --enable-vpopuser=vpopmail \
  --enable-vpopgroup=vchkpw \
  --disable-ezmlm-mysql \
  --enable-modify-quota \
  --enable-help
When adding the fist Forward I got an empty page as answer, an this in
Apache errorlog:
*** glibc detected *** /usr/local/apache2/cgi-bin/qmailadmin: double
free or corruption (top): 0x01f326e0 ***



The Forward is added an I can add and list Forwards from now on, when
the last Forward is deleted the error is repeated with the same
addresses as far I can see.
I Use Ubuntu 12.04.2 LTS, x86_64, fully patched.
And openssl-1.0.1e, netqmail-1.06, chkuser-2.0.9-release.patch,
qmail-authentication-081, ucspi-tcp-0.88, daemontools-0.76, pcre-8.32,
maildrop-2.6.0, vpopmail-5.4.33, ezmlm-idx-7.1.1, dovecot-2.2.1, 
apr-1.4.6,

apr-util-1.5.2, httpd-2.4.4, courier-authlib-0.65.0, sqwebmail-5.6.1,
autorespond-2.0.4, qmailadmin-1.2.16, qmailadmin-help-1.0.8 and
vqadmin-2.3.7 all configure-make-install.
Spam Filter is elsewhere.
I hope that anybody out there can figure out what I did wrong.



Best regards,
Allan Dukat


I misspoke. There was one problem, a bug I fixed and reported on the 
vpopmail list about 3 months ago. Here's a snip:

q
I've had a look at the code, and found that the config.h file, which 
defines CATCHALL_ENABLED, is not being included in the command.c file.
I'm not sure when or why that got dropped, but it effectively removed the 
commands associated with catchall processing along with it. 

I've added an include for config.h to command.c, and that has fixed the 
problem.
/q 


I don't necessarily think this is related to your trouble, but you'll
want to do this fix. The symptom, an empty qmailadmin page, was the same. 


Are you sure you don't want to reconsider using QMT? It's not too late.
Of course if you're having fun with this, then why change course? ;) 


--
-Eric 'shubes'


Thanks for your answers, Eric. 

Lets say I want the fun for now :-) 

I my current production system I use vpopmail-5.4.25, qmailadmin-1.2.12 and 
netqmail-1.05 with John M. Simpsons validrcptto.cdb patch. 

On my new system I want to use netqmail-1.06 with Chkuser 2.0 patch and 
vpopmail-5.4.33 with the usage daemon. 


I have installed vpopmail-5.5.0 in combination with qmailadmin-1.2.16, and
qmailadmin-1.2.15 in combination with vpopmail-5.4.33.
I have done the installs of qmailadmin without strip. 


I still get the same error: double free or corruption with no output I
( and the hackers in my company ;-) find usefull. 

The fact that the error do not change indicates that the error is somewhere 
else. 

Is there anybody out there that have any suggestions, where to look ? 

I am looking forward to your answers. 

Thanks in advance. 


Best regards,
Allan Dukat

!DSPAM:519b6d5a34131853810057!

[qmailadmin] Re: [SPAM] qmailadmin 1.2.16 questions

[Eric Shubert]

On 05/21/2013 08:43 AM, Allan Dukat wrote:

Eric Shubert writes:

On 05/17/2013 05:12 AM, Allan Dukat wrote:



OK, then I have a problem with qmailadmin-1.2.16, configured like this:
./configure \
  --enable-vpopmaildir=/home/vpopmail \
  --enable-htmldir=/usr/local/apache2/htdocs \
  --enable-cgibindir=/usr/local/apache2/cgi-bin \
  --enable-imageurl=/images/qmailadmin \
  --enable-imagedir=/usr/local/apache2/htdocs/images/qmailadmin \
  --enable-qmaildir=/var/qmail \
  --enable-ezmlmdir=/usr/local/bin/ezmlm \
  --enable-cgipath=/cgi-bin/qmailadmin \
  --enable-autoresponder-path=/usr/local/bin \
  --enable-vpopuser=vpopmail \
  --enable-vpopgroup=vchkpw \
  --disable-ezmlm-mysql \
  --enable-modify-quota \
  --enable-help
When adding the fist Forward I got an empty page as answer, an this in
Apache errorlog:
*** glibc detected *** /usr/local/apache2/cgi-bin/qmailadmin: double
free or corruption (top): 0x01f326e0 ***



The Forward is added an I can add and list Forwards from now on, when
the last Forward is deleted the error is repeated with the same
addresses as far I can see.
I Use Ubuntu 12.04.2 LTS, x86_64, fully patched.
And openssl-1.0.1e, netqmail-1.06, chkuser-2.0.9-release.patch,
qmail-authentication-081, ucspi-tcp-0.88, daemontools-0.76, pcre-8.32,
maildrop-2.6.0, vpopmail-5.4.33, ezmlm-idx-7.1.1, dovecot-2.2.1,
apr-1.4.6,
apr-util-1.5.2, httpd-2.4.4, courier-authlib-0.65.0, sqwebmail-5.6.1,
autorespond-2.0.4, qmailadmin-1.2.16, qmailadmin-help-1.0.8 and
vqadmin-2.3.7 all configure-make-install.
Spam Filter is elsewhere.
I hope that anybody out there can figure out what I did wrong.



Best regards,
Allan Dukat


I misspoke. There was one problem, a bug I fixed and reported on the
vpopmail list about 3 months ago. Here's a snip:
q
I've had a look at the code, and found that the config.h file, which
defines CATCHALL_ENABLED, is not being included in the command.c file.
I'm not sure when or why that got dropped, but it effectively removed
the commands associated with catchall processing along with it.
I've added an include for config.h to command.c, and that has fixed
the problem.
/q
I don't necessarily think this is related to your trouble, but you'll
want to do this fix. The symptom, an empty qmailadmin page, was the same.
Are you sure you don't want to reconsider using QMT? It's not too late.
Of course if you're having fun with this, then why change course? ;)
--
-Eric 'shubes'


Thanks for your answers, Eric.
Lets say I want the fun for now :-)
I my current production system I use vpopmail-5.4.25, qmailadmin-1.2.12
and netqmail-1.05 with John M. Simpsons validrcptto.cdb patch.
On my new system I want to use netqmail-1.06 with Chkuser 2.0 patch and
vpopmail-5.4.33 with the usage daemon.
I have installed vpopmail-5.5.0 in combination with qmailadmin-1.2.16, and
qmailadmin-1.2.15 in combination with vpopmail-5.4.33.
I have done the installs of qmailadmin without strip.
I still get the same error: double free or corruption with no output I
( and the hackers in my company ;-) find usefull.
The fact that the error do not change indicates that the error is
somewhere else.
Is there anybody out there that have any suggestions, where to look ?
I am looking forward to your answers.
Thanks in advance.
Best regards,
Allan Dukat






I agree that the error is probably somewhere else.
You might try the vpopmail list. I believe there are a few folks there 
who have successfully built on debian. I wouldn't expect there to be 
much difference on Ubuntu, but who knows.

Good luck!

--
-Eric 'shubes'


!DSPAM:519b740534134524912959!

[qmailadmin] Re: [SPAM] qmailadmin 1.2.16 questions

[Allan Dukat]

Eric Shubert writes: 


qmail-toaster (http://wiki.qmailtoaster.com) is presently on
vpopmail-5.4.33 with qmailadmin-1.2.16. There haven't been any problems 
reported.


OK, then I have a problem with qmailadmin-1.2.16, configured like this: 


./configure \
 --enable-vpopmaildir=/home/vpopmail \
 --enable-htmldir=/usr/local/apache2/htdocs \
 --enable-cgibindir=/usr/local/apache2/cgi-bin \
 --enable-imageurl=/images/qmailadmin \
 --enable-imagedir=/usr/local/apache2/htdocs/images/qmailadmin \
 --enable-qmaildir=/var/qmail \
 --enable-ezmlmdir=/usr/local/bin/ezmlm \
 --enable-cgipath=/cgi-bin/qmailadmin \
 --enable-autoresponder-path=/usr/local/bin \
 --enable-vpopuser=vpopmail \
 --enable-vpopgroup=vchkpw \
 --disable-ezmlm-mysql \
 --enable-modify-quota \
 --enable-help 

When adding the fist Forward I got an empty page as answer, an this in 
Apache errorlog: 

*** glibc detected *** /usr/local/apache2/cgi-bin/qmailadmin: double free 
or corruption (top): 0x01f326e0 ***

=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f9ed7c8ab96]
/usr/local/apache2/cgi-bin/qmailadmin[0x421f04]
/usr/local/apache2/cgi-bin/qmailadmin[0x4219ad]
/usr/local/apache2/cgi-bin/qmailadmin[0x42202f]
/usr/local/apache2/cgi-bin/qmailadmin[0x40715d]
/usr/local/apache2/cgi-bin/qmailadmin[0x4070a3]
/usr/local/apache2/cgi-bin/qmailadmin[0x4054f5]
/usr/local/apache2/cgi-bin/qmailadmin[0x4130c3]
/usr/local/apache2/cgi-bin/qmailadmin[0x402db6]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f9ed7c2d76d]
/usr/local/apache2/cgi-bin/qmailadmin[0x402929]
=== Memory map: 
0040-00434000 r-xp  08:01 266154 
/usr/local/apache2/cgi-bin/qmailadmin
00633000-00634000 r--p 00033000 08:01 266154 
/usr/local/apache2/cgi-bin/qmailadmin
00634000-00635000 rw-p 00034000 08:01 266154 
/usr/local/apache2/cgi-bin/qmailadmin

00635000-00641000 rw-p  00:00 0
00fad000-00fce000 rw-p  00:00 0  
[heap]
7f9ed79f6000-7f9ed7a0b000 r-xp  08:01 2359340
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9ed7a0b000-7f9ed7c0a000 ---p 00015000 08:01 2359340
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9ed7c0a000-7f9ed7c0b000 r--p 00014000 08:01 2359340
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9ed7c0b000-7f9ed7c0c000 rw-p 00015000 08:01 2359340
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9ed7c0c000-7f9ed7dc1000 r-xp  08:01 2359318
/lib/x86_64-linux-gnu/libc-2.15.so
7f9ed7dc1000-7f9ed7fc ---p 001b5000 08:01 2359318
/lib/x86_64-linux-gnu/libc-2.15.so
7f9ed7fc-7f9ed7fc4000 r--p 001b4000 08:01 2359318
/lib/x86_64-linux-gnu/libc-2.15.so
7f9ed7fc4000-7f9ed7fc6000 rw-p 001b8000 08:01 2359318
/lib/x86_64-linux-gnu/libc-2.15.so

7f9ed7fc6000-7f9ed7fcb000 rw-p  00:00 0
7f9ed7fcb000-7f9ed7fd4000 r-xp  08:01 2359333
/lib/x86_64-linux-gnu/libcrypt-2.15.so
7f9ed7fd4000-7f9ed81d4000 ---p 9000 08:01 2359333
/lib/x86_64-linux-gnu/libcrypt-2.15.so
7f9ed81d4000-7f9ed81d5000 r--p 9000 08:01 2359333
/lib/x86_64-linux-gnu/libcrypt-2.15.so
7f9ed81d5000-7f9ed81d6000 rw-p a000 08:01 2359333
/lib/x86_64-linux-gnu/libcrypt-2.15.so

7f9ed81d6000-7f9ed8204000 rw-p  00:00 0
7f9ed8204000-7f9ed8226000 r-xp  08:01 2359532
/lib/x86_64-linux-gnu/ld-2.15.so

7f9ed841a000-7f9ed841d000 rw-p  00:00 0
7f9ed842-7f9ed8426000 rw-p  00:00 0
7f9ed8426000-7f9ed8427000 r--p 00022000 08:01 2359532
/lib/x86_64-linux-gnu/ld-2.15.so
7f9ed8427000-7f9ed8429000 rw-p 00023000 08:01 2359532
/lib/x86_64-linux-gnu/ld-2.15.so
7fffec1e6000-7fffec207000 rw-p  00:00 0  
[stack]
7fffec37b000-7fffec37c000 r-xp  00:00 0  
[vdso]
ff60-ff601000 r-xp  00:00 0  
[vsyscall] 

The Forward is added an I can add and list Forwards from now on, when the 
last Forward is deleted the error is repeated with the same addresses as 
far I can see. 


I Use Ubuntu 12.04.2 LTS, x86_64, fully patched.
And openssl-1.0.1e, netqmail-1.06, chkuser-2.0.9-release.patch,
qmail-authentication-081, ucspi-tcp-0.88, daemontools-0.76, pcre-8.32,
maildrop-2.6.0, vpopmail-5.4.33, ezmlm-idx-7.1.1, dovecot-2.2.1, apr-1.4.6,
apr-util-1.5.2, httpd-2.4.4, courier-authlib-0.65.0, sqwebmail-5.6.1,
autorespond-2.0.4, qmailadmin-1.2.16, qmailadmin-help-1.0.8 and
vqadmin-2.3.7 all configure-make-install.
Spam Filter is elsewhere. 


I hope that anybody out there can figure out what I did wrong.

I hope you give qmail-toaster consideration. It has a lot of users with a 
friendly and helpful community base. Disclaimer: I'm the 

Re: [qmailadmin] [SPAM] qmailadmin 1.2.16 questions

[Tom Collins]

You haven't done anything wrong.  I seem to recall seeing this error in the 
past.  I run a modified version of 1.2.12 myself, and can't recall if I've had 
to fix this bug in the past or not (I guess I could try diffing against stock 
1.2.12 and review my changes).

If you reinstall qmailadmin with install instead of install-strip, that 
backtrace might contain the names of functions and it would be easier to track 
down the bug.

-Tom


On May 17, 2013, at 5:12 AM, Allan Dukat wrote:

 Eric Shubert writes: 
 qmail-toaster (http://wiki.qmailtoaster.com) is presently on
 vpopmail-5.4.33 with qmailadmin-1.2.16. There haven't been any problems 
 reported.
 
 OK, then I have a problem with qmailadmin-1.2.16, configured like this: 
 ./configure \
 --enable-vpopmaildir=/home/vpopmail \
 --enable-htmldir=/usr/local/apache2/htdocs \
 --enable-cgibindir=/usr/local/apache2/cgi-bin \
 --enable-imageurl=/images/qmailadmin \
 --enable-imagedir=/usr/local/apache2/htdocs/images/qmailadmin \
 --enable-qmaildir=/var/qmail \
 --enable-ezmlmdir=/usr/local/bin/ezmlm \
 --enable-cgipath=/cgi-bin/qmailadmin \
 --enable-autoresponder-path=/usr/local/bin \
 --enable-vpopuser=vpopmail \
 --enable-vpopgroup=vchkpw \
 --disable-ezmlm-mysql \
 --enable-modify-quota \
 --enable-help 
 When adding the fist Forward I got an empty page as answer, an this in Apache 
 errorlog: 
 *** glibc detected *** /usr/local/apache2/cgi-bin/qmailadmin: double free or 
 corruption (top): 0x01f326e0 ***
 === Backtrace: =
 /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f9ed7c8ab96]
 /usr/local/apache2/cgi-bin/qmailadmin[0x421f04]
 /usr/local/apache2/cgi-bin/qmailadmin[0x4219ad]
 /usr/local/apache2/cgi-bin/qmailadmin[0x42202f]
 /usr/local/apache2/cgi-bin/qmailadmin[0x40715d]
 /usr/local/apache2/cgi-bin/qmailadmin[0x4070a3]
 /usr/local/apache2/cgi-bin/qmailadmin[0x4054f5]
 /usr/local/apache2/cgi-bin/qmailadmin[0x4130c3]
 /usr/local/apache2/cgi-bin/qmailadmin[0x402db6]
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f9ed7c2d76d]
 /usr/local/apache2/cgi-bin/qmailadmin[0x402929]
 === Memory map: 
 0040-00434000 r-xp  08:01 266154 
 /usr/local/apache2/cgi-bin/qmailadmin
 00633000-00634000 r--p 00033000 08:01 266154 
 /usr/local/apache2/cgi-bin/qmailadmin
 00634000-00635000 rw-p 00034000 08:01 266154 
 /usr/local/apache2/cgi-bin/qmailadmin
 00635000-00641000 rw-p  00:00 0
 00fad000-00fce000 rw-p  00:00 0  
 [heap]
 7f9ed79f6000-7f9ed7a0b000 r-xp  08:01 2359340
 /lib/x86_64-linux-gnu/libgcc_s.so.1
 7f9ed7a0b000-7f9ed7c0a000 ---p 00015000 08:01 2359340
 /lib/x86_64-linux-gnu/libgcc_s.so.1
 7f9ed7c0a000-7f9ed7c0b000 r--p 00014000 08:01 2359340
 /lib/x86_64-linux-gnu/libgcc_s.so.1
 7f9ed7c0b000-7f9ed7c0c000 rw-p 00015000 08:01 2359340
 /lib/x86_64-linux-gnu/libgcc_s.so.1
 7f9ed7c0c000-7f9ed7dc1000 r-xp  08:01 2359318
 /lib/x86_64-linux-gnu/libc-2.15.so
 7f9ed7dc1000-7f9ed7fc ---p 001b5000 08:01 2359318
 /lib/x86_64-linux-gnu/libc-2.15.so
 7f9ed7fc-7f9ed7fc4000 r--p 001b4000 08:01 2359318
 /lib/x86_64-linux-gnu/libc-2.15.so
 7f9ed7fc4000-7f9ed7fc6000 rw-p 001b8000 08:01 2359318
 /lib/x86_64-linux-gnu/libc-2.15.so
 7f9ed7fc6000-7f9ed7fcb000 rw-p  00:00 0
 7f9ed7fcb000-7f9ed7fd4000 r-xp  08:01 2359333
 /lib/x86_64-linux-gnu/libcrypt-2.15.so
 7f9ed7fd4000-7f9ed81d4000 ---p 9000 08:01 2359333
 /lib/x86_64-linux-gnu/libcrypt-2.15.so
 7f9ed81d4000-7f9ed81d5000 r--p 9000 08:01 2359333
 /lib/x86_64-linux-gnu/libcrypt-2.15.so
 7f9ed81d5000-7f9ed81d6000 rw-p a000 08:01 2359333
 /lib/x86_64-linux-gnu/libcrypt-2.15.so
 7f9ed81d6000-7f9ed8204000 rw-p  00:00 0
 7f9ed8204000-7f9ed8226000 r-xp  08:01 2359532
 /lib/x86_64-linux-gnu/ld-2.15.so
 7f9ed841a000-7f9ed841d000 rw-p  00:00 0
 7f9ed842-7f9ed8426000 rw-p  00:00 0
 7f9ed8426000-7f9ed8427000 r--p 00022000 08:01 2359532
 /lib/x86_64-linux-gnu/ld-2.15.so
 7f9ed8427000-7f9ed8429000 rw-p 00023000 08:01 2359532
 /lib/x86_64-linux-gnu/ld-2.15.so
 7fffec1e6000-7fffec207000 rw-p  00:00 0  
 [stack]
 7fffec37b000-7fffec37c000 r-xp  00:00 0  
 [vdso]
 ff60-ff601000 r-xp  00:00 0  
 [vsyscall] 
 The Forward is added an I can add and list Forwards from now on, when the 
 last Forward is deleted the error is repeated with the same addresses as far 
 I can see. 
 I Use Ubuntu 12.04.2 LTS, x86_64, fully patched.
 And openssl-1.0.1e, netqmail-1.06, 

[qmailadmin] Re: [SPAM] qmailadmin 1.2.16 questions

[Eric Shubert]

On 05/17/2013 05:12 AM, Allan Dukat wrote:

Eric Shubert writes:

qmail-toaster (http://wiki.qmailtoaster.com) is presently on
vpopmail-5.4.33 with qmailadmin-1.2.16. There haven't been any
problems reported.


OK, then I have a problem with qmailadmin-1.2.16, configured like this:
./configure \
  --enable-vpopmaildir=/home/vpopmail \
  --enable-htmldir=/usr/local/apache2/htdocs \
  --enable-cgibindir=/usr/local/apache2/cgi-bin \
  --enable-imageurl=/images/qmailadmin \
  --enable-imagedir=/usr/local/apache2/htdocs/images/qmailadmin \
  --enable-qmaildir=/var/qmail \
  --enable-ezmlmdir=/usr/local/bin/ezmlm \
  --enable-cgipath=/cgi-bin/qmailadmin \
  --enable-autoresponder-path=/usr/local/bin \
  --enable-vpopuser=vpopmail \
  --enable-vpopgroup=vchkpw \
  --disable-ezmlm-mysql \
  --enable-modify-quota \
  --enable-help
When adding the fist Forward I got an empty page as answer, an this in
Apache errorlog:
*** glibc detected *** /usr/local/apache2/cgi-bin/qmailadmin: double
free or corruption (top): 0x01f326e0 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f9ed7c8ab96]
/usr/local/apache2/cgi-bin/qmailadmin[0x421f04]
/usr/local/apache2/cgi-bin/qmailadmin[0x4219ad]
/usr/local/apache2/cgi-bin/qmailadmin[0x42202f]
/usr/local/apache2/cgi-bin/qmailadmin[0x40715d]
/usr/local/apache2/cgi-bin/qmailadmin[0x4070a3]
/usr/local/apache2/cgi-bin/qmailadmin[0x4054f5]
/usr/local/apache2/cgi-bin/qmailadmin[0x4130c3]
/usr/local/apache2/cgi-bin/qmailadmin[0x402db6]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f9ed7c2d76d]
/usr/local/apache2/cgi-bin/qmailadmin[0x402929]
=== Memory map: 
0040-00434000 r-xp  08:01 266154
/usr/local/apache2/cgi-bin/qmailadmin
00633000-00634000 r--p 00033000 08:01 266154
/usr/local/apache2/cgi-bin/qmailadmin
00634000-00635000 rw-p 00034000 08:01 266154
/usr/local/apache2/cgi-bin/qmailadmin
00635000-00641000 rw-p  00:00 0
00fad000-00fce000 rw-p  00:00 0 [heap]
7f9ed79f6000-7f9ed7a0b000 r-xp  08:01 2359340
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9ed7a0b000-7f9ed7c0a000 ---p 00015000 08:01 2359340
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9ed7c0a000-7f9ed7c0b000 r--p 00014000 08:01 2359340
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9ed7c0b000-7f9ed7c0c000 rw-p 00015000 08:01 2359340
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9ed7c0c000-7f9ed7dc1000 r-xp  08:01 2359318
/lib/x86_64-linux-gnu/libc-2.15.so
7f9ed7dc1000-7f9ed7fc ---p 001b5000 08:01 2359318
/lib/x86_64-linux-gnu/libc-2.15.so
7f9ed7fc-7f9ed7fc4000 r--p 001b4000 08:01 2359318
/lib/x86_64-linux-gnu/libc-2.15.so
7f9ed7fc4000-7f9ed7fc6000 rw-p 001b8000 08:01 2359318
/lib/x86_64-linux-gnu/libc-2.15.so
7f9ed7fc6000-7f9ed7fcb000 rw-p  00:00 0
7f9ed7fcb000-7f9ed7fd4000 r-xp  08:01 2359333
/lib/x86_64-linux-gnu/libcrypt-2.15.so
7f9ed7fd4000-7f9ed81d4000 ---p 9000 08:01 2359333
/lib/x86_64-linux-gnu/libcrypt-2.15.so
7f9ed81d4000-7f9ed81d5000 r--p 9000 08:01 2359333
/lib/x86_64-linux-gnu/libcrypt-2.15.so
7f9ed81d5000-7f9ed81d6000 rw-p a000 08:01 2359333
/lib/x86_64-linux-gnu/libcrypt-2.15.so
7f9ed81d6000-7f9ed8204000 rw-p  00:00 0
7f9ed8204000-7f9ed8226000 r-xp  08:01 2359532
/lib/x86_64-linux-gnu/ld-2.15.so
7f9ed841a000-7f9ed841d000 rw-p  00:00 0
7f9ed842-7f9ed8426000 rw-p  00:00 0
7f9ed8426000-7f9ed8427000 r--p 00022000 08:01 2359532
/lib/x86_64-linux-gnu/ld-2.15.so
7f9ed8427000-7f9ed8429000 rw-p 00023000 08:01 2359532
/lib/x86_64-linux-gnu/ld-2.15.so
7fffec1e6000-7fffec207000 rw-p  00:00 0 [stack]
7fffec37b000-7fffec37c000 r-xp  00:00 0 [vdso]
ff60-ff601000 r-xp  00:00 0 [vsyscall]
The Forward is added an I can add and list Forwards from now on, when
the last Forward is deleted the error is repeated with the same
addresses as far I can see.
I Use Ubuntu 12.04.2 LTS, x86_64, fully patched.
And openssl-1.0.1e, netqmail-1.06, chkuser-2.0.9-release.patch,
qmail-authentication-081, ucspi-tcp-0.88, daemontools-0.76, pcre-8.32,
maildrop-2.6.0, vpopmail-5.4.33, ezmlm-idx-7.1.1, dovecot-2.2.1, apr-1.4.6,
apr-util-1.5.2, httpd-2.4.4, courier-authlib-0.65.0, sqwebmail-5.6.1,
autorespond-2.0.4, qmailadmin-1.2.16, qmailadmin-help-1.0.8 and
vqadmin-2.3.7 all configure-make-install.
Spam Filter is elsewhere.
I hope that anybody out there can figure out what I did wrong.


I hope you give qmail-toaster consideration. It has a lot of users
with a friendly and helpful community base. Disclaimer: I'm the
project lead, so I'm indubitably biased. ;)


I have, and now I can not remember why I choose to compile everything
myself to start with ;-(
Thanks in advance.
Best regards,
Allan Dukat






I misspoke. There was one problem, a bug I fixed and reported on the 
vpopmail list about 3 months ago. Here's a snip:

q
I've had a look at the code, and found that the config.h file, which 
defines CATCHALL_ENABLED, is not being included in the command.c file. 
I'm 

[qmailadmin] Re: [SPAM] qmailadmin 1.2.16 questions

[Eric Shubert]

On 05/15/2013 08:48 AM, Allan Dukat wrote:

Hi everyone
I am upgrading my mailserver, and want to use the latest versions of all
software, thus I am tryning to get vpopmail-5.4.33 and qmailadmin-1.2.16
to work together and get this error
*** glibc detected *** cgi-bin/qmailadmin: double free or corruption
when adding the first Forwards.
On Tue, 22 Nov 2011 Johannes Weberhofer wrote:
For qmailadmin 1.2.16 you need vpopmail 5.5(-devel). Could be fixed
using an older version, I think it's 1.2.15 that you need.
 From qmailadmin-1.2.16/ChangeLog:
1.2.14-1.2.16
Matt Brookings
- Removed mailbox image
 - Updated quota code to work with vpopmail v5.4.33
 - Fixed some compiler warnings
 - Updated default compiler flags
 - Updated package version string
 - Fixed some format string warnings
 - Reserved language template file codes 400 through 450 for custom
autoresponder headers
 - Added code to support custom autoresponder headers per language
Is it correct that this versions do not work together?
Is it OK to use vpopmail-devel-5.5.0 in production, it is not updated
since 2010-11-05?
Or would it be safest to use qmailadmin-1.2.13 whith vpopmail-5.4.33?
What is the recommendation from this list?
I am looking forward to your answers.
Best regards,
Allan Dukat



qmail-toaster (http://wiki.qmailtoaster.com) is presently on
vpopmail-5.4.33 with qmailadmin-1.2.16. There haven't been any problems 
reported.


I don't know to what extent 5.5 is ready for production. It's not been 
deemed stable yet to my knowledge. I've been waiting for some time to 
try out 5.5 with ldap support, but last I recall Matt was still ironing 
out the schema for that.


I hope you give qmail-toaster consideration. It has a lot of users with 
a friendly and helpful community base. Disclaimer: I'm the project lead, 
so I'm indubitably biased. ;)


--
-Eric 'shubes'


!DSPAM:5194f91734126691677620!

[qmailadmin] [SPAM] qmailadmin 1.2.16 questions

[Allan Dukat]

Hi everyone 

I am upgrading my mailserver, and want to use the latest versions of all 
software, thus I am tryning to get vpopmail-5.4.33 and qmailadmin-1.2.16 to 
work together and get this error 

*** glibc detected *** cgi-bin/qmailadmin: double free or corruption 

when adding the first Forwards. 

On Tue, 22 Nov 2011 Johannes Weberhofer wrote: 

For qmailadmin 1.2.16 you need vpopmail 5.5(-devel). Could be fixed using 
an older version, I think it's 1.2.15 that you need. 

From qmailadmin-1.2.16/ChangeLog: 


1.2.14-1.2.16
   Matt Brookings
   - Removed mailbox image
- Updated quota code to work with vpopmail v5.4.33
- Fixed some compiler warnings
- Updated default compiler flags
- Updated package version string
- Fixed some format string warnings
	- Reserved language template file codes 400 through 450 for custom 
autoresponder headers
	- Added code to support custom autoresponder headers per language 

Is it correct that this versions do not work together? 

Is it OK to use vpopmail-devel-5.5.0 in production, it is not updated since 
2010-11-05? 

Or would it be safest to use qmailadmin-1.2.13 whith vpopmail-5.4.33? 

What is the recommendation from this list? 

I am looking forward to your answers. 


Best regards,
Allan Dukat

!DSPAM:5193855f34124921740985!

[qmailadmin] [SPAM] Re: [qmailadmin] slow smtp connection

[Arch Giulio Nuti]

Il 11/05/2013 20:21, Eric Shubert ha scritto:


Sluggish performance is often a symptom of improper DNS configuration. 
What's in your /etc/resolv.conf file?

Is the address you're submitting from one of those listed in tcp.smtpd?



This is what I supposed.
I submit emails from private IP (192.168.x.x) the server has two 
interfaces: a private IP (192.168.x.x) and a public IP (37.205.xx.xx)

The problem is on both interfaces.

I did not change anything (I'm pretty sure) but in the last month the 
connection has gone worse and worse.


I think I'll write a brand new DNS config. But may be I have some 
problem in the firewall config.


Thanks

--
Giulio Nuti


Questo messaggio di posta elettronica contiene informazioni di carattere
confidenziale rivolte esclusivamente al destinatario sopra indicato.
E' vietato l'uso, la diffusione, distribuzione o riproduzione da parte
di ogni altra personain accordo alle direttive del DL 196/03
Nel caso aveste ricevuto questo messaggio di posta elettronica per
errore, siete pregati di segnalarlo immediatamente al mittente e
distruggere quanto ricevuto (compresi file allegati) senza farne copia.
Qualsivoglia utilizzo non autorizzato del contenuto di questo messaggio
costituisce violazione dell'obbligo di non prendere cognizione della
corrispondenza tra gli altri soggetti, salvo più grave illecito, ed
espone il responsabile alle relative conseguenze.
 
Confidentiality Notice. This electronic mail transmission may contain

legally priviledge and/or confidential information. Do not read this if
you are not the person(s) named.
Any use, distribution, copying or disclosure by any other person is
stricly prohibited (DL 196/03).
If you received this trasmission in error, please notify the sender and
destroy the original transmission and its attachments without reading or
saving in any manner.
---


!DSPAM:5190933634123720718861!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] slow smtp connection

[Bob Miller]

 
 I did not change anything (I'm pretty sure) but in the last month the 
 connection has gone worse and worse.

Maybe check your queue (ie qmail-qstat/qmail-qread)...


!DSPAM:5190eb8c34121570810489!

[qmailadmin] Re: [SPAM] Re: [qmailadmin] slow smtp connection

[Eric Shubert]

On 05/13/2013 03:09 AM, Arch Giulio Nuti wrote:

Il 11/05/2013 20:21, Eric Shubert ha scritto:


Sluggish performance is often a symptom of improper DNS configuration.
What's in your /etc/resolv.conf file?
Is the address you're submitting from one of those listed in tcp.smtpd?



This is what I supposed.
I submit emails from private IP (192.168.x.x) the server has two
interfaces: a private IP (192.168.x.x) and a public IP (37.205.xx.xx)
The problem is on both interfaces.

I did not change anything (I'm pretty sure) but in the last month the
connection has gone worse and worse.

I think I'll write a brand new DNS config. But may be I have some
problem in the firewall config.

Thanks



In that case also check your routing tables. I've seen misconfigurations 
where every other packet got sent to the wrong interface.


--
-Eric 'shubes'


!DSPAM:51912f9634123791914573!

[qmailadmin] Re: [SPAM] slow smtp connection

[Eric Shubert]

On 05/09/2013 11:23 AM, Arch Giulio Nuti wrote:

Hi
I've been using debian with qmail since last september (from 1998 to
2012 with Slackware). No big problems.
it is some days that my local smtp server is slow:35 seconds to
accept an email sent from me to a localnet address.

  cat tcp.smtp
127.:allow,RELAYCLIENT=
192.168.1.23:allow,RELAYCLIENT=
192.168.1.:allow,RELAYCLIENT=
37.205.134.210:allow,RELAYCLIENT=,QMAILQUEUE=/var/qmail/bin/qmail-queue,RBLSMTPD=

37.205.134.211:allow,RELAYCLIENT=,QMAILQUEUE=/var/qmail/bin/qmail-queue,RBLSMTPD=

85.18.95.80:deny
85.18.245.130:deny
94.76.244.144:deny
101.80.2.:deny
-

I did not change any settings in DNS.

Not shown: 984 closed ports
PORT  STATE SERVICE
22/tcpopen  ssh
25/tcpopen  smtp
80/tcpopen  http
110/tcp   open  pop3
111/tcp   open  rpcbind
139/tcp   open  netbios-ssn
143/tcp   open  imap
445/tcp   open  microsoft-ds
465/tcp   open  smtps
783/tcp   open  spamassassin
901/tcp   open  samba-swat
993/tcp   open  imaps
995/tcp   open  pop3s
2049/tcp  open  nfs
3306/tcp  open  mysql
1/tcp open  snet-sensor-mgmt

It seems there is no particular connection from Outside.


Could it depend from a DNS problem? I tried to compile a hosts file
and I have a DNS local server which seems to run fine...
Any Idea? I don't know where to start.


Thanks



Sluggish performance is often a symptom of improper DNS configuration. 
What's in your /etc/resolv.conf file?

Is the address you're submitting from one of those listed in tcp.smtpd?

--
-Eric 'shubes'


!DSPAM:518e643034121333613835!

[qmailadmin] [SPAM] slow smtp connection

[Arch Giulio Nuti]

Hi
I've been using debian with qmail since last september (from 1998 to 
2012 with Slackware). No big problems.
it is some days that my local smtp server is slow:35 seconds to 
accept an email sent from me to a localnet address.


 cat tcp.smtp
127.:allow,RELAYCLIENT=
192.168.1.23:allow,RELAYCLIENT=
192.168.1.:allow,RELAYCLIENT=
37.205.134.210:allow,RELAYCLIENT=,QMAILQUEUE=/var/qmail/bin/qmail-queue,RBLSMTPD=
37.205.134.211:allow,RELAYCLIENT=,QMAILQUEUE=/var/qmail/bin/qmail-queue,RBLSMTPD=
85.18.95.80:deny
85.18.245.130:deny
94.76.244.144:deny
101.80.2.:deny
-

I did not change any settings in DNS.

Not shown: 984 closed ports
PORT  STATE SERVICE
22/tcpopen  ssh
25/tcpopen  smtp
80/tcpopen  http
110/tcp   open  pop3
111/tcp   open  rpcbind
139/tcp   open  netbios-ssn
143/tcp   open  imap
445/tcp   open  microsoft-ds
465/tcp   open  smtps
783/tcp   open  spamassassin
901/tcp   open  samba-swat
993/tcp   open  imaps
995/tcp   open  pop3s
2049/tcp  open  nfs
3306/tcp  open  mysql
1/tcp open  snet-sensor-mgmt

It seems there is no particular connection from Outside.


Could it depend from a DNS problem? I tried to compile a hosts file 
and I have a DNS local server which seems to run fine...

Any Idea? I don't know where to start.


Thanks

--
Giulio

Questo messaggio di posta elettronica contiene informazioni di carattere
confidenziale rivolte esclusivamente al destinatario sopra indicato.
E' vietato l'uso, la diffusione, distribuzione o riproduzione da parte
di ogni altra personain accordo alle direttive del DL 196/03
Nel caso aveste ricevuto questo messaggio di posta elettronica per
errore, siete pregati di segnalarlo immediatamente al mittente e
distruggere quanto ricevuto (compresi file allegati) senza farne copia.
Qualsivoglia utilizzo non autorizzato del contenuto di questo messaggio
costituisce violazione dell'obbligo di non prendere cognizione della
corrispondenza tra gli altri soggetti, salvo più grave illecito, ed
espone il responsabile alle relative conseguenze.
 
Confidentiality Notice. This electronic mail transmission may contain

legally priviledge and/or confidential information. Do not read this if
you are not the person(s) named.
Any use, distribution, copying or disclosure by any other person is
stricly prohibited (DL 196/03).
If you received this trasmission in error, please notify the sender and
destroy the original transmission and its attachments without reading or
saving in any manner.
---


!DSPAM:518bc0e834122023981350!

Re: [qmailadmin] qmailadmin password change with test password strenght

[Tom Collins]

You might want to try this patch out -- it uses cracklib to enforce strong 
passwords.

http://sourceforge.net/tracker/?func=detailaid=1553526group_id=6691atid=306691

I don't know if it will still cleanly apply to the current version, but it 
could be a starting point for you.

-Tom


On Mar 17, 2013, at 11:00 PM, Nicholas C. wrote:

 Hi,
 
 Can I engage someone to write an add-on to do a password strength check?
 
 Many thanks
 
 -Original Message-
 From: Nicholas C. [mailto:nicholasc...@outlook.com] 
 Sent: Monday, 11 March, 2013 12:43 PM
 To: qmailadmin@inter7.com
 Subject: [qmailadmin] qmailadmin password change with test password strenght
 
 Hi,
 
 How can I add a password strength test in qmailadmin? 
 
 Regards
 Nic 
 
 
 
 
 
 
 
 


!DSPAM:5149097f34146777445199!

RE: [qmailadmin] [SPAM] Re: [qmailadmin] toaster-watcher cronjob errors

[Matt Rauch]

Thanks. I have stopped it for now. Disabled isoqlogd in toaster-watcher.
I'll do more digging.

Matt Rauch 

 -Original Message-
 From: Bob Miller [mailto:b...@computerisms.ca] 
 Sent: March-12-13 9:45 PM
 To: qmailadmin@inter7.com
 Subject: [qmailadmin] [SPAM] Re: [qmailadmin] toaster-watcher 
 cronjob errors
 
 
  
  fopen: @4000513f204b35d8b0dc.s: No such file or directory
  syscmd: /usr/local/bin/isoqlog /dev/null
  syscmd: result: 65280
  
  If I had to guess I would think its trying to open a temp 
 file of some 
  sort since the file its trying to open is different in each 
 instance 
  of the error, but I don't see any files like that In the /tmp 
  directory.
  
  Any help would be greatly appreciated.
 
 I can't speak to your script since I don't use it and don't 
 know what it does, but the file being referenced there is a 
 log file from daemontools.  That might be your qmail logs, or 
 some other service you configured when you built the system.  
 In some cases those files might be located in /var/log/qmail, 
 or it might be located within the service directory structure 
 under /service/qmail-smtpd or some such.  I know that isn't 
 overly helpful, but maybe if you can find where the files are 
 supposed to be you can run the script manually to try and 
 deduce what is happening...
 
 
  
  Thanks,
  
  Matt Rauch
  
  
  
  
  
  
 
 
 
 
 


!DSPAM:514096ff34141470917298!

[qmailadmin] toaster-watcher cronjob errors

[Matt Rauch]

Hello,

Since the weekend, I have started to get the following error from
the toaster-watcher.pl cronjob which is set for every 5 mins:

fopen: @4000513f204b35d8b0dc.s: No such file or directory
syscmd: /usr/local/bin/isoqlog /dev/null
syscmd: result: 65280

I tried looking online, but haven't come across anything of use to point me
I nthe right direction. Just wondering if anyone on here has come across
this before. To my knowledge nothing has been added/removed/upgraded or any
configs changed on the server. If I had to guess I would think its trying to
open a temp file of some sort since the file its trying to open is different
in each instance of the error, but I don't see any files like that In the
/tmp directory.

Any help would be greatly appreciated.

Thanks,

Matt Rauch




!DSPAM:513f40d934142033213326!

[qmailadmin] [SPAM] Re: [qmailadmin] toaster-watcher cronjob errors

[Bob Miller]

 
 fopen: @4000513f204b35d8b0dc.s: No such file or directory
 syscmd: /usr/local/bin/isoqlog /dev/null
 syscmd: result: 65280
 
 If I had to guess I would think its trying to
 open a temp file of some sort since the file its trying to open is different
 in each instance of the error, but I don't see any files like that In the
 /tmp directory.
 
 Any help would be greatly appreciated.

I can't speak to your script since I don't use it and don't know what it
does, but the file being referenced there is a log file from
daemontools.  That might be your qmail logs, or some other service you
configured when you built the system.  In some cases those files might
be located in /var/log/qmail, or it might be located within the service
directory structure under /service/qmail-smtpd or some such.  I know
that isn't overly helpful, but maybe if you can find where the files are
supposed to be you can run the script manually to try and deduce what is
happening...


 
 Thanks,
 
 Matt Rauch
 
 
 
 
 
 


!DSPAM:513fbe9c34144082379809!

[qmailadmin] qmailadmin password change with test password strenght

[Nicholas C .]

Hi,

How can I add a password strength test in qmailadmin? 

Regards
Nic 


!DSPAM:513d457d34149944119995!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] qmailadmin password change with test password strenght

[creditofinanciero]

!DSPAM:51376c2234144353718338!

[qmailadmin] [SPAM] Set number of simultaneous Postmaster logins in qmailadmin

[Matt Rauch]

Hello,

Is there a way to allow more then one Postmaster login in qmailadmin
at the same time? As it is now, if a second person logs in, it will kick out
the first user logged in as Postmaster. If its not possible, just let me
know too.

Thanks,

Matt Rauch


!DSPAM:5106d32834145104417720!

[qmailadmin] [SPAM] Unable to change bounce processing

[Eric Shubert]

I'm running qmailadmin 1.2.16 (with vpopmail 5.4.33), and when I click 
on an account's catchall button or otherwise attempt to change the 
catchall status for the domain, it simply returns a blank page without 
having changed anything. The url appears to be properly formatted, and I 
see what appears to be a normal message in the apache access log. I'm 
running QmailToaster on several hosts, and they all have this problem.


Will someone be so kind as to tell me how I might troubleshoot this?

TIA.

--
-Eric 'shubes'


!DSPAM:50fde82834144827127004!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Unable to change bounce processing

[creditofinanciero]

!DSPAM:50fde84634142078410221!

[qmailadmin] weird problem -

[Arch Giulio Nuti]

Hi all
I installed Debian with qmail (Thibault Richard) and is running fine. 
Sometime something weird is appening.
Down in this email I include the header of an email sended from an 
Italian University server.
The addressee has two email, the first is on my server, another one is 
on gmail.

As You can see  this email has been sent on Friday at 18.23.
The gmail server received the email immediately.
my server received it on sunday ad 22.39

Does it depend on my server or on the sender?
I cannot find any problem on my local server.

Thanks fo Your hints.

Giulio




Return-Path: c.x...@.xx
Delivered-To: danilo.xx...@yyy.yy
Received: (qmail 9644 invoked by uid 89); 13 Jan 2013 22:39:12 +0100
Delivered-To: stxx.danilo...@y.yy
Received: (qmail 9642 invoked by uid 168); 13 Jan 2013 22:39:12 +0100
X-Qmail-Scanner-Diagnostics: from smtp2.uniromxx.xx by v-server 
(envelope-from c.x...@xxx.xx, uid 89) with qmail-scanner-2.10st
 (clamdscan: 0.97.6/16480. mhr: 1.0. spamassassin: 3.3.1. perlscan: 
2.10st.

 Clear:RC:0(62.241.xxx.xxx):SA:0(-2.6/5.0):.
 Processed in 6.857667 secs); 13 Jan 2013 21:39:12 -
X-Spam-Status: No, hits=-2.6 required=5.0
X-Qmail-Scanner-Mail-From: c.x...@xxx.xx via v-server
X-Qmail-Scanner: 2.10st (Clear:RC:0(62.241.xxx.xxx):SA:0(-2.6/5.0):. 
Processed in 6.857667 secs Process 9629)

Received: from smtp2.xx.xx (62.241.xxx.xxx)
  by v-server.cad with SMTP; 13 Jan 2013 22:39:03 +0100
Received-SPF: pass (v-server.cad: SPF record at spf.x.xx designates 
62.241.xxx.xxx as permitted sender)
Received: from camilloPC (193.205.xxx.xxx) by smtp2.xxx.xx (8.0.023) 
(authenticated as c)

id 50DB9E852324; Fri, 11 Jan 2013 18:23:39 +0100
From: sender  c.x...@.xx
To: danilo.yy...@yy.yy,
Danilo gmail danilo.yyy...@gmail.com
References: 
5a584806116a494a9d83d339f4ad23c910c51...@amxprd0410mb377.eurprd04.prod.outlook.com
In-Reply-To: 
5a584806116a494a9d83d339f4ad23c910c51...@amxprd0410mb377.eurprd04.prod.outlook.com

Date: Fri, 11 Jan 2013 18:23:36 +0100

--
Arch. Giulio Nuti


Questo messaggio di posta elettronica contiene informazioni di carattere
confidenziale rivolte esclusivamente al destinatario sopra indicato.
E' vietato l'uso, la diffusione, distribuzione o riproduzione da parte
di ogni altra personain accordo alle direttive del DL 196/03
Nel caso aveste ricevuto questo messaggio di posta elettronica per
errore, siete pregati di segnalarlo immediatamente al mittente e
distruggere quanto ricevuto (compresi file allegati) senza farne copia.
Qualsivoglia utilizzo non autorizzato del contenuto di questo messaggio
costituisce violazione dell'obbligo di non prendere cognizione della
corrispondenza tra gli altri soggetti, salvo più grave illecito, ed
espone il responsabile alle relative conseguenze.
 
Confidentiality Notice. This electronic mail transmission may contain

legally priviledge and/or confidential information. Do not read this if
you are not the person(s) named.
Any use, distribution, copying or disclosure by any other person is
stricly prohibited (DL 196/03).
If you received this trasmission in error, please notify the sender and
destroy the original transmission and its attachments without reading or
saving in any manner.
---


!DSPAM:50f3cf9234146267140474!

[qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f3cfc534149516629476!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f3cfff34141665842892!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f3d01f34145074614598!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f3d05934145943914805!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f3d07834141349571112!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f3d0d234141295914790!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailad

[creditofinanciero]

!DSPAM:50f3d10e34141813810924!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailad

[creditofinanciero]

!DSPAM:50f3d12c34143907295053!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[Bèrto ëd Sèra]

Can someone please ban this address from spamming the list?

On 14 January 2013 11:26,  creditofinanci...@dimasur.com.mx wrote:
 ÉSTE ES UN MENSAJE GENERADO POR EL SISTEMA - LE ROGAMOS QUE NO RESPONDA.
 GRACIAS POR CONTACTARNOS PRONTO SERA ATENDIDO POR UNO DE NUESTROS EJECUTIVOS
 ATENTAMENTE DIRECCION DIMASUR 



-- 
==
If Pac-Man had affected us as kids, we'd all be running around in a
darkened room munching pills and listening to repetitive music.

!DSPAM:50f3d13a34141471139676!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailad

[creditofinanciero]

!DSPAM:50f3d16834141005915012!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f3d18734141957831037!

[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f3d0b334141956814258!

RE: [qmailadmin] weird problem -

[Thibault Richard]

Hello,

The two important lines in your header are :

Received: from camilloPC (193.205.xxx.xxx) by smtp2.xxx.xx (8.0.023)
(authenticated as c)
 id 50DB9E852324; Fri, 11 Jan 2013 18:23:39 +0100

= It indeed means smtp2.xxx.xx has received the instruction to send it
at 11 Jan 2013 18:23:39 +0100

Received: from smtp2.xx.xx (62.241.xxx.xxx)
   by v-server.cad with SMTP; 13 Jan 2013 22:39:03 +0100

= It indeed means smtp2.xx.xx succeed contacting your server only at 13
Jan 2013 22:39:03 +0100

It could means several things

1° There was a system problem (qmail-smtpd down) at 11 Jan 2013 18:23:39
+0100. It suppose this problem has been solved later. I suppose we can
exclude this hypothesis.

2° There was a routing problem between smtp2.xx.xx and your server
around 11 Jan 2013 18:23:39 +0100. 

-The sending server do not succeed sending this mail at 11 Jan 2013 18:23:39
+0100
-Then it retried 5 minutes later (11 Jan 2013 18:28) with the same problem 
-Then it retried 10 minutes later (11 Jan 2013 18:39) with the same problem
-Then it retried 2 hours later (11 Jan 2013 20:39) with the same problem
-Then it retried 2 hours later (11 Jan 2013 22:39) with the same problem
-Then it retried 1 day later (12 Jan 2013 22:39) with the same problem
-Then it retried 1 day later (13 Jan 2013 22:39) to finally succeed!

This hypothesis is based to classical re-try period configured in most of
the MTA

3° smtp2.xx.xx was blacklisted for a while on a blacklist not used my
Gmail

You could find it by determining the IP of smtp2.xx.xx

Try then

grep 62.241.xxx.xxx /var/log/qmail/qmail-smtpd/* 

If this is the case, you should have some record like this

rblsmtpd: 62.241.xxx.xxx pid 2628: 451
http://www.spamhaus.org/query/bl?ip=62.241.xxx.xxx

4° Last hypothesis

You have implemented this feature
http://qmailrocks.thibs.com/greylisting.php 
smtp2.xx.xx has configured strange retry period

I hope this 'll help you

Best Regards

Thibault a.k.a Thibs

-Original Message-
From: Arch Giulio Nuti [mailto:giulio.n...@grupponuti.it] 
Sent: lundi 14 janvier 2013 12:23
To: qmailadmin@inter7.com
Subject: [qmailadmin] weird problem -

Hi all
I installed Debian with qmail (Thibault Richard) and is running fine. 
Sometime something weird is appening.
Down in this email I include the header of an email sended from an Italian
University server.
The addressee has two email, the first is on my server, another one is on
gmail.
As You can see  this email has been sent on Friday at 18.23.
The gmail server received the email immediately.
my server received it on sunday ad 22.39

Does it depend on my server or on the sender?
I cannot find any problem on my local server.

Thanks fo Your hints.

Giulio




Return-Path: c.x...@.xx
Delivered-To: danilo.xx...@yyy.yy
Received: (qmail 9644 invoked by uid 89); 13 Jan 2013 22:39:12 +0100
Delivered-To: stxx.danilo...@y.yy
Received: (qmail 9642 invoked by uid 168); 13 Jan 2013 22:39:12 +0100
X-Qmail-Scanner-Diagnostics: from smtp2.uniromxx.xx by v-server
(envelope-from c.x...@xxx.xx, uid 89) with qmail-scanner-2.10st
  (clamdscan: 0.97.6/16480. mhr: 1.0. spamassassin: 3.3.1. perlscan: 
2.10st.
  Clear:RC:0(62.241.xxx.xxx):SA:0(-2.6/5.0):.
  Processed in 6.857667 secs); 13 Jan 2013 21:39:12 -
X-Spam-Status: No, hits=-2.6 required=5.0
X-Qmail-Scanner-Mail-From: c.x...@xxx.xx via v-server
X-Qmail-Scanner: 2.10st (Clear:RC:0(62.241.xxx.xxx):SA:0(-2.6/5.0):. 
Processed in 6.857667 secs Process 9629)
Received: from smtp2.xx.xx (62.241.xxx.xxx)
   by v-server.cad with SMTP; 13 Jan 2013 22:39:03 +0100
Received-SPF: pass (v-server.cad: SPF record at spf.x.xx designates
62.241.xxx.xxx as permitted sender)
Received: from camilloPC (193.205.xxx.xxx) by smtp2.xxx.xx (8.0.023)
(authenticated as c)
 id 50DB9E852324; Fri, 11 Jan 2013 18:23:39 +0100
From: sender  c.x...@.xx
To: danilo.yy...@yy.yy,
 Danilo gmail danilo.yyy...@gmail.com
References: 
5a584806116a494a9d83d339f4ad23c910c51...@amxprd0410mb377.eurprd04.prod.outl
ook.com
In-Reply-To: 
5a584806116a494a9d83d339f4ad23c910c51...@amxprd0410mb377.eurprd04.prod.outl
ook.com
Date: Fri, 11 Jan 2013 18:23:36 +0100

--
Arch. Giulio Nuti


Questo messaggio di posta elettronica contiene informazioni di carattere
confidenziale rivolte esclusivamente al destinatario sopra indicato.
E' vietato l'uso, la diffusione, distribuzione o riproduzione da parte
di ogni altra personain accordo alle direttive del DL 196/03
Nel caso aveste ricevuto questo messaggio di posta elettronica per
errore, siete pregati di segnalarlo immediatamente al mittente e
distruggere quanto ricevuto (compresi file allegati) senza farne copia.
Qualsivoglia utilizzo non autorizzato del contenuto di questo messaggio
costituisce violazione dell'obbligo di non prendere cognizione della
corrispondenza tra gli altri soggetti, salvo più grave 

[qmailadmin] [SPAM] Re: RE: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f4106b34141399820550!

[qmailadmin] [SPAM] Re: Re: [qmailadmin] weird problem -

[creditofinanciero]

!DSPAM:50f4201d34145278918575!

Re: [qmailadmin] How could SPAM ...

[Thibault Richard]

Hello,

It seems you are using qmail-scanner.

In such case, it depends on $sa_quarantine_site variable in 
/var/qmail/bin/qmail-scanner-queue.pl


e.g. : with Spamassassin default score value of 5 and $sa_quarantine_site 
variable set to '0.5', all mails with a score of 5,5 or more will be 
quarantined


You can find more details on 
http://toribio.apollinare.org/qmail-scanner/configure-options.html


Best Regards

Thibs

-Message d'origine- 
From: Giulio Nuti

Sent: Saturday, November 17, 2012 9:56 PM
To: qmailadmin@inter7.com
Subject: [qmailadmin] How could SPAM ...

Hi
I wonder why a spam could arrive to my email after being marked as SPAM...
Could You help me pls?
Thanks
G





From - Wed Nov 14 21:43:10 2012

X-Account-Key: account1
X-UIDL: UID1593-1352316642
X-Mozilla-Status: 0001
X-Mozilla-Status2: 
X-Mozilla-Keys:
Return-Path: ad...@mydomain.com
Delivered-To: giulio.n...@grupponuti.it
Received: (qmail 27111 invoked by uid 89); 14 Nov 2012 07:58:56 +0100
Delivered-To: grupponuti.it-webmas...@grupponuti.it
Received: (qmail 27108 invoked by uid 168); 14 Nov 2012 07:58:56 +0100
X-Qmail-Scanner-Diagnostics: from 101.80.2.177 by v-server (envelope-from 
ad...@mydomain.com, uid 89) with qmail-scanner-2.10st

 (clamdscan: 0.97.6/15574. mhr: 1.0. spamassassin: 3.3.1. perlscan: 2.10st.
 Clear:RC:0(101.80.2.177):SA:1(9.0/5.0):.
 Processed in 6.030113 secs); 14 Nov 2012 06:58:56 -
X-Spam-Status: Yes, hits=9.0 required=5.0
X-Spam-Level: +
X-Qmail-Scanner-Mail-From: ad...@mydomain.com via v-server
X-Qmail-Scanner: 2.10st (Clear:RC:0(101.80.2.177):SA:1(9.0/5.0):. Processed 
in 6.030113 secs Process 27095)

Received: from unknown (HELO mydomain.com) (101.80.2.177)
  by v-server.cad with SMTP; 14 Nov 2012 07:58:48 +0100
Received-SPF: unknown (v-server.cad: parse error in SPF record at 
esendmail.com)

Received: from mydomain.com  by webmail ; 2012-11-14 14:58 +0800 (CST)
From: =?gb2312?B?vqu14834?= ad...@mydomain.com
To: webmas...@grupponuti.it
Subject: 
=?gb2312?B?0fSzzrr+tPPVotC3MTAuODjUqi/Wu6OhzvexsczYsvrXqML0o6HQwr2usaHGpLrLzNK087rs1Oaj

oQ==?=
Date: Wed, 14 Nov 2012 14:58:56 +0800
MIME-Version: 1.0
X-Mailer: outlook
Content-Type: multipart/alternative;
boundary=_=NextPart=_jezc2nbwcx0kn4sks54ut0clhi3qizq12kir
Message-ID: 1352876329103327095@v-server
X-Antivirus: AVG for E-mail 2013.0.2793 [2629/5894]
X-AVG-ID: ID53CED553-535A43C









!DSPAM:50a88a7d33991211281728!

Re: [qmailadmin] How could SPAM ...

[Giulio Nuti]

Il 18/11/2012 11:08, Thibault Richard ha scritto:

Hello,

It seems you are using qmail-scanner.

In such case, it depends on $sa_quarantine_site variable in 
/var/qmail/bin/qmail-scanner-queue.pl


e.g. : with Spamassassin default score value of 5 and 
$sa_quarantine_site variable set to '0.5', all mails with a score of 
5,5 or more will be quarantined


You can find more details on 
http://toribio.apollinare.org/qmail-scanner/configure-options.html


Best Regards

Thibs

-Message d'origine- From: Giulio Nuti
Sent: Saturday, November 17, 2012 9:56 PM
To: qmailadmin@inter7.com
Subject: [qmailadmin] How could SPAM ...

Hi
I wonder why a spam could arrive to my email after being marked as 
SPAM...

Could You help me pls?
Thanks
G





From - Wed Nov 14 21:43:10 2012

X-Account-Key: account1
X-UIDL: UID1593-1352316642
X-Mozilla-Status: 0001
X-Mozilla-Status2: 
X-Mozilla-Keys:
Return-Path: ad...@mydomain.com
Delivered-To: giulio.n...@grupponuti.it
Received: (qmail 27111 invoked by uid 89); 14 Nov 2012 07:58:56 +0100
Delivered-To: grupponuti.it-webmas...@grupponuti.it
Received: (qmail 27108 invoked by uid 168); 14 Nov 2012 07:58:56 +0100
X-Qmail-Scanner-Diagnostics: from 101.80.2.177 by v-server 
(envelope-from ad...@mydomain.com, uid 89) with qmail-scanner-2.10st
 (clamdscan: 0.97.6/15574. mhr: 1.0. spamassassin: 3.3.1. perlscan: 
2.10st.

 Clear:RC:0(101.80.2.177):SA:1(9.0/5.0):.
 Processed in 6.030113 secs); 14 Nov 2012 06:58:56 -
X-Spam-Status: Yes, hits=9.0 required=5.0
X-Spam-Level: +
X-Qmail-Scanner-Mail-From: ad...@mydomain.com via v-server
X-Qmail-Scanner: 2.10st (Clear:RC:0(101.80.2.177):SA:1(9.0/5.0):. 
Processed in 6.030113 secs Process 27095)

Received: from unknown (HELO mydomain.com) (101.80.2.177)
  by v-server.cad with SMTP; 14 Nov 2012 07:58:48 +0100
Received-SPF: unknown (v-server.cad: parse error in SPF record at 
esendmail.com)

Received: from mydomain.com  by webmail ; 2012-11-14 14:58 +0800 (CST)
From: =?gb2312?B?vqu14834?= ad...@mydomain.com
To: webmas...@grupponuti.it
Subject: 
=?gb2312?B?0fSzzrr+tPPVotC3MTAuODjUqi/Wu6OhzvexsczYsvrXqML0o6HQwr2usaHGpLrLzNK087rs1Oaj

oQ==?=
Date: Wed, 14 Nov 2012 14:58:56 +0800
MIME-Version: 1.0
X-Mailer: outlook
Content-Type: multipart/alternative;
boundary=_=NextPart=_jezc2nbwcx0kn4sks54ut0clhi3qizq12kir
Message-ID: 1352876329103327095@v-server
X-Antivirus: AVG for E-mail 2013.0.2793 [2629/5894]
X-AVG-ID: ID53CED553-535A43C
 














-
Nessun virus nel messaggio.
Controllato da AVG - www.avg.com
Versione: 2013.0.2793 / Database dei virus: 2629/5903 -  Data di 
rilascio: 18/11/2012





Ok rut in this case SA:1(9.0/5.0)

that means this email has a score of 9.
Despite that has not being quarantined, ad I received.

G
ps - Please excuse my poor english

!DSPAM:50a8a59133991482615017!

[qmailadmin] How could SPAM ...

[Giulio Nuti]

Hi
I wonder why a spam could arrive to my email after being marked as SPAM...
Could You help me pls?
Thanks
G




From - Wed Nov 14 21:43:10 2012
X-Account-Key: account1
X-UIDL: UID1593-1352316642
X-Mozilla-Status: 0001
X-Mozilla-Status2: 
X-Mozilla-Keys:
Return-Path: ad...@mydomain.com
Delivered-To: giulio.n...@grupponuti.it
Received: (qmail 27111 invoked by uid 89); 14 Nov 2012 07:58:56 +0100
Delivered-To: grupponuti.it-webmas...@grupponuti.it
Received: (qmail 27108 invoked by uid 168); 14 Nov 2012 07:58:56 +0100
X-Qmail-Scanner-Diagnostics: from 101.80.2.177 by v-server (envelope-from 
ad...@mydomain.com, uid 89) with qmail-scanner-2.10st
 (clamdscan: 0.97.6/15574. mhr: 1.0. spamassassin: 3.3.1. perlscan: 2.10st.
 Clear:RC:0(101.80.2.177):SA:1(9.0/5.0):.
 Processed in 6.030113 secs); 14 Nov 2012 06:58:56 -
X-Spam-Status: Yes, hits=9.0 required=5.0
X-Spam-Level: +
X-Qmail-Scanner-Mail-From: ad...@mydomain.com via v-server
X-Qmail-Scanner: 2.10st (Clear:RC:0(101.80.2.177):SA:1(9.0/5.0):. Processed in 
6.030113 secs Process 27095)
Received: from unknown (HELO mydomain.com) (101.80.2.177)
  by v-server.cad with SMTP; 14 Nov 2012 07:58:48 +0100
Received-SPF: unknown (v-server.cad: parse error in SPF record at esendmail.com)
Received: from mydomain.com  by webmail ; 2012-11-14 14:58 +0800 (CST)
From: =?gb2312?B?vqu14834?= ad...@mydomain.com
To: webmas...@grupponuti.it
Subject: 
=?gb2312?B?0fSzzrr+tPPVotC3MTAuODjUqi/Wu6OhzvexsczYsvrXqML0o6HQwr2usaHGpLrLzNK087rs1Oaj
oQ==?=
Date: Wed, 14 Nov 2012 14:58:56 +0800
MIME-Version: 1.0
X-Mailer: outlook
Content-Type: multipart/alternative;
boundary=_=NextPart=_jezc2nbwcx0kn4sks54ut0clhi3qizq12kir
Message-ID: 1352876329103327095@v-server
X-Antivirus: AVG for E-mail 2013.0.2793 [2629/5894]
X-AVG-ID: ID53CED553-535A43C






!DSPAM:50a7d0e533999185365042!

Re: [qmailadmin] How could SPAM ...

[William Olson]

Your question is not clear enough.

Bill

http://www.goodcleanemail.com
http://www.freebsdrocks.net http://www.centosrocks.net



On Sat, Nov 17, 2012 at 3:56 PM, Giulio Nuti giulio.n...@grupponuti.itwrote:

 Hi
 I wonder why a spam could arrive to my email after being marked as SPAM...
 Could You help me pls?
 Thanks
 G


 --**--**

 From - Wed Nov 14 21:43:10 2012
 X-Account-Key: account1
 X-UIDL: UID1593-1352316642
 X-Mozilla-Status: 0001
 X-Mozilla-Status2: 
 X-Mozilla-Keys:
 Return-Path: ad...@mydomain.com
 Delivered-To: giulio.n...@grupponuti.it
 Received: (qmail 27111 invoked by uid 89); 14 Nov 2012 07:58:56 +0100
 Delivered-To: 
 grupponuti.it-webmaster@**grupponuti.itgrupponuti.it-webmas...@grupponuti.it
 Received: (qmail 27108 invoked by uid 168); 14 Nov 2012 07:58:56 +0100
 X-Qmail-Scanner-Diagnostics: from 101.80.2.177 by v-server (envelope-from 
 ad...@mydomain.com, uid 89) with qmail-scanner-2.10st
  (clamdscan: 0.97.6/15574. mhr: 1.0. spamassassin: 3.3.1. perlscan: 2.10st.
  Clear:RC:0(101.80.2.177):SA:1(**9.0/5.0):.
  Processed in 6.030113 secs); 14 Nov 2012 06:58:56 -
 X-Spam-Status: Yes, hits=9.0 required=5.0
 X-Spam-Level: +
 X-Qmail-Scanner-Mail-From: ad...@mydomain.com via v-server
 X-Qmail-Scanner: 2.10st (Clear:RC:0(101.80.2.177):SA:**1(9.0/5.0):.
 Processed in 6.030113 secs Process 27095)
 Received: from unknown (HELO mydomain.com) (101.80.2.177)
   by v-server.cad with SMTP; 14 Nov 2012 07:58:48 +0100
 Received-SPF: unknown (v-server.cad: parse error in SPF record at
 esendmail.com)
 Received: from mydomain.com  by webmail ; 2012-11-14 14:58 +0800 (CST)
 From: =?gb2312?B?vqu14834?= ad...@mydomain.com
 To: webmas...@grupponuti.it
 Subject: =?gb2312?B?0fSzzrr+**tPPVotC3MTAuODjUqi/**
 Wu6OhzvexsczYsvrXqML0o6HQwr2us**aHGpLrLzNK087rs1Oaj
 oQ==?=
 Date: Wed, 14 Nov 2012 14:58:56 +0800
 MIME-Version: 1.0
 X-Mailer: outlook
 Content-Type: multipart/alternative;
 boundary=_=NextPart=_**jezc2nbwcx0kn4sks54ut0clhi3qiz**q12kir
 Message-ID: 1352876329103327095@v-server
 X-Antivirus: AVG for E-mail 2013.0.2793 [2629/5894]
 X-AVG-ID: ID53CED553-535A43C
 --**--**
 





 




!DSPAM:50a7e1a133993532888536!

Re: [qmailadmin] How could SPAM ...

[Giulio Nuti]

Il 17/11/2012 23:08, William Olson ha scritto:

Your question is not clear enough.

Bill Processed in 6.030113 secs); 14 Nov 2012 06:58:56 -

X-Spam-Status: Yes, hits=9.0 required=5.0
X-Spam-Level: +



Hi
I found in my mailbox this email.
As You can see Spam-status hits is 9, a value 5 should be enough to be 
put to quarantine and not delivered to the mailbox.
Despite of this the subject was not modified and I found this and two 
othe emails in my mailbox. It is good 2 errors (IMHO) in two months, but 
is only to understand if I made some mistake or the server has some 
config error.

Tks


!DSPAM:50a7e46833996218019726!

Re: [qmailadmin] How could SPAM ...

[William Olson]

Your english is horribly broken. If you're quarantining message at 5 then
that is a very low threshold.

Bill

http://www.goodcleanemail.com
http://www.freebsdrocks.net http://www.centosrocks.net



On Sat, Nov 17, 2012 at 5:19 PM, Giulio Nuti giulio.n...@grupponuti.itwrote:

  Il 17/11/2012 23:08, William Olson ha scritto:

 Your question is not clear enough.

 Bill Processed in 6.030113 secs); 14 Nov 2012 06:58:56 -

 X-Spam-Status: Yes, hits=9.0 required=5.0
 X-Spam-Level: +


 Hi
 I found in my mailbox this email.
 As You can see Spam-status hits is 9, a value 5 should be enough to be
 put to quarantine and not delivered to the mailbox.
 Despite of this the subject was not modified and I found this and two othe
 emails in my mailbox. It is good 2 errors (IMHO) in two months, but is only
 to understand if I made some mistake or the server has some config error.
 Tks
 



!DSPAM:50a7f43e33995563916630!

RE: [qmailadmin] [SPAM] Auto-empty trash items older then a certain age

[Matt Rauch]

 -Original Message-
 From: Tom Collins [mailto:t...@tomlogic.com] 
 Sent: November-12-12 1:51 PM
 To: qmailadmin@inter7.com
 Subject: Re: [qmailadmin] [SPAM] Auto-empty trash items older 
 then a certain age
 
 Just want to throw out there that different email clients 
 will use different names for their deleted items.
 
 I'm using a cron job to clean up the Trash, Deleted 
 Messages and Deleted Items folders, including any folder 
 that starts with those strings.  Survey your system and see 
 what variations you find.
 
 I decided not to share my Perl script, since it uses the file 
 date (Perl's -M which returns days between script start 
 time and file modification time), not the date it was moved 
 into the Trash folder.  Hmm.  I just did some quick tests and 
 it looks like I should use -C (days since file change time) 
 to trigger of the timestamp of when the file was moved to the trash.
 
 So, here's my script.  Interested in feedback.  I have it in 
 my /etc/cron.daily so it runs every night.  The file globs 
 take care of directory hashing for both domains and users.
 
 I figured this was more efficient than recursing through the 
 domain list, getting a domain's home directory, recursing 
 through the user list and then processing the files.
 
 -Tom
 
 #!/usr/bin/perl
 
 $|++;
 $days = 45;
 
 @globs = (
   '*/*/Maildir/.Trash*/{cur,new}',
   '?/*/*/Maildir/.Trash*/{cur,new}',
   '*/?/*/Maildir/.Trash*/{cur,new}',
   '?/*/?/*/Maildir/.Trash*/{cur,new}',
 
   '*/*/Maildir/.Deleted\ {Messages,Items}*/{cur,new}',
   '?/*/*/Maildir/.Deleted\ {Messages,Items}*/{cur,new}',
   '*/?/*/Maildir/.Deleted\ {Messages,Items}*/{cur,new}',
   '?/*/?/*/Maildir/.Deleted\ {Messages,Items}*/{cur,new}'
 );
 
 $c = 0;
 
 print Deleting mail in .Trash and .Deleted Messages folders, 
 over $days days old.\n;
 
 foreach $path (@globs)
 {
   while ($name = glob ('/home/vpopmail/domains/' . $path))
   {
   opendir (D, $name) or print failed to open $name\n;
   while ($f = readdir(D))
   {
   # skip non-files
   next if (! -f $name/$f);
   $t = -C $name/$f;
   if ($t  $days)
   {
   unlink $name/$f;
   $c++;
   }
   }
   }
 }
 
 print Deleted $c messages over $days days old\n;

Not sure if you saw some of the responses I got, but apparently if you don't
use the expunge command, your quotas will not update. Someone can correct me
if I misinterpreted this. Ofcourse if you're not using quotas, that won't
matter. Otherwise your script seems to make sense based on my limited
programming knowledge. In my case, I only want to empty the Trash that
Squirrelmail uses for now, since its usually users that forget to purge it
once they delete messages that I'm concerned with to start. In the rare case
that they moved a message there by accident, I'll give it a 90 day window
before its expunged.

Matt


!DSPAM:50a6391133991782415209!

RE: [qmailadmin] [SPAM] Auto-empty trash items older then a certain age

[Matt Rauch]

  Hello,
 
   Sorry if this isn't the place to ask, but I've looked 
 all over and haven't managed to find a clear solution. I'm 
 looking for a way to have items that have been in the user's 
 .Trash folder for a certain period of time (lets say 30 days 
 or older) removed automatically. I thought there must be 
 built-in functionality for this, or a script someone has come 
 up with to manage this sort of thing. I've see a squirrelmail 
 plugin that does it based on number of logins or every x 
 number of days, but it empties the whole trash and doesn't 
 check each message's age individually.
 
 Any help would be greatly appreciated.
 
 Thanks,
 
 Matt Rauch

Just to update everyone. I did find a way to accomplish this even though we
are using the vpopmail auth. I found this script online and modified it to
fit my login info:
--
#!/usr/local/bin/bash
# MySQL details

HOST=localhost;
USER=vpopmail;
PWD=vpopmail passwd;

# Output sql to a file that we want to run
echo USE vpopmail; select concat(pw_name,'@',pw_domain) as username from
vpopmail;  /tmp/query.sql;

# Run the query and get the results
results=`mysql -h $HOST -u $USER -p$PWD -N  /tmp/query.sql`;

# Loop through each row
for row in $results
do
/usr/local/bin/doveadm expunge -u $row mailbox Trash savedbefore 52w
done

-

Maybe this can help someone else who is in the same boat.

Matt Rauch


!DSPAM:50a0f90033991110759285!

Re: [qmailadmin] [SPAM] Auto-empty trash items older then a certain age

[Tom Collins]

Just want to throw out there that different email clients will use different 
names for their deleted items.

I'm using a cron job to clean up the Trash, Deleted Messages and Deleted 
Items folders, including any folder that starts with those strings.  Survey 
your system and see what variations you find.

I decided not to share my Perl script, since it uses the file date (Perl's -M 
which returns days between script start time and file modification time), not 
the date it was moved into the Trash folder.  Hmm…  I just did some quick tests 
and it looks like I should use -C (days since file change time) to trigger of 
the timestamp of when the file was moved to the trash.

So, here's my script.  Interested in feedback.  I have it in my /etc/cron.daily 
so it runs every night.  The file globs take care of directory hashing for both 
domains and users.

I figured this was more efficient than recursing through the domain list, 
getting a domain's home directory, recursing through the user list and then 
processing the files.

-Tom

#!/usr/bin/perl

$|++;
$days = 45;

@globs = (
'*/*/Maildir/.Trash*/{cur,new}',
'?/*/*/Maildir/.Trash*/{cur,new}',
'*/?/*/Maildir/.Trash*/{cur,new}',
'?/*/?/*/Maildir/.Trash*/{cur,new}',

'*/*/Maildir/.Deleted\ {Messages,Items}*/{cur,new}',
'?/*/*/Maildir/.Deleted\ {Messages,Items}*/{cur,new}',
'*/?/*/Maildir/.Deleted\ {Messages,Items}*/{cur,new}',
'?/*/?/*/Maildir/.Deleted\ {Messages,Items}*/{cur,new}'
);

$c = 0;

print Deleting mail in .Trash and .Deleted Messages folders, over $days days 
old.\n;

foreach $path (@globs)
{
while ($name = glob ('/home/vpopmail/domains/' . $path))
{
opendir (D, $name) or print failed to open $name\n;
while ($f = readdir(D))
{
# skip non-files
next if (! -f $name/$f);
$t = -C $name/$f;
if ($t  $days)
{
unlink $name/$f;
$c++;
}
}
}
}

print Deleted $c messages over $days days old\n;


On Nov 12, 2012, at 8:21 AM, Matt Rauch wrote:

 Hello,
 
  Sorry if this isn't the place to ask, but I've looked 
 all over and haven't managed to find a clear solution. I'm 
 looking for a way to have items that have been in the user's 
 .Trash folder for a certain period of time (lets say 30 days 
 or older) removed automatically. I thought there must be 
 built-in functionality for this, or a script someone has come 
 up with to manage this sort of thing. I've see a squirrelmail 
 plugin that does it based on number of logins or every x 
 number of days, but it empties the whole trash and doesn't 
 check each message's age individually.
 
 Any help would be greatly appreciated.
 
 Thanks,
 
 Matt Rauch
 
 Just to update everyone. I did find a way to accomplish this even though we
 are using the vpopmail auth. I found this script online and modified it to
 fit my login info:
 --
 #!/usr/local/bin/bash
 # MySQL details
 
 HOST=localhost;
 USER=vpopmail;
 PWD=vpopmail passwd;
 
 # Output sql to a file that we want to run
 echo USE vpopmail; select concat(pw_name,'@',pw_domain) as username from
 vpopmail;  /tmp/query.sql;
 
 # Run the query and get the results
 results=`mysql -h $HOST -u $USER -p$PWD -N  /tmp/query.sql`;
 
 # Loop through each row
 for row in $results
 do
 /usr/local/bin/doveadm expunge -u $row mailbox Trash savedbefore 52w
 done
 
 -
 
 Maybe this can help someone else who is in the same boat.
 
 Matt Rauch
 
 
 
 


!DSPAM:50a11bf333991914119077!

Re: [qmailadmin] qmail admin softlimit

[Amit Rathor]

Dear.

Please make changes in /etc/php5/apache2/php.ini   for the following
parameters,

post_max_size
upload_max_filesize
memory_limit

as it looks qmail increases the attachment size but apache / http restrict
that.

Thanks,



On Fri, Nov 9, 2012 at 12:29 AM, Arch Giulio Nuti giulio.n...@grupponuti.it
 wrote:

 Hi all
 as you know I installed Qmail from Thibs site.
 I would enlarge the softlimit to receive attached file up to 20Mb.

 I tried to set it with
 echo '800'  /var/qmail/control/databytes

 then
  qmailctl restart

 but nothing changes.

 Where is my mistake? ( Do not consider the 20Mb as an error... I know it
 is..)

 Thanks
 Giulio



 




-- 
Amit Rathor


!DSPAM:509cb13833991762875751!