wiki:es:FAQ/Using YAM

Version 2 (modified by Emilio Jimenez, 5 years ago) (diff)

En otros idiomas:

Utilizando YAM

  1. Interfaz de Usuario
    1. ¿Por qué la opción de "Texto Coloreado" en la ventana de lectura aparece mal la primera vez que abro esta hoja?
    2. Los atajos de Menú no funcionan mientras están activos los menús contextuales, ¿por qué?
    3. El medidor en la ventana de transferencia de correo aparece mal, ¿por qué?
    4. ¿Por qué la selección con teclado de múltiples mensajes no funciona?
    5. Utilizo AmigaOS 3.9 y tengo activado el tema AISS. Desafortunadamente algunos de los iconos muestran un fondo negro.¿Por qué?
    6. La lista de anexos gráficamente se muestra cortada y no refleja todos los anexos disponibles. ¿Hay algo para prevenir esto?
    7. ¿Por qué la ventana de preselección/transferencia de correo algunas veces está activa por defecto y otras veces no?
    8. El menú de la ventana de escritura contiene definiciones de atajos extrañas "ramiga X", "ramiga C". ¿Por qué no se utiliza en su lugar la típica imagen de Amiga?
    9. He cambiado la definición de atajo de TextEditor.mcc para utilizar un atajo, no el de por defecto, para operaciones de Cortar y Pegar. Sin embargo, YAM continúa mostrando p.ej. "Amiga+C" en la ventana.
    10. El icono de anexo a veces desaparece de repente en la lista de mensajes principal, ¿Por qué?
    11. Cuando utilizo las teclas de flecha arriba/abajo, la barra de desplazamiento de la lista de correo principal se mueve en vez de remarcar el mensaje a cambiar. ¿Por qué?
    12. El redibujado de la lista de carpetas es tan lento que puedo ver el redibujado de cada carpeta. ¿Por qué?
    13. ¿Puedo guardar permanentemente la posición y tamaño de una ventana?
    14. ¿Por qué algunas columnas de la lista de correo siempre se redimensionan automáticamente?
    15. Los botones de la barra de herramientas y otros gráficos se muestran con colores erróneos. ¿Por qué?
    16. Los botones de la barra de herramientas no caben en la ventana, los botones situados a la derecha no se pueden acceder. ¿Cómo puedo solucionar esto?
    17. El diseño de la ventana de preferencias no se adapta apropiadamente cuando se reduce su tamaño, ¿hay alguna solución disponible para esto?
    18. La impresión no parece funcionar. ¿Qué está fallando?
    19. La impresión parece funcionar, pero siempre obtengo un aviso de advertencia justo antes de que el documento se imprima?!?
    20. ¿Por qué YAM toma los corchetes como en "http://www.example.com" como parte de URLs?
    21. ¿Por qué YAM falla o se cuelga cuando entro en la sección 'Mixed/Misc' en la ventana de configuración o mientras inicia?
    22. Why there are Enforcer hits when flushing memory after uniconifying YAM and its MUI prefs?
    23. No puedo cambiar la dirección de remitente (De) en la ventana de escritura desde la versión YAM 2.8. ¿Por qué?
  2. Language Support
    1. There seems to be no translation available for my language?
  3. Reading Mails
    1. Why are some mails displayed without any text content which got displayed properly some weeks ago?
    2. When displaying an email with embedded soft-styles such as bold/italic, etc. the mail will be displayed with the style markers '*' as well, why?
    3. Doubleclicking an URL doesn't seem to popup my favourite webbrowser?
    4. YAM shows the default icon for attachments rather than the one I configured in DefIcons. Why?
    5. Why do certain mails I receive show up with lines quoted like ">From " even if the author of that mail hasn't written that From line quoted?
  4. Replying/Forwarding Mails
    1. I can't put my initials into or change the quoting string used on reply! Why?
    2. When replying to a mail, a wrong To: address is put in the write window, why?
    3. What's the purpose of the 'Bounce' option in YAM and can I use it to e.g. bounce SPAM mail back?
    4. Why are are mails duplicated in the Outgoing folder when editing them again later?
  5. Composing Mails
    1. Is it possible to send an email to a group of recipients in one go?
    2. When writing an email I get an error message like "+++ Host environment not found"?
    3. Why isn't YAM able to mark whole sentences as bold/italic/underline and just highlights single words? Wasn't that possible already?
    4. Why is the TAB key not advancing to the internal text editor gadget when I finished writing the subject line of a mail?
    5. Why doesn't YAM let me choose an address from the popup list when writing a mail?
    6. My system hangs when deleting a block of text in the editor while using a key qualifier, why?
  6. Filtering Mails
    1. If I search for "[SPAM]" in a filter, mails not containing this string will get hit by the filter as well, why?
    2. How to train YAM's SPAM filter properly?
  7. Network Setup
    1. How to properly set up SMTP-AUTH authentication?
    2. When sending mail via smtp.gmail.com, YAM returns an error upon terminating the connection. However, the mail will be correctly send to its recipient.
    3. When I use Genesis, Yam always uses the Genesis user to choose the account. How can I change that?
    4. I am not able to abort a POP3 transfer and the whole application seems to hang, why?
    5. I have automatic mail download/send on startup enabled, but YAM 2.6 doesn't perform the mail exchange. Why?

Interfaz de Usuario

¿Por qué la opción de "Texto Coloreado" en la ventana de lectura aparece mal la primera vez que abro esta hoja?

Esto es un fallo en MUI 3.8 y desfortunadamente no se puede arreglar de ninguna manera. Sin embargo, si está corregido en versiones de MUI ≥ 3.9. Así que por favor actualice su instalación de MUI, si es posible.

Los atajos de Menú no funcionan mientras están activos los menús contextuales, ¿por qué?

Desafortunadamente, los menús contextuales de carpetas y de listas de mensajes que puede interferir e impedirle el uso normal de los atajos de las opciones del menú a menos que mueva el puntero fuera de la lista. Desafortunadamente este es un fallo de MUI ⇐3.8, que sólo puede corregir desactivando el menú contextual o actualizando MUI al menos a la versión 3.9.

El medidor en la ventana de transferencia de correo aparece mal, ¿por qué?

Debido a un fallo en MUI 3.8, el medidor en la ventana de transferencia de correo parece "desbordar" su contenedor cuando representa valores muy altos, típicamente alrededor de 8 MB o más. Este fallo es inócuo, pero se necesita una actualización de MUI (3.9 o posterior) para corregir este problema. Tal actualización no está disponible para Amigas m68k en el momento de escritura de este artículo.

¿Por qué la selección con teclado de múltiples mensajes no funciona?

De acuerdo con la documentación y la configuración GUI de la clase NList.mcc (la cual se utiliza en YAM para mostrar la lista de mensajes) debería poder seleccionar varias entradas en la lista utilizando las teclas CTRL+Arriba/Abajo. Sin embargo, cuando utilizo estas teclas la lista se desplaza hacia el principio o el final de la misma no permitiendo la selección de múltiples mensajes. La razón para este problema es, que las combinaciones de teclado por defecto de NList.mcc y las por defecto de MUI se interfieren. Así que cuando utilice CTRL+Arriba/Abajo las por defecto de MUI tendrán preferencia sobre las de NList y por tanto no funcionarán correctamente las de NList. La solución es o actualizar a la versión 0.108 o posterior de NList donde la combinación de teclas por defecto ha sido cambiada para utilizar ALT+Arriba/Abajo en vez de CTRL. Sólo asegúrese de volver a definir sus preferencias de combinación de teclado en la configuración MUI pestaña NList después de haber instalado la claes NList 0.108+. Otra solución (para versiones anteriores de NList) sería manualmente cambiar las preferencias de la combinación de teclado en la configuración de MUI para utilizar la tecla ALT en vez de CTRL (vea todas las entradas de "Select XXX" en el ejemplo siguiente).

Utilizo AmigaOS 3.9 y tengo activado el tema AISS. Desafortunadamente algunos de los iconos muestran un fondo negro.¿Por qué?

Los iconos AISS son iconos PNG que utilizan canales alfa. Con AmigaOS 3.9 la transpariencia no se puede mostrar correctamente porque hay algunas incompatibilidades con la datatypes.library.

La lista de anexos gráficamente se muestra cortada y no refleja todos los anexos disponibles. ¿Hay algo para prevenir esto?

Para los mensajes con muchos anexos, la visualizción gráfica de los anexos en la ventana de lectura puede verse cortada. Este es el caso de que la zona de la lista de anexos no puede agrandarse para el tamaño requerido (p.ej.porque la ventana es pequeña). Desafortunadamente no es posible mostrar/utilizar una barra deslizadora para estos casos debido a razones técnicas.

Pero como la lista de anexos en un grupo virtual debería poder utilizar el desplazamiento virtual en las funciones de MUI para este caso. Por favor consulte la configuración de MUI en las preferencias de acciones de desplazamiento botón teclado/ratón. Pero por defecto, MUI deberá permitirle mediante pulsación del bóton intermedio del ratón mientras lo mueve. Esto debería permitirle desplazar la lista de anexos y visualizar el resto de anexos que normalmente quedan ocultos. Otra manera para mostrar todos los anexos del mensaje es, por supuesto utilizar el correspondiente botón de la barra de herramientas (Mostrar, Imprimir, etc.) que le mostrará toda la lista de anexos.

¿Por qué la ventana de preselección/transferencia de correo algunas veces está activa por defecto y otras veces no?

YAM se puede configurar para mostrar la ventana de preselección/transferencia para descargar nuevo correo sólo si ciertas condiciones se dan, por ejemplo siempre, nunca o sólo si hay mensajes muy grandes para descargar. Desde que los correos pueden ser gestionados en segundo plano mientras continúa su trabajo con YAM sería un gran inconveniente si la ventana de preselección robase el foco de atención de la actual ventana activa (p.ej. una ventana de escritura para un nuevo mensaje). Imagine sólo que presiona la tecla "C" en el mismo momento que se abre la ventana de preselección. Esto inmediatamente cancelaría la transferencia, incluso si sólo iba a escribir la palabra "Commodore"…

Para evitar tal salida indeseada YAM abrirá la ventana de preselección/transferencia en un estado inactivo para transferencias de correo iniciados automáticamente (p.ej. transferencia o recogida de correo programada iniciada con un script ARexx). Para todas las transferencias iniciadas por el usuario (importar, exportar, obtener/enviar correo) se activará la ventana, porque esta es una acción que fue explícitamente solicitada por el usuario y no solicitada automáticamente por el propio YAM.

El menú de la ventana de escritura contiene definiciones de atajos extrañas "ramiga X", "ramiga C". ¿Por qué no se utiliza en su lugar la típica imagen de Amiga?

La razón de esta rareza se ha corregido en la versión 2.5 de YAM. Sin embargo, por favor encuentre las explicaciones en versiones anteriores de porqué no se podía utilizar la imágen típica de 'Amiga' en los items de menú para indicar el atajo: El tema es, que la configuración de estos atajos era del usuario. De hecho, TextEditor.mcc provee un gestor de configuración donde un usuario puede especificar él mismo los atajos de teclado que quiere utilizar. La visualización de "ramiga X" era sólo un marcador - incluso no era una definición real de atajo. Sólo debería señalar que combinación de teclas por defecto se utilizan normalmente para estas operaciones. Así que fue más cosmética que otra cosa. Pero como se ha dicho, en YAM 2.5 se ha cambiado y ahora debería aparecer la imágen típica de Amiga como se esperaba.

He cambiado la definición de atajo de TextEditor.mcc para utilizar un atajo, no el de por defecto, para operaciones de Cortar y Pegar. Sin embargo, YAM continúa mostrando p.ej. "Amiga+C" en la ventana.

Desde la versión YAM 2.5, el comportamiento de los atajos por defecto de las acciones de Editar como Copiar y Pegar han cambiado. Esto significa, como se ha explicado en anteiores puntos del FAQ, YAM ahora utiliza siempre los atajos estandar de acuerdo al StlyeGuides común. P.ej. una operación de Copiar siempre aparecerá como "Amiga+C" al igual que la operación de Pegar aparecerá siempre como "Amiga+V" sin importar como lo haya configurado en TextEditor.mcc.

Para versiones anteriores a 2.5 de YAM, la situación es ligeramente diferente. Ahí, el atajo configurado en TextEditor.mcc siempre se utilizará y se mostrará con el marcador p.ej. "ramiga X" en un menú de ventana sólo para mostrar el valor por defecto si tiene definido el valor por defecto en TextEditor.mcc.

El icono de anexo a veces desaparece de repente en la lista de mensajes principal, ¿Por qué?

En la lista principal de mensajes donde todos los mensajes de la carpeta están listados, el icono de estado de anexos (normalmente es un clip) a veces se visualiza, pero de repente desaparece en el momento que hace click en ese mensaje para ver su contenido. Aunque esto puede parecer un poco extraño y puede dar la impresión de que los anexos se han perdido cuando se visualiza el mensaje, este comportamiento es normal y correcto.

La razón por la que esto ocurre es que desafortunadamente algunos clientes de correo antiguos intentan enviar mensajes donde el tipo content-type se define como "multipart/mixed" o "multipart/related" incluso si el mensaje sólo contiene texto sin anexos. Esto claramente es incorrecto de acuerdo a las RFC s y puede ser considerado un fallo de aquellos programas de correo.Sin embargo, la razón por la que YAM muestra primero el icono de estado de anexos es que sólo analiza la cabecera principal del mensaje debido a razones de optimización y en el momento que hace click en el mensaje correspondiente (más tiempo consumido) el análisis se realiza y es donde automáticamente reconoce que el mensaje realmente no contiene ningún anexo binario o documento, sino sólo el texto normal del mensaje.

Así que el comportamiento de YAM es totalmente correcto y está en línea de lo que sugieren las RFC s.

Cuando utilizo las teclas de flecha arriba/abajo, la barra de desplazamiento de la lista de correo principal se mueve en vez de remarcar el mensaje a cambiar. ¿Por qué?

La causa para este comportamiento puede ser, que ha seleccionado la lista de correo principal a través de la opción de tecla de activación "Tab" en las propiedades de MUI. MUI tiene una propiedad llamada CycleChain que le permite rotar entre todas las opciones existentes en la ventana a través de la tecla Tab. En cada caso, la lista de correo principal de YAM se puede activar a través de numerosos usos de la tecla Tab.

Y como la lista de correo principal basada en NList cambia su comportamiento cuando es directamente activada a través de CycleChain, esta es la razón por la que la barra deslizadora se mueve cuando utiliza las flechas de arriba/abajo. Si una clase NList está activada se desplazará hacia abajo en vez de cambiar la selección.

Sin embargo, hay una forma sencilla de resolver tal situación. Sólo tiene que presionar "Ctrl+Tab" para indicar a MUI que desactive todaas las opciones actualmente en uso y entonces podrá volver a cambiar la selección en la lista de correo a través de las flechas arriba/abajo.

El redibujado de la lista de carpetas es tan lento que puedo ver el redibujado de cada carpeta. ¿Por qué?

La razón para el problema es que está dibujando en YAM, que YAM utiliza la clase NListtree.mcc para componer la lista de carpetas. Esta clase es una subclase de las clases NList y depende en gran medida de la clase interna NList.mcc.

Como de hecho es un problema, la clase NListtree se conoce que no está optimizado en el redibujado de elementos. Como si masivamente se redibujaran los elementos y al haber otra ventana delante de la lista se redibuja continuamente. Así que, este es un tema conocido de la clase NListtree y esperamos que sea corregido en versiones futuras de NListtree.mcc.

Sin embargo, perfectamente puede intentar evitar esta lentitud de redibujado asegurándose que no hay otra ventana abierta delante de la lista de carpetas en YAM durante el tiempo requerido de redibujado.

¿Puedo guardar permanentemente la posición y tamaño de una ventana?

Sí, a través de la opción normal de MUI 'snapshot'….

…inicie el interfaz de las preferencias de MUI seleccionando 'Preferencias/MUI'. Seleccione la sección 'ventanas' y asegúrese de que el tercero de los iconos de sistema está activado. Después de guardar las preferencias cada ventana tendrá un icono de sistema adicional en la esquina superior derecha. Un click en este icono y recordará la posición y tamaño actual de la ventana para futuras sesiones. Esta es una función general de MUI y si la utiliza en las ventanas de YAM podrá utilizarlo para "recordar" el tamaño de ventana permanentemente de YAM.

¿Por qué algunas columnas de la lista de correo siempre se redimensionan automáticamente?

De hecho, este comportamiento es muy común en las listas basadas en NList. El 'problema' es, que NList está por defecto automáticamente ajustando el tamaño de cada columna dependiendo del ancho de su contenido. Así que si tiene correo con p.ej. líneas de asunto muy extensas o si la columna de estado contiene una buena cantidad de iconos de estado, puede ocurrir que NList automáticamente decida redimensionar las columnas.

Mientras que esto puede ser muy molesto durante el funcionamiento normal, puede ser también bastante útil en algunos casos. Sin embargo, existe también la posibilidad de forzar a NList a que no redimensione una columna automáticamente. Para que esto ocurra, tiene que arrastrar el separador vertical al tamaño deseado (en realidad tendrá que arrastrar todas) y utilizar entonces la función 'snapshot' de MUI a la que tiene acceso normalmente a través del icono en la esquina superior derecha de la ventana principal de YAM.

Los botones de la barra de herramientas y otros gráficos se muestran con colores erróneos. ¿Por qué?

Usualmente esto ocurre debido a un fallo en la 'ilbm.datatype' y sólo ocurre si YAM se está ejecutando en pantallas hicolor o truecolor. Puede encontrar una actualización de ILBM.datatype en Aminet.

Los botones de la barra de herramientas no caben en la ventana, los botones situados a la derecha no se pueden acceder. ¿Cómo puedo solucionar esto?

Algunos usuarios creen que los gráficos son demasiado grandes, pero de hecho las etiquetas de los botones se comen demasiado espacio. Si está utilizando como fuente de etiqueta la topaz/8, entonces algunos de los botones no serán visibles en una pantalla de 640 de ancho de resolución. Solución: seleccione 'Preferencias/MUI' y vaya a la sección de 'Barra de Herramientas'. Ahora puede o elegir una fuente más delgada (helvetica/9 funciona bien) o desactivar completamente las etiquetas (modo 'sólo imágen').

El diseño de la ventana de preferencias no se adapta apropiadamente cuando se reduce su tamaño, ¿hay alguna solución disponible para esto?

Sí, lo sabemos y se ha corregido el tema en nuevas versiones de YAM. De hecho, fue un fallo en el diseño de la ventana de preferencias de las versiones ⇐ 2.4p1 de YAM. Cualquier versión posterior no deberá tener este problema.

La impresión no parece funcionar. ¿Qué está fallando?

El funcionamiento de impresión en YAM es directamente utilizando el device PRT: del sistema operativo que esté utilizando. Por favor asegúrese de tener el dispositivo debidamente configurado y verificado que puede imprimir a través del PRT:. De esta forma, YAM no hace nada especial en la impresión.

La impresión parece funcionar, pero siempre obtengo un aviso de advertencia justo antes de que el documento se imprima?!?

Bajo ciertas circunstancias puede ocurrir que cuando intenta imprimir un mensaje, obtenga un aviso de advertencia sobre si la impresora está fuera de línea y/o notificar que la impresora no tiene papel. Sin embargo, cuando presiona Okay/Ignorar el documento se imprime perfectamente sin problemas.

La razón para este extraño comportamiento es, que YAM tiene una rutina de comprobación de impresora que intenta identificar si la impresora está en línea y/o no tiene papel. Sin embargo, esta rutina no puede funcionar bien en algunas ocasiones o si su impresora y/o printer.device notifica un estado de error.

Para sortear el problema puede definir YAM para suprimir la advertencia completamente y directmente enviar la información a la impresora a riesgo de obtener quizás estados de impresora incorrectos. Todo lo que tiene que hacer es abrir su archivo YAM:.config en un editor de texto y buscar en la configuración, "PrinterCheck". Todo lo que tiene que hacer es definir esta opción como "N" y guardar el archivo. Entonces YAM no le agobiará con estas notificaciones de error nunca más a partir del momento que lo reinicie.

¿Por qué YAM toma los corchetes como en "http://www.example.com" como parte de URLs?

A pesar de las recomendaciones en RFC 1738 para decodificar cada caracter cuando son supuestamente parte de una URLs, un número de servidores de Internet, entidades y usuarios siguen utilizando el "[]" corchete en formato no codificado, y esto suele hacer que YAM detenga el reconocimiento de una URL en el momento en que se encuentra tales caracteres, como en "<http://www.example.com/files[7]/myfile>". Como forma de evitar este problema, YAM 2.4 toma estos caractéres como parte de la URL. Los paréntesis están permitidos en URLs en formato no codificado, el cual otra vez niega el uso de () para delimitar URLs. Está avisado de que hay que utilizar "<" y ">" para este propósito.

¿Por qué YAM falla o se cuelga cuando entro en la sección 'Mixed/Misc' en la ventana de configuración o mientras inicia?

Esto puede ser a causa de fallos en el sistema XPK (una colección de librerias utilizadas para comprimir y encriptar archivos). Es conocido que la versión 4.31 de XPK tiene un fallo en la función xpkQuery(), así que deberá actualizar al menos a la versión 4.32 o posterior. Además, en la versión 4.33 hay una versión fallida de xpkNONE.library que se puede encontrar en el directorio LIBS:compressors. Sugerimos que borre este archivo (¿quién lo utiliza?). Se pueden encontrar versiones recientes de XPK en http://www.dstoecker.eu/xpkmaster.html.

Y por último pero no menos importante, otras librerías para comprimir de terceras partes guardadas en el directorio LIBS:compressors pueden causar el mismo problema. Así que si le pasa el problema mencionado arriba, le sugerimos que utilice herramientas como 'SnoopDOS' para seguir la secuencia de apertura de la librería mientras cambia a la página de configuración 'Mixed/Misc' de YAM. En el momento en que YAM falle a causa de una librería para comprimir defectuosa, se le notificará en la salida de SnoopDOS. Elimne esta librería defectuosa de LIBS:compressors e intente iniciar YAM otra vez.

Why there are Enforcer hits when flushing memory after uniconifying YAM and its MUI prefs?

If you iconify YAM while its MUI prefs window is opened, then you do an AVAIL FLUSH and then uniconify YAM, you get Enforcer hits. Unfortunately, this is a bug in MUI ⇐3.8. The same problem can be reproduced with any other MUI application.

No puedo cambiar la dirección de remitente (De) en la ventana de escritura desde la versión YAM 2.8. ¿Por qué?

Esto no es correcto. Correcto es, que la ventana de escritura ya no tiene una opción para cambiar el texto de la dirección del remitente (De). Pero ahora hay una completa y más poderosa forma de cambiar la dirección del remitente que introduciendo el texto en un campo. Since YAM 2.8 you can setup an unlimited number of 'identities' in the global YAM configuration. There, identities can be setup to have different sender addresses and as soon as you have configured more than two identities the write window will show a 'From:' cycle gadget that will allow you to easily change the identity and thus the sender address for the mail you are currently composing.

So you simply have to setup as many identities as you use different email addresses and then use the cycle gadget in the write window instead. In addition, if properly setup, this identity support also allows you to chose different SMTP servers, sent mail folders, default signatures and other options per identity which is way more powerful than just manually entering different sender addresses each time in a freetext string gadget.

Language Support

There seems to be no translation available for my language?

Well, as you might know. YAM is open source and as such is highly dependent on on the users (community) - especially when it comes to locale translation. Even if there are organisations like the ATO who are trying to organize a global and free translation service for Amiga applications, we are trying to give individual the chance to contribute their translation.

So if you find that YAM isn't yet fully translated for your language, please have a look at Localization document. There you should find information on how to generate your own translation file and also contribute to us.

We are looking forward to receive your translations.

Reading Mails

Why are some mails displayed without any text content which got displayed properly some weeks ago?

Mails may contain several "streams", like the normal text and attachments. The text however may also exist in more than just one variant. The standard allows plain text and HTML text to coexist within one mail, but in this case both parts must contain the same text, even if they are displayed differently.

Now some very smart companies, but this also applies for spam mails, decide to fill only the HTML part with their message and leave the alternative text part empty. Most mail clients on other systems prefer to display HTML text this goes unnoticed by the masses and nobody complains. Since YAM still prefers plain text over other alternatives and hence will display a mail with no body at all.

However, this can be worked around. Open the config window, go to the "Read" page and activate the options "Display all texts" and "Show alternative parts". This will let YAM display the alternative HTML part as an attachment and additionally will show this HTML part converted to text.

When displaying an email with embedded soft-styles such as bold/italic, etc. the mail will be displayed with the style markers '*' as well, why?

In versions previous to YAM 2.5+, email messages were displayed with the soft style markers in a mail. However, this cause severe trouble in case a style marker was incorrectly recognized so that text was mixed up. Especially for formatted text like stylished ASCII-art signatures or documentations this ended up in a completly mixed up display of the email. In addition, other mainstream email programs also didn't strip the soft-style markers for the very same reasons.

Example: Considering that an author of an email wrote a short ASCII-art documentation in an email to e.g. explain a bit mask that he used and where he wanted to highlight the first bit as important in bold:

0      1 0 1 1
|      | | | |
|      | | | bit5
*bit1* | | bit4
       | bit3
       bit2

Due to the used '*' bold-style characters this may have ended up looking like the following in YAM < 2.5 because the '*' chars were completly replaced by the bold style only:

0      1 0 1 1
|      | | | |
|      | | | bit5
bit1 | | bit4
       | bit3
       bit2

As can be seen in that example, the ASCII-art here is completly mixed up due to the removed "*" bold-style characters.

However, now with YAM 2.5+ these kind of problems were fixed by keeping those soft-style characters in the showed mail text so that the above example now perfectly ends up being display correctly with the bold style and its markers:

0      1 0 1 1
|      | | | |
|      | | | bit5
*bit1* | | bit4
       | bit3
       bit2

In addition to that fix, it is now more easily possible to spot which character can be used to start writing a word in bold style rather than having to always use the corresponding toolbar button.

Doubleclicking an URL doesn't seem to popup my favourite webbrowser?

For automatically popping up your webbrowser upon clicking on an URL in a mail you are view ing in YAM, you require to configure either an external Arexx script to popup the web browser or to install and configure openurl.library and its corresponding tools. Here we are going to discuss both possibilities. However, OpenURL should be considered the default preferred way.

via OpenURL: Before we are going to discuss how to configure OpenURL correctly, please make sure you have the very latest version correctly installed and reachable for YAM. As of writing, the latest version of OpenURL is version 7.2. Please make sure that the following command outputs similar values on you shell:

1> version LIBS:openurl.library full
openurl.library 7.2 (01.12.2005)

In addition, you should have a preferences program 'OpenURL' in you SYS:Prefs drawer. This is the main configuration tool for OpenURL. On a freshly installed OpenURL setup, it contains default settings. However, please note that these defauls do most likely NOT work out-of-the-box. You have to actually change them to your own iternet applications environment. As we are currently only interested in setting up a web browser in OpenURL, we take IBrowse as an example.

So, if you have the preferences application open, you will see different registers for web browsers, mailers and FTP programs you can configure. In 'Browsers' you should find an 'IBrowse' entry with some default settings. Doubleclick on it and make sure the following window shows the similar information:

Please note, that especially the "Path" setting definitly requires a change, as you are supposed to put in the correct directory/file path to the IBrowse executable. However, make sure that the "%u" part at the very end of the string remains.

Next, make sure that in the main configuration window, the 'Misc' register contains the following settings:

Now, if you have everything correctly configured and setup according to the above explainations, you should be able to open an URL even from the command line via the C:OpenURL executable that was also supplied with the default OpenURL installation:

1> openurl http://www.yam.ch/

This should, if correctly configured, fire up IBrowse in case it was configured to be the web browser with the highest priority in OpenURL. So please check your OpenURL configuration that e.g. IBrowse is at the top of your configured web browser list. In addition, if the above openurl command didn't succeed with automatically launching your web browser, try to use tools like SnoopDOS or Snoopy for tracking what OpenURL is trying to do when you execute the C:OpenURL command.

If this worked as expected, you can now try to doubleclick on an URL in a mail mesage in YAM (after having restarted YAM). If this still doesn't fire up IBrowse as the C:OpenURL did, then please have a look at the "Scripts" configuration tab in YAM. There, you have to make sure that you have NOT configured any arexx script for handling the doubleclicks on URLs. ("When double-clicking a URL" have to be empty)

via Arexx: If, for whatever reason it might be, you want to use a plain Arexx script for firing up the correct web browser, all you have to do is - go to the 'Scripts' configuration tab in YAM. There, make sure that you have the 'GotoURL.yam' script configured for the doubleclick actions on URLs. In addition, you have to make sure that - if you have YAM 2.5+ running - the script command string contains an %p qualifier at the end, like:

For YAM 2.5+:

YAM:Rexx/GotoURL.yam %p

For older YAM versions:

YAM:Rexx/GotoURL.yam

However, please note again, that the preferred way of configuring a doublick action on URLs is, to use OpenURL instead of the limited Arexx script possibility.

YAM shows the default icon for attachments rather than the one I configured in DefIcons. Why?

YAM 2.5+ introduced a new so-called AttachmentGroup which shows all attachments of a mail in an icon/image bar at the bottom of the mail read window. For each attachment, it will show a seperate icon/image depending on the file type of the attachment. For archieving this, it uses the DefIcon system of the operating system it is runing on. This system allows (through SYS:Prefs/DefIcons) to configure seperate icons for various types of files. Unfortunately, it is limited and especially the way third-party applications like YAM can query the icon/image for a certain file isn't perfect at all. In addition, the way DefIcon identifies a file type is based on certain rules a user can configure in SYS:Prefs/DefIcons where some rules do actually try to analyze the binary content of the file in question and therefore require the actual file to exist.

Now, when YAM is going to show the user the AttachmentGroup, it hasn't decoded all different MIME parts due to performance reasons. This means, that at the time YAM tries to show the user the icon/image for an attachment, it just knows the filename, description and size of the attachment, but it hasn't actually written the binary data of it to disk. So, at the time YAM is going to ask the DefIcons system for the actual icon/image of the file it can't supply the decoded binary and therefore will only show/query for the default type based on the MIME type of the attachment.

However, as soon as the attachment was decoded either because it was viewed/printed/saved from within YAM, the AttachmentGroup will show the correct icon/image based on what DefIcons supplies.

Why do certain mails I receive show up with lines quoted like ">From " even if the author of that mail hasn't written that From line quoted?

Well, the answer is, the badly defined MBOX format is the reason.

Certain mail delivery agents (MDA) and POP3 server implementations do have different interpretations of the MBOX format. In fact there are numerous MDAs (even procmail) out there which do not correctly escape those "From " line appearing in a message body and for that reasons most POP3 servers just plainly delivers the messages out of a MBOX format 'as is' instead of removing the ">" escaping. And unfortunately that missinterpretation is so widely spread over the various MDA implementations that a proper fix for it is really hard - if not impossible.

So, the answer is that this quoting is already done during initial mail delivery and that most likely your ISP is to blame for it. The only sensible approach to finally fix these common ">From " quoting issues is to force your provider to switch to the better defined and well accepted maildir format which doesn't depend on that '>' escaping…

Replying/Forwarding Mails

I can't put my initials into or change the quoting string used on reply! Why?

In YAM 2.5 we removed the possibility to add your own initials to the quoting string '>' that is normally put in front of every line when you reply to a mail. This was done to conform to common netiquettes and the so-called Son-Of-RFC 1036 and its successors.

The point is, that there are some kind of common rules when creating an email. And one of those rules is the way a text/mail should be quoted. Borrowed from the way quoting was common in Usenet, emails use the same '>' quotation character that is put in front of every replied line in a mail. Previous versions of YAM allowed to put your own initials in that quoting string so that a string like 'JD>' was added on all mails that were quoted by the user John Doe. While this seemed to be a nice and neat way of getting more order into the quoting history, it more or less ends up in more obfuscation of mails, especially in large threads. Another point why such initial quotation strings shouldn't be used is, that there is only a very few amount of mail clients that are able to identify these strings as actual quotations and strip or highlight them accordingly on a reply.

Therefore, we generally removed the possibility to add your own initials to the quote string as well as the graphical elements to change the quotation string in the YAM configuration window. We really believe that compatibility to common rules and RFC s is most important.

For further readings on the pros and cons and how a mail should be properly quoted please have a look at http://learn.to/quote. Keep especially an eye on the 'Quotationsmarks' section that pretty much sums the issue up.

When replying to a mail, a wrong To: address is put in the write window, why?

Well, there seems to be a common misunderstanding of the folder based "mailing list" feature in YAM. Normally YAM allows to configure a folder as a so-called "mailing list folder" where you can set a "To: pattern" and "To: address", so that certain mail actions like reply, forward or new mail react differently when the configured pattern matches the To: address of a mail. For example, if you are suscbribed to the YAM user mailing list your ought to have a seperate folder for the posts arriving from the YAM mailing list and eventually your folder configuration will have a configuration similar to:

'To' pattern: #?yam@freelists.org#?
'To' address: yam@freelists.org

So in case you are pressing reply to a mail where the To: matches the configured pattern, the preconfigured "To: address" of the folder will be inserted instead.

However, it seems that some people mix up the "To: pattern" and set it to "#?" or their own mail address only. This is clearly not what this 'To' pattern is all about and definitly ends up in not being able to correctly reply to a mail - especially when you are in the Incoming folder.

So, please go through all your folder configurations (doubleclicking on each folder) and check that you have the "To: pattern" correctly set or the mailing list feature disabled for the folder. Best practice would be, if you want the mailing list feature enabled, to use the "Auto" button in the folder configuration window. This will automatically try to find out the correct pattern and mail address in case you already have some mails in the folder.

In addition, please also keep in mind that when replying to a mail that is stored in the incoming folder, YAM will check all mailing list configurations of all folders. That means, if you press "reply" on a mail in the incoming folder, YAM will walk through all your folders and if a "To: pattern" matches the mail, the write window will get the specified "To: address" instead of the mail's original sender address. So here the incoming folder is somewhat special and therefore it is absolutely necessary to have all 'To' patterns of all folders setup correctly.

What's the purpose of the 'Bounce' option in YAM and can I use it to e.g. bounce SPAM mail back?

Since early versions (2.3), YAM has a 'bounce' (remail) option which allows to send a mail to an alternative recipient as it would have been sent to that recipient originally. This functionality is also often called a 'remail' operation. What YAM does is, to take the mail as you have received it and directly remail it to an alternative recipient. The new recipient will receive that mail with more or less not noticing that it was send to an another person previously.

In fact, 'more or less' in this term means, that YAM will add some special header entries (e.g. 'Resent-From:' header) to signal that the mail in question was not really comming from the original author directly, but 'resent' instead. This is to conform to RFC s and to give the new recipient at least a minor hint that the mail in question may have been altered on the way.

So if you once received a mail on accident which normally should have gone to someone else you can use the bounce functionality to do that. Another use case could be to forward the mail as is to another account of your own.

However, this functionality is not meant to be used to bounce the mail back to the original author. This includes that e.g. if you received a SPAM message you want to bounce it back to the original author (the spammer) to give him the impression that something went wrong and that the user didn't exist. That's not only producing unnecessary email traffic but also isn't the scope of the bounce functionality in YAM. In addition, since 95% of the junk mail have bogus sender addresses this would result in error messages or that you have sent SPAM yourself to someone innocent. Spammers themself don't care about whether the mail makes it or not (hence the bogus address). All they are after is the small percent that fall for whatever they are spamming for. If the address is simply bad then it is going to bounce back or more commonly it is someone else's address that is going to get bombarded with bounced messages.

Why are are mails duplicated in the Outgoing folder when editing them again later?

With YAM 2.9 the usage of the Outgoing folder has changed. It is no longer used to store both "unfinished" AKA "work in progress and put on hold" mails together with "finished" AKA "ready to be sent" mails, but only "finished" mails. If you plan to make further modifications to a mail before finally sending it out you should not click on "Send now/later" in the write window but on "Save as draft". This will place the mail in the new Drafts folder to make further modifications at a later point in time. Mails in the Drafts folder will never be sent out by YAM, but can easily be edited again by a simple double click.

However, modifying a "finished" mail in the Outgoing folder is still possible, but then the mail will be treated as any other received mail and YAM will create a new mail in the Outgoing folder. It is then the user's task to decide which mail is the one to be sent out. The other one should be deleted to avoid confusion for the receiving recipients.

Composing Mails

Is it possible to send an email to a group of recipients in one go?

Yes it is. You just have to create a new list with a suitable name in YAM's address book and add all the desired recipients. Then add this list as a regular recipient when writing a mail.

When writing an email I get an error message like "+++ Host environment not found"?

If you are about to write an email in the internal texteditor of YAM and you automatically get an error message similar to this one:

+++ Error 13 in line 1: Host environment not found

This points out that the internal TextEditor.mcc tries to perform spell checking via its internal functionality. So this is no error message from YAM, but an error message comming from TextEditor.mcc. To get rid of the warning, please go to the MUI preferences (SYS:MUI/MUI) and make sure you disable the spell checking of TextEditor.mcc within its MUI preferences there. Afterwards the above error message should vanish.

But if you prefer to get the spell checking running, please consult additional documentation about the AlphaSpell support of TextEditor.mcc and how to properly set it up.

Why isn't YAM able to mark whole sentences as bold/italic/underline and just highlights single words? Wasn't that possible already?

Since YAM 2.5 the text highlighting functionality in YAM was changed according to more or less established standard when writing/displaying email on different email programs.

Previously, the internal TextEditor allowed to mark whole sentences as bold/underline/italic/colored whereas this operation ended up in showing those sentences in the corresponding style. When having sent the mail it would then end up as e.g. the following example in the final email message:

*This sentence in bold*

However, this scheme was completly incompatible to the given established standards in the email client community. Mailers such as Thunderbird never displayed those sentences in the correct style. In addition, it wasn't quite intuitive to notice the bold state when reading through such emails in the first place especially if they are wrapped to the next line.

Therefore, the highlighting practices were changed in YAM 2.5 so that each single word in a sentence will now be selected and set to the corresponding style separatly. So now the above sentence will end up looking like the following in YAM 2.5:

*This* *sentence* *in* *bold*

Even if that seems to be very ugly on a first thought, it is the only logical approach to the problem of having such mail interchangeable between different mailers. In addition, in most cases only single words need to get or should be highlighted in an email so that you will hardly set a whole sentence in bold/underline or such.

Why is the TAB key not advancing to the internal text editor gadget when I finished writing the subject line of a mail?

This "problem" should only be visible with YAM versions equal or higher than 2.5+ In fact, it isn't really a problem, but a changed behaviour. The point is, that due to the change to TheBar.mcc the toolbar is now also within the normal MUI "CycleChain" for allowing an application to get fully manageable via keyboard. So, if you are now editing the subject line of a mail and you press the TAB (Tabulator) key, the next activated MUI gadget will be the first toolbar button instead of the TextEditor gadget like it was in versions prior to 2.5.

However, to still being able to switch to the text editor immediately you can use the Return/Enter key instead. That means, if you are finished with editing/writing the subject line and you want to change to the text editor for writing the actual content of the mail, just press the "Return" key instead.

Why doesn't YAM let me choose an address from the popup list when writing a mail?

When completing a yet known address YAM needs to be able to distinguish one address from another. That means that both, alias and realname, should be "relatively" unique. Example: First address book entry Name: foobar Alias: Address: test1@… Second address book entry Name: blafasel Alias: foobar Address: test2@… As soon as you enter "foobar" in the "To:" field the address match list will pop up to let you choose a recipient. But selecting either of these two entries will fail, because YAM cannot tell these two entries apart if "foobar" is the only matching criteria. "foobar" can be resolved to the first entry's name AND to the second entry's alias, but not to one single entry. That is why the resolve will fail. The only soltion for this problem is to use unique names and aliases. That means NO real name must exactly match any other alias, and vice versa.

My system hangs when deleting a block of text in the editor while using a key qualifier, why?

Unfortunately, this is a bug in the Texteditor.mcc ⇐ v15.9 MUI custom class you are using. Please upgrade to the very latest version available at http://www.sf.net/projects/texteditor-mcc

Filtering Mails

If I search for "[SPAM]" in a filter, mails not containing this string will get hit by the filter as well, why?

Well the reason is, that you seem to have missed that the string gadget for entering the search string accepts AmigaDOS wildcards. Therefore, the [ is a special reserved character and have to be escaped to match the literal character itself. So if you want to search for a [ character with an AmigaDOS pattern aware method you have to use:

'[SPAM']

where the ' character escapes the reserved state of the [ and ] chars. However, even more precisly would be to use:

'[SPAM']#?

instead and turn off the "Substring" option. That would then match only subjects that actually start with [SPAM] as there might even be non-SPAM messages contain that string somewhere.

NOTE on searching for [SPAM]:

Matching SPAM messages on the literal [SPAM] marker in a subject line is more or less a bad idea as it would cause (even if correctly escaped) many non-SPAM messages to get filtered incorrectly. Normally SPAM filter add an additional header line like 'X-Spam-Status:' to each checked email. So to reduce the amount of incorrectly matched mails you would be better off searching for that optional header line and search if it starts with "Yes".

How to train YAM's SPAM filter properly?

YAM's spam filter is an adaptive filter - a so-called Bayesian spam-filter - which was ported from the well-known mail client Thunderbird and behaves exactly the same.

Background: The nature of this kind of spam filtering is an iterative learning process where the content of a mail will be evaluated according to a calculated spam probability. That means, that right from the beginning it is absolutely "stupid" and doesn't know which mails are actually spam or no spam. Hence the filter needs to be trained manually to be able to distinguish between spam and no spam.

Usage: After enabling the spam filter all newly received mails will most likely be classified as spam and automatically moved to the spam folder. This is absolutely normal and intended! Again, keep in mind that the spam engine is "stupid" and only relies on your user input.

Now you have to tell YAM which mails are really spam and which are not spam (so-called Ham). Just mark all regular (no spam) mails which were moved to the spam folder as "Not Spam" and move them to another folder (i.e. the incoming folder). This will train the spam engine about how "no spam" mails look like. Such mails are called false negatives because they were automatically flagged as spam but they aren't spam. Continue to do so as more "no spam" mail arrives which will be automatically flagged as spam on accident.

Of course, the spam procedure applies to spam mail that was not recognized as spam. If new mail arrives and it wasn't properly recognized as spam flag it as spam manually. Continue to do so as new mail arrives. After some time YAM will gradually become better in correctly recognizing spam mails itself and you will have to classify false positive and not recognized spam mails yourself very seldom - However, there will always remain a small probability of false positives and not recognized spam mail, no matter what.

WARNING: You should NOT "enforce" the learning process by classifying all your previously collected spam mails manually after enabling the spam filter. YAM will learn best by itself with a little help by the user, as described above. Only newly received emails should be manually flagged as spam or no spam. Usually about 100 mails (good as well as bad) are enough to let YAM recognize spam mails correctly with a probability of 90% and more. However, if for some reason the spam filter "stops" to work for you no matter how to train it, go to the YAM configuration and reset the SPAM training data and restart flagging spam and no spam manually as new mail arrives.

Network Setup

How to properly set up SMTP-AUTH authentication?

Some mail providers (ISP) recently changed their requirements regarding to how incoming mail is handled and who is allowed to send mail through their servers via the SMTP protocol. This mainly was necessary to reduce the amount of SPAM, thus letting only authorized users send mails. This protocol is called SMTP-AUTH and fully supported by YAM 2.5+.

Often providers even require the users to connect to their SMTP servers via an encrypted connection only. This is what the SSL/TLS feature in YAM is for. Together with the required AmiSSL library, it fully encrypts every transfer through YAM and the mail server. To use such a secure connection you must install AmiSSL V3.5. While AmigaOS4.0 already comes with AmiSSL V3.5 installed, for OS3.x or MorphOS you have to download AmiSSL 3.6 from the AmiSSL homepage and install it on your system.

To properly configure a SMTP-AUTH connection in YAM, you can go to the TCP/IP page of the configuration window. There you have to make sure that you have configured SMTP accordingly:

    secure connection type: SSLv3 (if it is required)
    use SMTP-AUTH: yes
    User name: <your user name>
    Password: <your password>
    Method: Auto

Usually 'Auto' as the authentication method should be suffice. If your mail provider still doesn't accept your mails then you should select a specific authentication method (DIGEST-MD5, CRAM-MD5, LOGIN or PLAIN).

And if you are still unable to send mails even via one predefined method, then you can run YAM with the DEBUG command-line option. This option will enable the internal TCP/IP debugging and output any raw output of the connection on the shell you just started YAM from. See FAQ item for more information on how to debug YAM.

When sending mail via smtp.gmail.com, YAM returns an error upon terminating the connection. However, the mail will be correctly send to its recipient.

It seems that this is a problem/bug in the SMTP server implementation of the googlemail mail servers (smtp.gmail.com, smtp.googlemail.com, …). When sending an email over one of the SMTP servers of googlemail, the server immediately drops the connection when the client (YAM) signalled the server that it wants to quit the connection. However, the standard (RFC 2821) clearly defines that if a server receives such a QUIT command, it have to reply with a status code and afterwards drop the connection. Unfortunatley, the googlemail servers seems to not send this status code anymore if a mail was already successfully transfered. This of course, clearly violates the standard and causes YAM to drop an error/warning message about an unexpected connection drop.

Unfortunately, there doesn't exist any way of avoiding/supressing those warnings with YAM 2.4. However, recent versions (2.5) have an added workaround for the problem and doesn't automatically popup those warnings anymore.

Still, we highly suggest to send an email to the support of googlemail and let them know about the problem. Of course, feel free to cite this FAQ item in the hope that at one day googlemail developers will read it and fix their SMTP server implementation.

In addition to the above violation to the RFC s, the gmail servers seem to have a rather long timeout phase when communicating to SMTP clients like YAM. This means that upon sending an email it might happen that right at the end of the communication to the SMTP server of google, YAM returns an error because the gmail server didn't correctly response within the internally specified time interval within YAM. On the other hand it might be that this time interval was simply incorrectly set to a too short value. So please make sure (if you have YAM 2.5+ running) that your ".config" file has the "SocketTimeout" value right at the end of the file set to at least 30 or even higher which means that YAM will wait 30 seconds for a response from the mail server before considering the connection being broken/dropped.

When I use Genesis, Yam always uses the Genesis user to choose the account. How can I change that?

YAM has special built in support for the Genesis TCP/IP stack by being able to query the currently active username. So it supports to automatically start YAM with the user that your Genesis TCP/IP stack is currently running. E.g. If you have Genesis configured for a user "john doe" and you have the very same username in YAM configured, it will startup automatically with that user enabled and doesn't query for any user selection or password.

However, if for some reasons you are not able to sync the user names of Genesis≠YAM, you can start YAM either from the command line with the option "USER <USERNAME>" or by adding the 'USER' tooltype to the YAM icon. In that case, YAM will then automatically select the specified user and just query for the password.

I am not able to abort a POP3 transfer and the whole application seems to hang, why?

YAM has been a single-threaded application until version 2.7 which uses so-called blocking socket I/O. This means, that until version 2.7 it could only process one job at a time and a single TCP/IP transfer like a POP3 or SMTP connection or transfer might lock up the whole application (even GUI operations) in case the server doesn't response. This, for example can happen if the POP3/SMTP server you are trying to connect to isn't responding properly or your connection is suddenly interrupted.

The reason for the GUI lockup is, that as soon as YAM is trying to connect to other server, it is fully relying on the functionality of the TCP/IP stack you are running on your operating system (e.g. Roadshow on AmigaOS4). And as YAM is still using blocking socket I/O and that the TCP/IP stack might have a large timeout for retrying a certain TCP/IP operation it suddenly can cause your YAM application to block until the TCP/IP stack decides to return from the blocking socket call.

Even if for most connection types and users this might not be a big issue, we know that it can become very annoying and disturbing. Especially if you are having a dail-up connection. However, we have already planned to address the issue in a future version by introducing full multi-threading together with the use of non-blocking socket I/O in YAM. Until that happens, you can also try to lower the timeout of your TCP/IP stack and/or try to shutdown the TCP/IP stack if a connection suddenly locks up YAM.

As mentioned earlier, since version 2.7 YAM is fully multithreaded and should not block any GUI elements during a network transfer.

I have automatic mail download/send on startup enabled, but YAM 2.6 doesn't perform the mail exchange. Why?

YAM supports multiple users. Each of these users must have a real name to enable YAM to distinguish between these users. This name must be set in YAM's user management.

The problem with the automatic mail exchange on startup arises if a user doesn't have a real name. In this case YAM 2.6 cannot detect that upon a (re)start the user has changed and hence it will skip the automatic mail exchange completely. However this can only happen if you never ever opened YAM's user management to give the user a real name.

The solution is very simple: open YAM's user management window, check all user names to be correct and close the window again. After that the automatic mail exchange upon start will work again.

Attachments (3)

Download all attachments as: .zip