Highlighted
Absent Member.
Absent Member.
2411 views

Custom Fields Storage

Hello,

How GroupWise keep custom fields on the message? (Use internet header or
is a proprietary format)?
Labels (1)
0 Likes
8 Replies
Highlighted
Absent Member.
Absent Member.

Re: Custom Fields Storage

My problem is:
I want to send an email in GroupWise using SMTP but I want to set custom
properties. How are steps to do set custom properties?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Custom Fields Storage

Hi,

There are two ways to look at "sending email in GroupWise using SMTP" :

1) You can send an email from a GroupWise account. If the email is addressed to an Internet recipient (i.e. someone with an email address that is NOT in the local GroupWise system), then GroupWise will route the message through the GWIA to the Internet via SMTP.

In this case, you do not do anything with SMTP - you deal only with GroupWise via native GroupWise calls, and GroupWise converts and sends the message via SMTP. You cannot modify the message headers using this format. I don't think that custom fields are preserved as SMTP headers in this case - any data in custom fields is lost. (Novell: If I'm wrong about that, please advise...)

To send a message from a GW mailbox via SOAP, see the sendItemRequest() method.

2) You can send an email via SMTP directly. Your application can use any SMTP server to send to, including the GroupWise Internet Agent (GWIA). You can "forward" SMTP messages to the Internet by sending them to the GWIA. Depending on how GWIA is configured, you may or may not need to provide authentication data for a valid GroupWise account to be able to forward SMTP messages through GWIA.

In this case, you are interacting with GWIA just as with any other SMTP server. The GW SOAP API isn't involved at all. You formulate the SMTP message, which means you have complete control over all headers. You can create custom headers if you would like.

Note, however, that messages sent this way are NOT stored in a GroupWise mailbox as a "sent" item. You are simply using GWIA as a pass-thru server - there is no persistent connection to a GroupWise mailbox at all.


You could use a sort of combination of these two methods to send the SMTP message with custom headers (method #2 above), AND store the message in a GW mailbox as a sent item with custom fields (method #1).

To do this, rather than *sending* the message via the GW SOAP API, you would rather just *create* the message. That is, you would send the message using SMTP (via GWIA or any other SMTP server), and then *create* a corresponding "sent" item in GroupWise. This would add a message to their mailbox as a sent item, but wouldn't actually try to send it. (See createItemRequest() as opposed to sendItemRequest()).

Note, however, that if the GW user were to re-send the sent item you add to their mailbox, any custom field data would be lost when GroupWise converts the message to SMTP. (Again, Novell: advise if this is incorrect.)

HTH.

--sk.


>>> On 7/2/2009 at 2:37 AM, Bogdan Eremia<bogdaneremia@yahoo.com> wrote:


My problem is:
I want to send an email in GroupWise using SMTP but I want to set custom
properties. How are steps to do set custom properties?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Custom Fields Storage

If you are sending messages through gwia / smtp, the only option
you have is to use xfield MIME header fields. I believe settings
xfields are only available in 8.0 and later.

The Custom fields are only preserved in a GroupWise system (not
internet messages (rfc822)).

>>> On Thursday, July 02, 2009 at 8:01 AM, Sean

Kirkby<skirkby@armordatasystems.com> wrote:
> Hi,
>
> There are two ways to look at "sending email in GroupWise using SMTP" :
>
> 1) You can send an email from a GroupWise account. If the email is
> addressed to an Internet recipient (i.e. someone with an email address

that
> is NOT in the local GroupWise system), then GroupWise will route the

message
> through the GWIA to the Internet via SMTP.
>
> In this case, you do not do anything with SMTP ‑ you deal only with

GroupWise
> via native GroupWise calls, and GroupWise converts and sends the message

via
> SMTP. You cannot modify the message headers using this format. I don't
> think that custom fields are preserved as SMTP headers in this case ‑

any data
> in custom fields is lost. (Novell: If I'm wrong about that, please
> advise...)
>
> To send a message from a GW mailbox via SOAP, see the sendItemRequest()
> method.
>
> 2) You can send an email via SMTP directly. Your application can use any


> SMTP server to send to, including the GroupWise Internet Agent (GWIA).

You
> can "forward" SMTP messages to the Internet by sending them to the GWIA.


> Depending on how GWIA is configured, you may or may not need to provide
> authentication data for a valid GroupWise account to be able to forward

SMTP
> messages through GWIA.
>
> In this case, you are interacting with GWIA just as with any other SMTP
> server. The GW SOAP API isn't involved at all. You formulate the SMTP
> message, which means you have complete control over all headers. You can


> create custom headers if you would like.
>
> Note, however, that messages sent this way are NOT stored in a GroupWise
> mailbox as a "sent" item. You are simply using GWIA as a pass‑thru

server ‑
> there is no persistent connection to a GroupWise mailbox at all.
>
>
> You could use a sort of combination of these two methods to send the SMTP


> message with custom headers (method #2 above), AND store the message in a

GW
> mailbox as a sent item with custom fields (method #1).
>
> To do this, rather than *sending* the message via the GW SOAP API, you

would
> rather just *create* the message. That is, you would send the message

using
> SMTP (via GWIA or any other SMTP server), and then *create* a

corresponding
> "sent" item in GroupWise. This would add a message to their mailbox as a


> sent item, but wouldn't actually try to send it. (See createItemRequest()

as
> opposed to sendItemRequest()).
>
> Note, however, that if the GW user were to re‑send the sent item you add

to
> their mailbox, any custom field data would be lost when GroupWise converts


> the message to SMTP. (Again, Novell: advise if this is incorrect.)
>
> HTH.
>
> ‑‑sk.
>
>>>> On 7/2/2009 at 2:37 AM, Bogdan Eremia<bogdaneremia@yahoo.com> wrote:

>
> My problem is:
> I want to send an email in GroupWise using SMTP but I want to set custom
> properties. How are steps to do set custom properties?

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Custom Fields Storage

Thanks for your answers

Is there a way to read MIME.822 attachment or get x-Fields from mail
object using GroupWise web service 7.2 ?




Preston Stephenson wrote:
> If you are sending messages through gwia / smtp, the only option
> you have is to use xfield MIME header fields. I believe settings
> xfields are only available in 8.0 and later.
>
> The Custom fields are only preserved in a GroupWise system (not
> internet messages (rfc822)).
>
>>>> On Thursday, July 02, 2009 at 8:01 AM, Sean

> Kirkby<skirkby@armordatasystems.com> wrote:
>> Hi,
>>
>> There are two ways to look at "sending email in GroupWise using SMTP" :
>>
>> 1) You can send an email from a GroupWise account. If the email is
>> addressed to an Internet recipient (i.e. someone with an email address

> that
>> is NOT in the local GroupWise system), then GroupWise will route the

> message
>> through the GWIA to the Internet via SMTP.
>>
>> In this case, you do not do anything with SMTP ‑ you deal only with

> GroupWise
>> via native GroupWise calls, and GroupWise converts and sends the message

> via
>> SMTP. You cannot modify the message headers using this format. I don't
>> think that custom fields are preserved as SMTP headers in this case ‑

> any data
>> in custom fields is lost. (Novell: If I'm wrong about that, please
>> advise...)
>>
>> To send a message from a GW mailbox via SOAP, see the sendItemRequest()
>> method.
>>
>> 2) You can send an email via SMTP directly. Your application can use any

>
>> SMTP server to send to, including the GroupWise Internet Agent (GWIA).

> You
>> can "forward" SMTP messages to the Internet by sending them to the GWIA.

>
>> Depending on how GWIA is configured, you may or may not need to provide
>> authentication data for a valid GroupWise account to be able to forward

> SMTP
>> messages through GWIA.
>>
>> In this case, you are interacting with GWIA just as with any other SMTP
>> server. The GW SOAP API isn't involved at all. You formulate the SMTP
>> message, which means you have complete control over all headers. You can

>
>> create custom headers if you would like.
>>
>> Note, however, that messages sent this way are NOT stored in a GroupWise
>> mailbox as a "sent" item. You are simply using GWIA as a pass‑thru

> server ‑
>> there is no persistent connection to a GroupWise mailbox at all.
>>
>>
>> You could use a sort of combination of these two methods to send the SMTP

>
>> message with custom headers (method #2 above), AND store the message in a

> GW
>> mailbox as a sent item with custom fields (method #1).
>>
>> To do this, rather than *sending* the message via the GW SOAP API, you

> would
>> rather just *create* the message. That is, you would send the message

> using
>> SMTP (via GWIA or any other SMTP server), and then *create* a

> corresponding
>> "sent" item in GroupWise. This would add a message to their mailbox as a

>
>> sent item, but wouldn't actually try to send it. (See createItemRequest()

> as
>> opposed to sendItemRequest()).
>>
>> Note, however, that if the GW user were to re‑send the sent item you add

> to
>> their mailbox, any custom field data would be lost when GroupWise converts

>
>> the message to SMTP. (Again, Novell: advise if this is incorrect.)
>>
>> HTH.
>>
>> ‑‑sk.
>>
>>>>> On 7/2/2009 at 2:37 AM, Bogdan Eremia<bogdaneremia@yahoo.com> wrote:

>> My problem is:
>> I want to send an email in GroupWise using SMTP but I want to set custom
>> properties. How are steps to do set custom properties?

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Custom Fields Storage

In 7.0.x:
If the mime attachment already exists, you can read it.
You can't force the creation of a mime.

There is no logic to create / expose x-fields.

They are both only available in 8.0.x.

>>> On Tuesday, July 07, 2009 at 3:55 AM, Bogdan

Eremia<bogdaneremia@yahoo.com>
wrote:
> Thanks for your answers
>
> Is there a way to read MIME.822 attachment or get x‑Fields from mail
> object using GroupWise web service 7.2 ?
>
>
>
>
> Preston Stephenson wrote:
>> If you are sending messages through gwia / smtp, the only option
>> you have is to use xfield MIME header fields. I believe settings
>> xfields are only available in 8.0 and later.
>>
>> The Custom fields are only preserved in a GroupWise system (not
>> internet messages (rfc822)).
>>
>>>>> On Thursday, July 02, 2009 at 8:01 AM, Sean

>> Kirkby<skirkby@armordatasystems.com> wrote:
>>> Hi,
>>>
>>> There are two ways to look at "sending email in GroupWise using SMTP" :
>>>
>>> 1) You can send an email from a GroupWise account. If the email is
>>> addressed to an Internet recipient (i.e. someone with an email address

>> that
>>> is NOT in the local GroupWise system), then GroupWise will route the

>> message
>>> through the GWIA to the Internet via SMTP.
>>>
>>> In this case, you do not do anything with SMTP ‑ you deal only with

>> GroupWise
>>> via native GroupWise calls, and GroupWise converts and sends the

message
>> via
>>> SMTP. You cannot modify the message headers using this format. I don't


>>> think that custom fields are preserved as SMTP headers in this case ‑

>> any data
>>> in custom fields is lost. (Novell: If I'm wrong about that, please
>>> advise...)
>>>
>>> To send a message from a GW mailbox via SOAP, see the sendItemRequest()


>>> method.
>>>
>>> 2) You can send an email via SMTP directly. Your application can use

any
>>
>>> SMTP server to send to, including the GroupWise Internet Agent (GWIA).

>> You
>>> can "forward" SMTP messages to the Internet by sending them to the GWIA.


>>
>>> Depending on how GWIA is configured, you may or may not need to provide


>>> authentication data for a valid GroupWise account to be able to forward

>> SMTP
>>> messages through GWIA.
>>>
>>> In this case, you are interacting with GWIA just as with any other SMTP


>>> server. The GW SOAP API isn't involved at all. You formulate the SMTP


>>> message, which means you have complete control over all headers. You

can
>>
>>> create custom headers if you would like.
>>>
>>> Note, however, that messages sent this way are NOT stored in a GroupWise


>>> mailbox as a "sent" item. You are simply using GWIA as a pass‑thru

>> server ‑
>>> there is no persistent connection to a GroupWise mailbox at all.
>>>
>>>
>>> You could use a sort of combination of these two methods to send the

SMTP
>>
>>> message with custom headers (method #2 above), AND store the message in

a
>> GW
>>> mailbox as a sent item with custom fields (method #1).
>>>
>>> To do this, rather than *sending* the message via the GW SOAP API, you

>> would
>>> rather just *create* the message. That is, you would send the message

>> using
>>> SMTP (via GWIA or any other SMTP server), and then *create* a

>> corresponding
>>> "sent" item in GroupWise. This would add a message to their mailbox as

a
>>
>>> sent item, but wouldn't actually try to send it. (See

createItemRequest()
>> as
>>> opposed to sendItemRequest()).
>>>
>>> Note, however, that if the GW user were to re‑send the sent item you

add
>> to
>>> their mailbox, any custom field data would be lost when GroupWise

converts
>>
>>> the message to SMTP. (Again, Novell: advise if this is incorrect.)
>>>
>>> HTH.
>>>
>>> ‑‑sk.
>>>
>>>>>> On 7/2/2009 at 2:37 AM, Bogdan Eremia<bogdaneremia@yahoo.com> wrote:
>>> My problem is:
>>> I want to send an email in GroupWise using SMTP but I want to set custom


>>> properties. How are steps to do set custom properties?

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Custom Fields Storage


Attachment winmail.dat contains information with x-fields and other
information. For GroupWise can be created a similar attachment?


Preston Stephenson wrote:
> In 7.0.x:
> If the mime attachment already exists, you can read it.
> You can't force the creation of a mime.
>
> There is no logic to create / expose x-fields.
>
> They are both only available in 8.0.x.
>
>>>> On Tuesday, July 07, 2009 at 3:55 AM, Bogdan

> Eremia<bogdaneremia@yahoo.com>
> wrote:
>> Thanks for your answers
>>
>> Is there a way to read MIME.822 attachment or get x‑Fields from mail
>> object using GroupWise web service 7.2 ?
>>
>>
>>
>>
>> Preston Stephenson wrote:
>>> If you are sending messages through gwia / smtp, the only option
>>> you have is to use xfield MIME header fields. I believe settings
>>> xfields are only available in 8.0 and later.
>>>
>>> The Custom fields are only preserved in a GroupWise system (not
>>> internet messages (rfc822)).
>>>
>>>>>> On Thursday, July 02, 2009 at 8:01 AM, Sean
>>> Kirkby<skirkby@armordatasystems.com> wrote:
>>>> Hi,
>>>>
>>>> There are two ways to look at "sending email in GroupWise using SMTP" :
>>>>
>>>> 1) You can send an email from a GroupWise account. If the email is
>>>> addressed to an Internet recipient (i.e. someone with an email address
>>> that
>>>> is NOT in the local GroupWise system), then GroupWise will route the
>>> message
>>>> through the GWIA to the Internet via SMTP.
>>>>
>>>> In this case, you do not do anything with SMTP ‑ you deal only with
>>> GroupWise
>>>> via native GroupWise calls, and GroupWise converts and sends the

> message
>>> via
>>>> SMTP. You cannot modify the message headers using this format. I don't

>
>>>> think that custom fields are preserved as SMTP headers in this case ‑
>>> any data
>>>> in custom fields is lost. (Novell: If I'm wrong about that, please
>>>> advise...)
>>>>
>>>> To send a message from a GW mailbox via SOAP, see the sendItemRequest()

>
>>>> method.
>>>>
>>>> 2) You can send an email via SMTP directly. Your application can use

> any
>>>> SMTP server to send to, including the GroupWise Internet Agent (GWIA).
>>> You
>>>> can "forward" SMTP messages to the Internet by sending them to the GWIA.

>
>>>> Depending on how GWIA is configured, you may or may not need to provide

>
>>>> authentication data for a valid GroupWise account to be able to forward
>>> SMTP
>>>> messages through GWIA.
>>>>
>>>> In this case, you are interacting with GWIA just as with any other SMTP

>
>>>> server. The GW SOAP API isn't involved at all. You formulate the SMTP

>
>>>> message, which means you have complete control over all headers. You

> can
>>>> create custom headers if you would like.
>>>>
>>>> Note, however, that messages sent this way are NOT stored in a GroupWise

>
>>>> mailbox as a "sent" item. You are simply using GWIA as a pass‑thru
>>> server ‑
>>>> there is no persistent connection to a GroupWise mailbox at all.
>>>>
>>>>
>>>> You could use a sort of combination of these two methods to send the

> SMTP
>>>> message with custom headers (method #2 above), AND store the message in

> a
>>> GW
>>>> mailbox as a sent item with custom fields (method #1).
>>>>
>>>> To do this, rather than *sending* the message via the GW SOAP API, you
>>> would
>>>> rather just *create* the message. That is, you would send the message
>>> using
>>>> SMTP (via GWIA or any other SMTP server), and then *create* a
>>> corresponding
>>>> "sent" item in GroupWise. This would add a message to their mailbox as

> a
>>>> sent item, but wouldn't actually try to send it. (See

> createItemRequest()
>>> as
>>>> opposed to sendItemRequest()).
>>>>
>>>> Note, however, that if the GW user were to re‑send the sent item you

> add
>>> to
>>>> their mailbox, any custom field data would be lost when GroupWise

> converts
>>>> the message to SMTP. (Again, Novell: advise if this is incorrect.)
>>>>
>>>> HTH.
>>>>
>>>> ‑‑sk.
>>>>
>>>>>>> On 7/2/2009 at 2:37 AM, Bogdan Eremia<bogdaneremia@yahoo.com> wrote:
>>>> My problem is:
>>>> I want to send an email in GroupWise using SMTP but I want to set custom

>
>>>> properties. How are steps to do set custom properties?

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Custom Fields Storage

Only with 8.0.x

>>> On Tuesday, July 07, 2009 at 8:44 AM, Bogdan

Eremia<bogdaneremia@yahoo.com>
wrote:

> Attachment winmail.dat contains information with x‑fields and other
> information. For GroupWise can be created a similar attachment?
>
>
> Preston Stephenson wrote:
>> In 7.0.x:
>> If the mime attachment already exists, you can read it.
>> You can't force the creation of a mime.
>>
>> There is no logic to create / expose x‑fields.
>>
>> They are both only available in 8.0.x.
>>
>>>>> On Tuesday, July 07, 2009 at 3:55 AM, Bogdan

>> Eremia<bogdaneremia@yahoo.com>
>> wrote:
>>> Thanks for your answers
>>>
>>> Is there a way to read MIME.822 attachment or get x‑Fields from mail


>>> object using GroupWise web service 7.2 ?
>>>
>>>
>>>
>>>
>>> Preston Stephenson wrote:
>>>> If you are sending messages through gwia / smtp, the only option
>>>> you have is to use xfield MIME header fields. I believe settings
>>>> xfields are only available in 8.0 and later.
>>>>
>>>> The Custom fields are only preserved in a GroupWise system (not
>>>> internet messages (rfc822)).
>>>>
>>>>>>> On Thursday, July 02, 2009 at 8:01 AM, Sean
>>>> Kirkby<skirkby@armordatasystems.com> wrote:
>>>>> Hi,
>>>>>
>>>>> There are two ways to look at "sending email in GroupWise using SMTP"

:
>>>>>
>>>>> 1) You can send an email from a GroupWise account. If the email is
>>>>> addressed to an Internet recipient (i.e. someone with an email

address
>>>> that
>>>>> is NOT in the local GroupWise system), then GroupWise will route the
>>>> message
>>>>> through the GWIA to the Internet via SMTP.
>>>>>
>>>>> In this case, you do not do anything with SMTP ‑ you deal only with
>>>> GroupWise
>>>>> via native GroupWise calls, and GroupWise converts and sends the

>> message
>>>> via
>>>>> SMTP. You cannot modify the message headers using this format. I

don't
>>
>>>>> think that custom fields are preserved as SMTP headers in this case

‑
>>>> any data
>>>>> in custom fields is lost. (Novell: If I'm wrong about that, please
>>>>> advise...)
>>>>>
>>>>> To send a message from a GW mailbox via SOAP, see the

sendItemRequest()
>>
>>>>> method.
>>>>>
>>>>> 2) You can send an email via SMTP directly. Your application can use

>> any
>>>>> SMTP server to send to, including the GroupWise Internet Agent (GWIA).


>>>> You
>>>>> can "forward" SMTP messages to the Internet by sending them to the

GWIA.
>>
>>>>> Depending on how GWIA is configured, you may or may not need to

provide
>>
>>>>> authentication data for a valid GroupWise account to be able to

forward
>>>> SMTP
>>>>> messages through GWIA.
>>>>>
>>>>> In this case, you are interacting with GWIA just as with any other

SMTP
>>
>>>>> server. The GW SOAP API isn't involved at all. You formulate the

SMTP
>>
>>>>> message, which means you have complete control over all headers. You

>> can
>>>>> create custom headers if you would like.
>>>>>
>>>>> Note, however, that messages sent this way are NOT stored in a

GroupWise
>>
>>>>> mailbox as a "sent" item. You are simply using GWIA as a pass‑thru
>>>> server ‑
>>>>> there is no persistent connection to a GroupWise mailbox at all.
>>>>>
>>>>>
>>>>> You could use a sort of combination of these two methods to send the

>> SMTP
>>>>> message with custom headers (method #2 above), AND store the message

in
>> a
>>>> GW
>>>>> mailbox as a sent item with custom fields (method #1).
>>>>>
>>>>> To do this, rather than *sending* the message via the GW SOAP API,

you
>>>> would
>>>>> rather just *create* the message. That is, you would send the

message
>>>> using
>>>>> SMTP (via GWIA or any other SMTP server), and then *create* a
>>>> corresponding
>>>>> "sent" item in GroupWise. This would add a message to their mailbox

as
>> a
>>>>> sent item, but wouldn't actually try to send it. (See

>> createItemRequest()
>>>> as
>>>>> opposed to sendItemRequest()).
>>>>>
>>>>> Note, however, that if the GW user were to re‑send the sent item

you
>> add
>>>> to
>>>>> their mailbox, any custom field data would be lost when GroupWise

>> converts
>>>>> the message to SMTP. (Again, Novell: advise if this is incorrect.)
>>>>>
>>>>> HTH.
>>>>>
>>>>> ‑‑sk.
>>>>>
>>>>>>>> On 7/2/2009 at 2:37 AM, Bogdan Eremia<bogdaneremia@yahoo.com>

wrote:
>>>>> My problem is:
>>>>> I want to send an email in GroupWise using SMTP but I want to set

custom
>>
>>>>> properties. How are steps to do set custom properties?

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Custom Fields Storage

Thank you for you answer.

Thanks,
Bogdan


Preston Stephenson wrote:
> Only with 8.0.x
>
>>>> On Tuesday, July 07, 2009 at 8:44 AM, Bogdan

> Eremia<bogdaneremia@yahoo.com>
> wrote:
>
>> Attachment winmail.dat contains information with x‑fields and other
>> information. For GroupWise can be created a similar attachment?
>>
>>
>> Preston Stephenson wrote:
>>> In 7.0.x:
>>> If the mime attachment already exists, you can read it.
>>> You can't force the creation of a mime.
>>>
>>> There is no logic to create / expose x‑fields.
>>>
>>> They are both only available in 8.0.x.
>>>
>>>>>> On Tuesday, July 07, 2009 at 3:55 AM, Bogdan
>>> Eremia<bogdaneremia@yahoo.com>
>>> wrote:
>>>> Thanks for your answers
>>>>
>>>> Is there a way to read MIME.822 attachment or get x‑Fields from mail

>
>>>> object using GroupWise web service 7.2 ?
>>>>
>>>>
>>>>
>>>>
>>>> Preston Stephenson wrote:
>>>>> If you are sending messages through gwia / smtp, the only option
>>>>> you have is to use xfield MIME header fields. I believe settings
>>>>> xfields are only available in 8.0 and later.
>>>>>
>>>>> The Custom fields are only preserved in a GroupWise system (not
>>>>> internet messages (rfc822)).
>>>>>
>>>>>>>> On Thursday, July 02, 2009 at 8:01 AM, Sean
>>>>> Kirkby<skirkby@armordatasystems.com> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> There are two ways to look at "sending email in GroupWise using SMTP"

> :
>>>>>> 1) You can send an email from a GroupWise account. If the email is
>>>>>> addressed to an Internet recipient (i.e. someone with an email

> address
>>>>> that
>>>>>> is NOT in the local GroupWise system), then GroupWise will route the
>>>>> message
>>>>>> through the GWIA to the Internet via SMTP.
>>>>>>
>>>>>> In this case, you do not do anything with SMTP ‑ you deal only with
>>>>> GroupWise
>>>>>> via native GroupWise calls, and GroupWise converts and sends the
>>> message
>>>>> via
>>>>>> SMTP. You cannot modify the message headers using this format. I

> don't
>>>>>> think that custom fields are preserved as SMTP headers in this case

> ‑
>>>>> any data
>>>>>> in custom fields is lost. (Novell: If I'm wrong about that, please
>>>>>> advise...)
>>>>>>
>>>>>> To send a message from a GW mailbox via SOAP, see the

> sendItemRequest()
>>>>>> method.
>>>>>>
>>>>>> 2) You can send an email via SMTP directly. Your application can use
>>> any
>>>>>> SMTP server to send to, including the GroupWise Internet Agent (GWIA).

>
>>>>> You
>>>>>> can "forward" SMTP messages to the Internet by sending them to the

> GWIA.
>>>>>> Depending on how GWIA is configured, you may or may not need to

> provide
>>>>>> authentication data for a valid GroupWise account to be able to

> forward
>>>>> SMTP
>>>>>> messages through GWIA.
>>>>>>
>>>>>> In this case, you are interacting with GWIA just as with any other

> SMTP
>>>>>> server. The GW SOAP API isn't involved at all. You formulate the

> SMTP
>>>>>> message, which means you have complete control over all headers. You
>>> can
>>>>>> create custom headers if you would like.
>>>>>>
>>>>>> Note, however, that messages sent this way are NOT stored in a

> GroupWise
>>>>>> mailbox as a "sent" item. You are simply using GWIA as a pass‑thru
>>>>> server ‑
>>>>>> there is no persistent connection to a GroupWise mailbox at all.
>>>>>>
>>>>>>
>>>>>> You could use a sort of combination of these two methods to send the
>>> SMTP
>>>>>> message with custom headers (method #2 above), AND store the message

> in
>>> a
>>>>> GW
>>>>>> mailbox as a sent item with custom fields (method #1).
>>>>>>
>>>>>> To do this, rather than *sending* the message via the GW SOAP API,

> you
>>>>> would
>>>>>> rather just *create* the message. That is, you would send the

> message
>>>>> using
>>>>>> SMTP (via GWIA or any other SMTP server), and then *create* a
>>>>> corresponding
>>>>>> "sent" item in GroupWise. This would add a message to their mailbox

> as
>>> a
>>>>>> sent item, but wouldn't actually try to send it. (See
>>> createItemRequest()
>>>>> as
>>>>>> opposed to sendItemRequest()).
>>>>>>
>>>>>> Note, however, that if the GW user were to re‑send the sent item

> you
>>> add
>>>>> to
>>>>>> their mailbox, any custom field data would be lost when GroupWise
>>> converts
>>>>>> the message to SMTP. (Again, Novell: advise if this is incorrect.)
>>>>>>
>>>>>> HTH.
>>>>>>
>>>>>> ‑‑sk.
>>>>>>
>>>>>>>>> On 7/2/2009 at 2:37 AM, Bogdan Eremia<bogdaneremia@yahoo.com>

> wrote:
>>>>>> My problem is:
>>>>>> I want to send an email in GroupWise using SMTP but I want to set

> custom
>>>>>> properties. How are steps to do set custom properties?

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.