On Wed, 2005-04-06 at 09:16 +0200, Paul J Stevens wrote: > First of all let me thank you for testing this feature :-)
Hehe, I like to live on the edge. Maybe upgrading to dbmail 2.1 on a production server was not the safest move, but not as bold as the dist-upgrade i did to Ubuntu Hoary at the same time... ;) > >>h=received:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; > >>b=NHvYPHzaPDu3ThkTc+qw5jYjbCcWnHojOqH8/HTNzMW+E7ZOHX1Itrn3LfiL3veTN4t/BlPG1KqoERtakpttrt5SOglQ/1plGcP6cF+Ud5ehhrYGtywP0LBG3toxCj/+LuapwPd8e/7TKsokyl3Vx3X8iEuQANROV/NQQMynfU0=')] > > Damn, this almost looks like a python pickle... What *are* they doing here I > wonder... The messages in question was forwarded from Yahoo -> GMail -> my server. > >>: [ERROR: value too long for type character varying(255) ] > > Yep. I've been hitting that one as well while testing postgres. And how did > you > adjust the field width in postgres?? Being a mysql user mostly myself, I'm so > used to using 'ALTER TABLE <table> CHANGE <fieldname> <field definition>' but > that don't work in postgres... Had to replace the field with a new one. (I really miss that ALTER COLUMN stuff from Oracle/MS-SQL) -- Robert
