Operating system name and version: Linux kello.ru 2.6.32.16-141.fc12.i686 #1 SMP Wed Jul 7 04:47:25 UTC 2010 i686 i686 i386 GNU/Linux
Version of smsd: smstools-3.1.3-7.fc12.i686
Smsd installed from: package repository
Name and model of a modem: Huawei Technologies Co., Ltd. E620 USB Modem
Interface: USB

Dear all!
I'm trying to build email2sms gateway using fedora linux and Huawei USB-modem. The system runs sendmail with procmail to sort mail. I'm trying to use email2sms example script that was supplied with smstools. I have created user 'test' on this host (kello.ru). After I've created .procmailrc file in his home directory:
VERBOSE=off MAILDIR=/var/spool/mail DEFAULT=/var/spool/mail/test LOGFILE=/var/log/procmail :0 * ^TOtest | /usr/local/bin/email2sms

Now I see in /var/log/maillog:
Jul 22 16:01:31 kello procmail[15242]: Suspicious rcfile "/home/test/.procmailrc"

I can send sms using smssend command. But no message arrives when I'm sending e-mail to test@kello.ru. No new files appears in /var/spool/sms/* Only this strange messages in smsd.logfile:2010-07-22 16:10:35,3, GSM2: Could not send character A, cause: Input/output error 2010-07-22 16:10:45,3, GSM2: Could not send character ., cause: Input/output error 2010-07-22 16:10:55,3, GSM2: Could not send character A, cause: Input/output error 2010-07-22 16:11:05,3, GSM2: Could not send character ., cause: Input/output error 2010-07-22 16:11:15,3, GSM2: Could not send character A, cause: Input/output error

Could anybody point me to solution of this problem? Any help will be appreciated!
TIA

Hiisi wrote

Now I see in /var/log/maillog:
Jul 22 16:01:31 kello procmail[15242]: Suspicious rcfile "/home/test/.procmailrc"

[ Select ]

Try this:
# chmod 0640 /home/test/.procmailrc

Also check who owns the file, and change it if it's not owned by user test. And check that /home/test is owned by test:test.

Hiisi wrote

I can send sms using smssend command. But no message arrives when I'm sending e-mail to test@kello.ru. No new files appears in /var/spool/sms/* Only this strange messages in smsd.logfile:2010-07-22 16:10:35,3, GSM2: Could not send character A, cause: Input/output error 2010-07-22 16:10:45,3, GSM2: Could not send character ., cause: Input/output error 2010-07-22 16:10:55,3, GSM2: Could not send character A, cause: Input/output error 2010-07-22 16:11:05,3, GSM2: Could not send character ., cause: Input/output error 2010-07-22 16:11:15,3, GSM2: Could not send character A, cause: Input/output error

[ Select ]

smssend? It's not a program from Smstools. Probably you have another SMS daemon running. It may also cause that "Input/output error", which means that the device is not usable. Check if another process is using your modem, and try to stop it. Also check what ports were provided when you plugged your modem (using dmesg), and if there is more than one port, try with another one.

keke wrote

Hiisi wrote

Now I see in /var/log/maillog:
Jul 22 16:01:31 kello procmail[15242]: Suspicious rcfile "/home/test/.procmailrc"

[ Select ]

Try this:
# chmod 0640 /home/test/.procmailrc

Also check who owns the file, and change it if it's not owned by user test. And check that /home/test is owned by test:test.

Done that. It has been owned by root. But still having the same warnings in /var/log/maillog

keke wrote

smssend? It's not a program from Smstools. Probably you have another SMS daemon running.

[Sampo@kello ~]$ yum provides /usr/bin/smssend Ladatut liitännäiset: fastestmirror, presto, refresh-packagekit, show-leaves smstools-3.1.3-7.fc12.i686 : Tools to send and receive short messages through : GSM modems or mobile phones Asennuslähde: fedora Vastaavuus : Tiedostonimi: /usr/bin/smssend smstools-3.1.3-7.fc12.i686 : Tools to send and receive short messages through : GSM modems or mobile phones Asennuslähde: installed Vastaavuus : Muuta : Tarjoajavastaavuus: /usr/bin/smssend

keke wrote

It may also cause that "Input/output error", which means that the device is not usable. Check if another process is using your modem, and try to stop it.

Sorry, I don't know how to do that

keke wrote

Also check what ports were provided when you plugged your modem (using dmesg), and if there is more than one port, try with another one.

From dmesg output:
usb 1-4: new high speed USB device using ehci_hcd and address 118 usb 1-4: New USB device found, idVendor=12d1, idProduct=1001 usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0 usb 1-4: Product: HUAWEI Mobile usb 1-4: Manufacturer: HUAWEI Technology usb 1-4: configuration #1 chosen from 1 choice option 1-4:1.0: GSM modem (1-port) converter detected usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0 option 1-4:1.1: GSM modem (1-port) converter detected usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2 option 1-4:1.2: GSM modem (1-port) converter detected usb 1-4: GSM modem (1-port) converter now attached to ttyUSB3

When I pug in this modem there's always 3 new devices:
/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB2
or
/dev/ttyUSB1
/dev/ttyUSB2
/dev/ttyUSB3
Or sometimes (like in the output above):
/dev/ttyUSB0
/dev/ttyUSB2
/dev/ttyUSB3
It doesn't matter which one I use in /etc/smsd.conf. So, I've created 3 devices:
[root@kello ~]# cat /etc/smsd.conf # Example smsd.conf. Read the manual for a description devices = GSM1, GSM2, GSM3 logfile = /var/spool/sms/smsd.log infofile = /var/run/smsd/smsd.running pidfile = /var/run/smsd/smsd.pid loglevel = 5 checkhandler = /var/spool/sms/ucsautoconvert # Settings to run smsd without root priviledges: user = Sampo group = dialout outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed incoming = /var/spool/sms/incoming sent = /var/spool/sms/sent [GSM1] device = /dev/ttyUSB0 incoming = yes report = yes #pin = 1111 [GSM2] device = /dev/ttyUSB1 incoming = yes report = yes #pin = 1111 [GSM3] device = /dev/ttyUSB2 incoming = yes report = yes #pin = 1111

It causes errors like this one:
2010-07-25 15:09:25,3, GSM3: Cannot open serial port /dev/ttyUSB2, error: No such file or directory 2010-07-25 15:09:25,2, GSM3: Modem handler 2 terminated.

But anyway, it works
Still can't find solution to my problem
Kiitos, keke.

Hiisi wrote

keke wrote

Hiisi wrote

Now I see in /var/log/maillog:
Jul 22 16:01:31 kello procmail[15242]: Suspicious rcfile "/home/test/.procmailrc"

[ Select ]

Try this:
# chmod 0640 /home/test/.procmailrc

Also check who owns the file, and change it if it's not owned by user test. And check that /home/test is owned by test:test.

Done that. It has been owned by root. But still having the same warnings in /var/log/maillog

I have to say that I do not know what causes the trouble in your server.

In my server the file .procmailrc is -rw-r--r-- and owned by user:user. Email2sms works as expected. If you changed permissions to 0640, you could try once more with 0644.

As I do not know how to fix this issue, you could try to find a solution with Google, search something like "procmail Suspicious rcfile .procmailrc". It seems that this is a common problem.

Hiisi wrote

keke wrote

smssend? It's not a program from Smstools. Probably you have another SMS daemon running.

[Sampo@kello ~]$ yum provides /usr/bin/smssend Ladatut liitännäiset: fastestmirror, presto, refresh-packagekit, show-leaves smstools-3.1.3-7.fc12.i686 : Tools to send and receive short messages through : GSM modems or mobile phones Asennuslähde: fedora Vastaavuus : Tiedostonimi: /usr/bin/smssend smstools-3.1.3-7.fc12.i686 : Tools to send and receive short messages through : GSM modems or mobile phones Asennuslähde: installed Vastaavuus : Muuta : Tarjoajavastaavuus: /usr/bin/smssend

[ Select ]

Perhaps Fedora package has changed something, I cannot check it right now because I have no FC installed. If that smssend is a script, does it place files into /var/spool/sms/outgoing directory?

Hiisi wrote

keke wrote

It may also cause that "Input/output error", which means that the device is not usable. Check if another process is using your modem, and try to stop it.

Sorry, I don't know how to do that

First stop the smsd if it's running. Then check if a device is symbolic link:

# ls -l /dev/ttyUSB0
lr-xr-xr-x 1 root root 9 Jul 5 14:40 /dev/ttyUSB0 -> usb/tts/0

In my case it's a link. Check if any process is using that device:

# lsof | grep usb/tts/0
smsd 31409 root 6u CHR 188,0 827 /dev/usb/tts/0

In my case smsd is using it, because I did not stop it. You should not see any processes.

Hiisi wrote

keke wrote

Also check what ports were provided when you plugged your modem (using dmesg), and if there is more than one port, try with another one.

From dmesg output:
usb 1-4: new high speed USB device using ehci_hcd and address 118 usb 1-4: New USB device found, idVendor=12d1, idProduct=1001 usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0 usb 1-4: Product: HUAWEI Mobile usb 1-4: Manufacturer: HUAWEI Technology usb 1-4: configuration #1 chosen from 1 choice option 1-4:1.0: GSM modem (1-port) converter detected usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0 option 1-4:1.1: GSM modem (1-port) converter detected usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2 option 1-4:1.2: GSM modem (1-port) converter detected usb 1-4: GSM modem (1-port) converter now attached to ttyUSB3

[ Select ]

When I pug in this modem there's always 3 new devices:
/dev/ttyUSB0
/dev/ttyUSB1
/dev/ttyUSB2
or
/dev/ttyUSB1
/dev/ttyUSB2
/dev/ttyUSB3
Or sometimes (like in the output above):
/dev/ttyUSB0
/dev/ttyUSB2
/dev/ttyUSB3
It doesn't matter which one I use in /etc/smsd.conf. So, I've created 3 devices:
[root@kello ~]# cat /etc/smsd.conf # Example smsd.conf. Read the manual for a description devices = GSM1, GSM2, GSM3 logfile = /var/spool/sms/smsd.log infofile = /var/run/smsd/smsd.running pidfile = /var/run/smsd/smsd.pid loglevel = 5 checkhandler = /var/spool/sms/ucsautoconvert # Settings to run smsd without root priviledges: user = Sampo group = dialout outgoing = /var/spool/sms/outgoing checked = /var/spool/sms/checked failed = /var/spool/sms/failed incoming = /var/spool/sms/incoming sent = /var/spool/sms/sent [GSM1] device = /dev/ttyUSB0 incoming = yes report = yes #pin = 1111 [GSM2] device = /dev/ttyUSB1 incoming = yes report = yes #pin = 1111 [GSM3] device = /dev/ttyUSB2 incoming = yes report = yes #pin = 1111

[ Select ]

 

[ Expand ]

It causes errors like this one:
2010-07-25 15:09:25,3, GSM3: Cannot open serial port /dev/ttyUSB2, error: No such file or directory 2010-07-25 15:09:25,2, GSM3: Modem handler 2 terminated.

[ Select ]

But anyway, it works
Still can't find solution to my problem

Use one port only, because those are interfaces to the same device. In some cases only a certain port was working with AT commands. When in your case any port is working, just select single one.

If possible and necessary, use udev to keep the names of ports the same.

Hiisi wrote

Kiitos, keke.

Ole hyvä.

keke wrote

I have to say that I do not know what causes the trouble in your server.

In my server the file .procmailrc is -rw-r--r-- and owned by user:user. Email2sms works as expected. If you changed permissions to 0640, you could try once more with 0644.

As I do not know how to fix this issue, you could try to find a solution with Google, search something like "procmail Suspicious rcfile .procmailrc". It seems that this is a common problem.

Now I have:
# ls -l /home/test/.procmailrc -rw-r--r--. 1 test test 132 22.7. 15:41 /home/test/.procmailrc

But still having the same warnings in /var/log/maillog...

keke wrote

Perhaps Fedora package has changed something, I cannot check it right now because I have no FC installed. If that smssend is a script, does it place files into /var/spool/sms/outgoing directory?

Yes, it does.

keke wrote

First stop the smsd if it's running. Then check if a device is symbolic link:

# ls -l /dev/ttyUSB0
lr-xr-xr-x 1 root root 9 Jul 5 14:40 /dev/ttyUSB0 -> usb/tts/0

In my case it's a link. Check if any process is using that device:

# lsof | grep usb/tts/0
smsd 31409 root 6u CHR 188,0 827 /dev/usb/tts/0

In my case smsd is using it, because I did not stop it. You should not see any processes.

Thanks for the hint. No other process is using it.

keke wrote

Use one port only, because those are interfaces to the same device. In some cases only a certain port was working with AT commands. When in your case any port is working, just select single one.

If possible and necessary, use udev to keep the names of ports the same.

I have created the following udev rule:
# cat /etc/udev/rules.d/95-huawei-e15150.rules SUBSYSTEM=="usb", ATTRS{serial}=="0000:00:03.3", SYMLINK+="modem" GROUP="dialout"

Now when I plug in the device /dev/modem file appears but ownership is wrong:
# ls -l /dev/modem lrwxrwxrwx. 1 root root 15 26.7. 11:45 /dev/modem -> bus/usb/001/015

I can't understand why GROUP option doesn't work as expected. The bus /dev/modem refer to has right permissions:
# ls -l /dev/bus/usb/001/015 crw-rw-r--. 1 root dialout 189, 14 26.7. 11:45 /dev/bus/usb/001/015

Forgot to mention that smssend doesn't work with /dev/modem in /etc/smsd.conf, even running as root. I have a lot of entries like this in smsd' logfile:
2010-07-26 12:14:46,3, GSM1: Could not send character A, cause: Invalid argument 2010-07-26 12:14:56,3, GSM1: Could not send character ., cause: Invalid argument

Everything works as expected when using /dev/ttyUSB0 in config file.

I do not have more hints on how to get procmail to work in your server. But I believe that Google will help you.


The GROUP option in your udev rule works, but it has no effect with symlink. Try this kind of a rule, it's from my server which is running Ubuntu 9.04:

# Get info: udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB1) # Reload rules: udevadm control --reload-rules KERNEL=="ttyUSB*", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", SYMLINK="controller0", OWNER="smsd", GROUP="dialout", MODE="0600" KERNEL=="ttyUSB*", ATTRS{idVendor}=="0eba", ATTRS{idProduct}=="1080", SYMLINK="modem0", OWNER="smsd", GROUP="dialout", MODE="0660" KERNEL=="ttyUSB*", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="0609", SYMLINK="modem1", OWNER="smsd", GROUP="dialout", MODE="0660"

Those rules creates the following:

# ls -l /dev/controller0 /dev/modem*
lrwxrwxrwx 1 root root 7 2010-07-26 14:41 /dev/controller0 -> ttyUSB0
lrwxrwxrwx 1 root root 7 2010-07-26 14:43 /dev/modem0 -> ttyUSB1
lrwxrwxrwx 1 root root 7 2010-07-26 14:30 /dev/modem1 -> ttyUSB2

# ls -l /dev/ttyUSB*
crw------- 1 smsd dialout 188, 0 2010-07-26 14:41 /dev/ttyUSB0
crw-rw---- 1 smsd dialout 188, 1 2010-07-26 14:43 /dev/ttyUSB1
crw-rw---- 1 smsd dialout 188, 2 2010-07-26 14:31 /dev/ttyUSB2

Smsd uses /dev/modem* and works as with /dev/ttyUSB*.

I have added the following rule:
KERNEL=="ttyUSB*", ATTRS{idVendor}=="1d6b", ATTRS{idProduct}=="0002", SYMLINK="modem", OWNER="smsd", GROUP="dialout", MODE="0660"

And now smsd starts perfectly. It works as expected until strange thing occurs: modem disconnects by itself. Here's dmesg' output:
option: option_instat_callback: error -108 option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 option 1-4:1.0: device disconnected option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 option 1-4:1.1: device disconnected option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 option 1-4:1.2: device disconnected usb 1-4: new high speed USB device using ehci_hcd and address 41 hub 1-0:1.0: unable to enumerate USB device on port 4 usb 3-2: new full speed USB device using ohci_hcd and address 14 usb 3-2: not running at top speed; connect to a high speed hub usb 3-2: New USB device found, idVendor=12d1, idProduct=1001 usb 3-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0 usb 3-2: Product: HUAWEI Mobile usb 3-2: Manufacturer: HUAWEI Technology usb 3-2: configuration #1 chosen from 1 choice option 3-2:1.0: GSM modem (1-port) converter detected usb 3-2: GSM modem (1-port) converter now attached to ttyUSB0 option 3-2:1.1: GSM modem (1-port) converter detected usb 3-2: GSM modem (1-port) converter now attached to ttyUSB1 option 3-2:1.2: GSM modem (1-port) converter detected usb 3-2: GSM modem (1-port) converter now attached to ttyUSB2

In some other thread I saw you told the OS causes this. So, I have asked this question on Fedora' mailing list. Hope will get support there soon.
As for the problem with warnings about suspicious .procmailrc fail, I've found solution to it. it was wrong test' user home directory permissions that caused this. I had to make sure it's writeable only by user itself (and not by its group).
Anyway, thanks for fast and useful support, Keijo. Appreciate that!