Hi Aaron;
I actually have just that setup (at least I think :)), and that is the
method that is causing my issues in Outlook Express:
mysql> select * from dbmail_aliases where alias_idnr = "11" or
alias_idnr = "3";
+------------+-----------------------+----------------------+-------------+
| alias_idnr | alias | deliver_to | client_idnr |
+------------+-----------------------+----------------------+-------------+
| 3 | [EMAIL PROTECTED] | !/usr/bin/procmail | 0 |
| 11 | [EMAIL PROTECTED] | 3 | 0 |
+------------+-----------------------+----------------------+-------------+
the first one will end up malformed in OE, whereas the second one
appears just fine
procmailrc related rule's:
:0 H:spamlock
* ^X-Spam-Status: Yes
| /software/dbmail2RC8/sbin/dbmail-smtp -m "Junk E-mail" -u dstilts
:0wf H:lock
| /software/dbmail2RC8/sbin/dbmail-smtp -m "INBOX" -u dstilts
master.cf line which takes care of the SPAM marking first:
dbmail-smtp unix - n n - - pipe
flags= user=dbmail:dbmail argv=/usr/bin/spamc -f -e
/software/dbmail2RC8/sbin/dbmail-smtp -d ${recipient} -r ${sender}
Do I have something wrong here that you can spot that would be causing
the problems I'm having?
Thanks much!
Dan
Aaron Stone wrote:
From the file dbmail/EXTRAS:
Dbmail can forward to external programs.
Create an alias. Set the deliver_to for that alias to:
"|/usr/bin/procmail" will pipe the message for the alias to procmail
"!/usr/bin/procmail" will do the same but add a mbox style header
You can also use this scan mail for certain users:
"|/usr/bin/spamassasin | dbmail-smtp -d <username>"
I'll put this into the dbmail-users documentation.
Aaron
Dan Stilts <[EMAIL PROTECTED]> said:
one other bit of info i just noticed
When comparing the headers from the two emails (one sent to alias with
deliver_to set to procmail, which is then inserted again using
dbmail-smtp -m "INBOX" -u <user>, and one sent to deliver_to of the uid
of the account), I notice an extra line being added to the end:
From [EMAIL PROTECTED] Tue Oct 5 10: 26:00 2004
Seems Outlook Express is trying to use this as the "From:" that it
prints, but not being valid, chokes on it?
Thanks,
Dan
Dan Stilts wrote:
I don't suppose anyone has a workaround/fix for this by chance?
Just some additional info:
I notice that the problem is only occuring when i have the deliver_to
set to
!/usr/bin/procmail /etc/procmail_users/<user>.procmailrc
And this is still only displaying incorrectly in Outlook Express.
Attached are a couple files. Both are log snips of dbmail_smtp with
trace = 5. one log shows the message coming in where it is delivered
to procmail, then reinserted, and the other, is to an alias that has a
direct deliver_to, to the user.
Let me know if there is anything else you would like me to include.
Thanks,
Dan
Aaron Stone wrote:
Paul J Stevens <[EMAIL PROTECTED]> said:
Ok so probably the mimeparser is adding spurious \r characters
in the string send to the client.
What's your take Aaron?
Yep, it's in the MIME parser. Somewhere, in the MIME parser. Early in
the
2.0rc series, I had a fairly elegant and unified mechanism for receiving
messages, but the \r, \r\n, \r\r\n, etc. problems with the MIME parser
forced us to change to much heftier code that handled messages
differently
if they came in over the network or from stdin.
Once we move to a more robust MIME parser in 2.1, we'll be able to throw
differently formatted messages at it and get better results. As for 2.0,
we'll just have to figure out a robust hack...
Aaron
--
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
