sending mail results in Error: *Trying to put int in string

Bug #181264 reported by Cody A.W. Somerville
2
Affects Status Importance Assigned to Milestone
Sapidlib
Fix Committed
Undecided
Unassigned
Lpuni-final
Fix Committed
Undecided
Unassigned

Bug Description

With FluffOS and lpuni-final, when I send a mail (regardless if I specify a cc or not) I get the following error:

Error: *Trying to put int in string

Current Object: /obj/mudlib/mail_clients/mail_client#64 ("/obj/mudlib/mail_clients/mail_client#64")
Current Program: "/obj/mudlib/mail_clients/mail_client.c"
File: "/obj/mudlib/mail_clients/mail_client.c" Line: 1147

Traceback:
"Line: 1147 File: "/obj/mudlib/mail_clients/mail_client.c"
Object: /obj/mudlib/mail_clients/mail_client#64 ("/obj/mudlib/mail_clients/mail_client#64")
 Program: "/obj/mudlib/mail_clients/mail_client.c""

The recipients do still receive the message.

Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

Marking invalid for trunk as we haven't migrated to FluffOS yet and the error doesn't seem to occur with MudOS.

description: updated
Changed in sapidlib:
status: New → Invalid
Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

Parthenon: Can you take a look at this?

Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

Fixed bug in lpuni-final series.

revno: 16
committer: Cody A.W. Somerville <cody-somerville@cody-laptop>
branch nick: lpuni-final
timestamp: Wed 2008-02-20 16:24:46 -0400
message:
  Fix bug #181264 and tidy mail client code.

Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

I also synced the mail client with the mainline.

Changed in sapidlib:
status: Invalid → Fix Committed
Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

revno: 53
committer: Cody A.W. Somerville <cody-somerville@cody-laptop>
branch nick: sapidlib
timestamp: Wed 2008-02-20 16:27:02 -0400
message:
  Tidy up mail client and apply fix for bug #181264

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.