[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.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 -
!DSPAM:50f3cfc534149516629476!
[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -
!DSPAM:50f3cfff34141665842892!
[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -
!DSPAM:50f3d01f34145074614598!
[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -
!DSPAM:50f3d05934145943914805!
[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -
!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 -
!DSPAM:50f3d0d234141295914790!
[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -
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] weird problem -
!DSPAM:50f3d18734141957831037!
[qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] [SPAM] Re: [qmailadmin] weird problem -
!DSPAM:50f3d0b334141956814258!
RE: [qmailadmin] weird problem -
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 -
!DSPAM:50f4106b34141399820550!
[qmailadmin] [SPAM] Re: Re: [qmailadmin] weird problem -
!DSPAM:50f4201d34145278918575!
Re: [qmailadmin] weird problem with corrupt .dir-control file
On Mar 28, 2005, at 9:53 AM, Dave Steinberg wrote:
What would have really helped me would have been any of the following:
- A call to perror() after failed mkdir() / chown calls. Not checking
those return values was what bubbled up into a cryptic, misleading
error message.
- In r_mkdir, testing that tmpbuf either exists and is a directory, or
doesn't exist. If its a file / link / pipe / whatever, then things
should explode.
Sadly, I don't have time to put together a patch at this time.
What do you think about this patch (cross-posted to vpopmail, since
that's where the patch was made).
This patch adds considerably more error checking to r_mkdir.
--- vpopmail.c 1 Mar 2005 01:17:37 - 1.28.2.17
+++ vpopmail.c 8 Apr 2005 05:16:23 -
@@ -31,6 +31,7 @@
#include time.h
#include dirent.h
#include pwd.h
+#include errno.h
#include config.h
#include md5.h
#include vpopmail.h
@@ -1800,19 +1801,40 @@
int r_mkdir(char *path, uid_t uid, gid_t gid )
{
char tmpbuf[MAX_BUFF];
+ int err;
int i;
+ struct stat sb;
+
+ if (*path == '\0') return 0;
- for(i=0;path[i]!=0;++i){
-if ( (i 0) (path[i] == '/') ) {
+ for(i=0; ;++i){
+if ( (i 0) ((path[i] == '/') || (path[i] == '\0')) ) {
tmpbuf[i] = 0;
- if (mkdir(tmpbuf,VPOPMAIL_DIR_MODE) == 0)
+ err = mkdir(tmpbuf,VPOPMAIL_DIR_MODE);
+ if (err == 0)
chown(tmpbuf, uid, gid);
+ else if (errno != EEXIST) {
+/* Note that if tmpbuf is a file, we'll catch the error on the
+ * next directory creation (ENOTDIR) or when we verify that the
+ * directory exists and is a directory at the end of the
function.
+ */
+fprintf (stderr, Unable to create directory %s: , tmpbuf);
+perror();
+return -1;
+ }
+ if (path[i] == '\0') break;
}
tmpbuf[i] = path[i];
}
- mkdir(path,VPOPMAIL_DIR_MODE);
- chown(path, uid, gid);
- return(0);
+ if (stat (path, sb) != 0) {
+fprintf (stderr, Couldn't stat %s: , path);
+perror ();
+return -1;
+ } else if (! S_ISDIR(sb.st_mode)) {
+fprintf (stderr, Error: %s is not a directory.\n, path);
+return -1;
+ }
+ return 0;
}
/
/
--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
You don't need a laptop to troubleshoot high-speed Internet:
sniffter.com
[qmailadmin] weird problem with corrupt .dir-control file
Hi everyone, I just solved a really weird problem with my dir-control file, and I wanted to seek advice and also record this in the archives in case anyone else had the issue. Basics of my setup: - vpopmail 5.4.6 (I'll upgrade once I'm done inflicting pain on myself in other ways) - NFS mounted home directories provide access to the /home/vpopmail directory. Another NFS volume provides /home/vpopmail/domains. Those are mounted on my 2 mail servers. - I have maproot=vpopmail on the domains mount, so even if I do stuff as root - the permissions stay correct as vpopmail:vchkpw. - NFS connectivity is local, over 100mbit switch. When the problem first started, it manifested itself as the error Unable to chdir to vpopmail/domains when I would run 'vadddomain -r8 testdom.com'. Naturally I *could* chdir to /home/vpopmail/domains - I even wrote a tiny c program and tried it as all the various uid's. No dice. Only after running vadddomain under gdb (props to you guys for keeping '-g' in the CFLAGS), was I able to figure out that the call to next_big_dir in vadddomain returned /home/vpopmail/domains/.dir-control, and so DomainSubDir was being set to /home/vpopmail/domains/.dir-control/testdom.com. Obviously, that doesn't fly to calls to mkdir(). I ended up restoring my .dir-control file from backups, and things appear to be back to normal. What would have really helped me would have been any of the following: - A call to perror() after failed mkdir() / chown calls. Not checking those return values was what bubbled up into a cryptic, misleading error message. - In r_mkdir, testing that tmpbuf either exists and is a directory, or doesn't exist. If its a file / link / pipe / whatever, then things should explode. Sadly, I don't have time to put together a patch at this time. Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/
