List Info

Thread: amavisd-new detects bad headers in S/MIME signed mails




amavisd-new detects bad headers in S/MIME signed mails
country flaguser name
Germany
2007-02-27 06:02:56
Hi all,

my amavis installation detects a bad header in S/MIME signed
emails if the text 
part has no Content-Type header.

I'm getting this message in my dsn:
> The message WAS NOT relayed to:
>   <spamassassinxams.example>:
>    554 5.6.0 Reject, id=06568-01 - BAD_HEADER: MIME
error: error: couldn't parse head; error near:; Just a
simple test e-mail.
> 
> (...)
> 
> INVALID HEADER: BAD MIME HEADERS OR BAD MIME STRUCTURE
> 
>   MIME error: error: couldn't parse head; error near:;
Just a simple test
>     e-mail.

this message (excerpt) is okay:
> This is an S/MIME signed message
> 
> ------951292EBBC2F84AA1BE7CF21B5B37562
> Content-type: text/plain; charset=us-ascii
> 
> Just a simple test e-mail.
> 
> ------951292EBBC2F84AA1BE7CF21B5B37562
Full message: http://www.felix-schwarz.name/files/misc/2007/smime_
okay.msg

While this one triggers the bad header:
> This is an S/MIME signed message
> 
> ------8BFB1D6001F9748054F2C3412980690B
> Just a simple test e-mail.
> 
> ------8BFB1D6001F9748054F2C3412980690B
Full message: http://www.felix-schwarz.name/files/misc/2007/
smime_bad_header.msg

 From what I know of multipart-Mails, no header is required
in the subparts 
(Content-Type should default to US-ASCII implicitely).

And amavis has not problem with this message:
> Content-type: multipart/mixed; boundary="simple
boundary" 
> 
> This is the preamble.  It is to be ignored, though it 
> is a handy place for mail composers to include an 
> explanatory note to non-MIME compliant readers. 
> --simple boundary 
> 
> This is implicitly typed plain ASCII text. 
> It does NOT end with a linebreak. 
> --simple boundary 
Full message: http://www.felix-schwarz.name/files/misc/2007/mime_ok
ay.msg

Did I messed up my amavis or do you see the same results? I
saw this on 
different systems with 2.3.3 and 2.4.4.

Is the Content-Type actually required in the S/MIME
specification? At least I 
did not find such a requirement in RFC 2311 [1].

fs

[1] http://www.
rfc-editor.org/rfc/rfc2311.txt


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

Re: Portlet Example
country flaguser name
United States
2007-02-27 04:11:10

We&nbsp;can do with inter portlet communcation.
 
Inter portlet communication Examples:
 
Page to page communication example:
 
&nbsp;

Wiring Click-to-Action portlets for inter-portlet communication in WebSphere Portal V5

 
You can find lot of examples (inter portlet communication) from the below URL:

&nbsp;
Thanks and Regards,
ASRao,
Prodapt Solutions (CMMI Level 5),
Chennai, TN, India.
Onsite: IBM, Bahrain (BBM)


----- Original Message ----
From: michael_tech <listsmiketech.net>
To: portletsyahoogroups.com
Sent: Tuesday, February 27, 2007 12:51:11 AM
Subject: [portlets] Portlet Example

Hi,

I wanna write two portlets:

One portlet is for the navigation. It displays a tree view of
available pages.

The other portlet shall display the chosen page. This should be a
common scenario.

My problem is: How does the second portlet know, which page to
display? What is the common way to solve this?

Greetings

Mike




Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.

__._,_.___
.

__,_._,___
Re: amavisd-new detects bad headers in S/MIME signed mails
country flaguser name
Germany
2007-02-27 06:37:08
Sorry guys,

after several hours staring at the problem, I just found the
problem:
 >> ------8BFB1D6001F9748054F2C3412980690B
 >> Just a simple test e-mail.
 >>
 >> ------8BFB1D6001F9748054F2C3412980690B

Due to the empty line at the end, the original text is
interpreted as email 
header and in this case, amavis is right, the header is
bad...

fs


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
AMaViS-user mailing list
AMaViS-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user

AMaViS-FAQ:http://www.amav
is.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/ho
wto/

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )