Bugzilla – Bug 561813
Capisuitefax: missing MailandSave Function
Last modified: 2009-12-13 13:17:26 UTC
+++ This bug was initially created as a clone of Bug #556236 +++ After fixing the isdn trouble with the newly built capi4linux-package on my 11.2 x86_64 system making the capisuite running now a new problem has appeared which I cannot classify safely as another bug in one of the Capi-Packages or a misconfiguration on my computer so I would be grateful if anybody could check whether the issue is the same for other capisuitefax-users on 11.2: Incoming Faxes are correctly displayed in the corresponding Fax-received-directory however, though it is properly set in the etc/capisuite/fax.conf file (MailandSave, default setting) the converting of the sff-fax-files and their forwarding to the local email mailbox is not initiated. Same with sent faxes: There is no confirmation forwarded to the Mail account, so you have to look at the log files if the jobs have been done successfully. I hope there are some ISDN/Capi-specialists who can help me to solve the problem as its essential for my business working with openSUSE. Thanks.
In addittion, most parameters given in the fax.conf file are ignored, i.e. fax_action="MailAndSave" fax_headline="XYZ" fax_numbers="19" fax_stationID="+49 8622 919750" outgoing_MSN="19" fax_email="" Neither Fax Headline nor station ID are shown in the sent-fax-file after converting it to tiff or pdf. Greetings Franz
Sorry the ladder is fixed now (Headline etc. is shown now) F.
The problem is fixed for me now. It has NOT been a capisuite bug, however, a (little) error occurs during standard network installation with YAST as - if you change hostname.domain from .site (default) to .local no warning is given that the domain .local should no longer be used as it is due to Multicast DNS use. In order to prevent other users from running into the same rusty knife as I did please consider to move this report to another appropriate site in bugzillas report sites. Thanks.
The mDNS issue is tracked by bug #564317. Please do not hijack existing bugs. Instead file a new one.