Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DBMail: users

2.3.6 delivery failed with malformed subject

 

 

DBMail users RSS feed   Index | Next | Previous | View Threaded


pwadas at jewish

Jul 30, 2009, 3:12 AM

Post #1 of 5 (1040 views)
Permalink
2.3.6 delivery failed with malformed subject

Hello,
I got in sendmail queue a message with probably malformed subject field.
The message is multipart, and the subject (probably automatically generated
by Microsoft Outlook Express 6.00.2900.5512 , contains the names
of 10-15 binary jpeg attachments (attachments files base64 converted).

Total message size is about 1,5 MB. Subject header is iso-8859-2 encoded.

Subject:
=?iso-8859-2?Q?Wysy=B3anie_wiadomo=B6ci_e-mail:_DSC03363.JPG=2C_DSC0336?=

=?iso-8859-2?Q?4.JPG=2C_DSC03370.JPG=2C_DSC03376.JPG=2C_DSC03380.JPG=2C_D?=

=?iso-8859-2?Q?SC03392.JPG=2C_DSC03393.JPG=2C_DSC03400.JPG=2C_DSC03409.?=

=?iso-8859-2?Q?JPG=2C_DSC03413.JPG=2C_DSC03424.JPG=2C_DSC03438.JPG=2C_DSC?=

=?iso-8859-2?Q?03464.JPG=2C_DSC03259.JPG=2C_DSC03295.JPG=2C_DSC03335.JP?=
=?iso-8859-2?Q?G=2C_DS?=

This is taken from queue spool file. When I modify subject in queue file by
hand
to contain

Subject: blabla

the message gets delivered, otherwise dbmail-deliver returns error. I tried
to deliver
the same message with dbmail-deliver -u by hand, with no error., anyway it
must be
something with subject. MTA is current sendmail.org's sendmail.

My guess is some max length of some database field containing subject, or
similar. The
db is current pgsql. There's nothing particular in dbmail error log
(increased loglevel to max).

Regards,
P.
--
View this message in context: http://www.nabble.com/2.3.6-delivery-failed-with-malformed-subject-tp24735655p24735655.html
Sent from the dbmail users mailing list archive at Nabble.com.

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


vulture at netvulture

Jul 30, 2009, 8:52 AM

Post #2 of 5 (974 views)
Permalink
Re: 2.3.6 delivery failed with malformed subject [In reply to]

You are using dbmail-deliver with sendmail?

Try setting your syslog to level 511 and running again. I don't like the
syslog logging as it cuts off messages, but it should give us more than
stdout/stderr that is lost with sendmail piping to dbmail-deliver.

-Jon

--
Scanned for viruses and dangerous content by MailScanner

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


pwadas at jewish

Jul 30, 2009, 10:07 AM

Post #3 of 5 (974 views)
Permalink
Re: 2.3.6 delivery failed with malformed subject [In reply to]

Jonathan Feally wrote:
>
> You are using dbmail-deliver with sendmail?
>
> Try setting your syslog to level 511 and running again. I don't like the
> syslog logging as it cuts off messages, but it should give us more than
> stdout/stderr that is lost with sendmail piping to dbmail-deliver.
>
> -Jon
>

as noted, loglevel increased to maximum, but don't see anything particular
in it,
only error I had from sendmail was
----
Jul 30 07:37:44 b02 sm-mta[17348]: n6TC8UcC017946: to=recipient [at] domain,
delay=17:29:09, xdelay=00:00:03, mailer=local, pri=10797264, dsn=4.0.0,
stat=Deferred: local mailer (/usr/sbin/sensible-mda) exited with EX_TEMPFAIL
----

Same message from stdin to dbmail-deliver and the same user was delivered,
anyway queue processing retry did not success until I manually threw out
iso-encoded garbage in subject from queue qf.... file.

PS. To test dbmail-deliver with sendmail I modified slightly debian helper
sensible-mda, adding
a few paragraphs just like these existing, and a small check to determine
which MDA shall
be used for particular user, something like

use_dbmail_delivery(char *final_user) {
// pg connection declarations here
PGresult *res;
char *query[MAXLEN];
sprintf(query, "SELECT count(*) as howmany FROM dbmail_users WHERE
username LIKE %s LIMIT 1;", final_user, final_user );
res = PQexec(pgc, query );
if ( PQresultStatus(res) != PGRES_TUPLES_OK )
{
PQfinish(pgc);
pgc = (PGconn *) NULL;
return 0;
}
int ret = atoi( PQgetvalue(res, 0, 0) );
return
}

[...]

if ( use_dbmail_delivery(recipient))
{ ... exec DBMAIL_DELIVER, "-u", "%s", recipient ) }
else
... [ follow the rest of original sensible-mda program ]


http://packages.debian.org/sid/sensible-mda

Regards,
P.
--
View this message in context: http://www.nabble.com/2.3.6-delivery-failed-with-malformed-subject-tp24735655p24742694.html
Sent from the dbmail users mailing list archive at Nabble.com.

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


pwadas at jewish

Jul 30, 2009, 12:04 PM

Post #4 of 5 (973 views)
Permalink
Re: 2.3.6 delivery failed with malformed subject [In reply to]

aa, here we go. I saved original queue files and modified to contain
my addressess (regarding log file, I forgot sendmail call of dbmail-deliver
use minimal log, and this is my setting, because 511 log grows huge very
quickly,
too quickly to wait for malformed message). Anyway with saved queue files,
into which I put my own account addressess, I got the following delivery
reports which clears something. So, it is sql issue anyway.
Regards,
P.

----- Transcript of session follows -----
sensible-mda[30143]: Parms: sensible-mda sender [at] senderdomain
recipient [at] domain
sensible-mda[30143]: trying: get_status(recipient [at] domain)
sensible-mda[30143]: get_status: /etc/mail/smrsh/dbmail-deliver -u
recipient [at] domain pg notice
sensible-mda[30143]: get_status: /etc/mail/smrsh/dbmail-deliver -u
recipient [at] domain pg ret 1
sensible-mda[30143]: MDA: /etc/mail/smrsh/dbmail-deliver -u
recipient [at] domain
Jul 30 20:53:29 b02.lepiej.pl dbmail-deliver[30143]: [0x8051bc8]
Warning:[misc] dm_get_hash_for_string(+2273): hash algorithm not supported.
Using SHA1.
Jul 30 20:53:30 b02.lepiej.pl dbmail-deliver[30143]: [0x8051bc8]
Error:[message] _header_value_get_id(+1577): SQLException: ERROR: value too
long for type
character varying(255)

dbmail-deliver: dbmail-message.c:1582: _header_value_get_id: Assertion `*id'
failed.
451 4.3.0 mailer local died with signal 6
Arguments: sensible-mda sender [at] senderdomain recipient [at] domain
recipient [at] domain Deferred: local mailer (/usr/sbin/sensible-mda)
exited with EX_TEMPFAIL
Message could not be delivered for 1 day
Message will be deleted from queue

--
View this message in context: http://www.nabble.com/2.3.6-delivery-failed-with-malformed-subject-tp24735655p24745375.html
Sent from the dbmail users mailing list archive at Nabble.com.

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail


vulture at netvulture

Jul 30, 2009, 12:35 PM

Post #5 of 5 (981 views)
Permalink
Re: 2.3.6 delivery failed with malformed subject [In reply to]

Piotr Wadas wrote:
> Error:[message] _header_value_get_id(+1577): SQLException: ERROR: value too
> long for type
> character varying(255)
>
Ah hah! I'll take a look at this and figure out something for it.

-Jon

--
Scanned for viruses and dangerous content by MailScanner

_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

DBMail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.