Phoenix Network Forums

I've the impression, that e-mails originated on infinity don't currently go out. I've tried it using /usr/bin/mail . Can that be checked (resp. fixed), please?

Regards
Thomas

I don't even know how to use mail, however infinity's smtp server works fine for sending mail and I'm still receiving system logs from infinity which suggests that mail also works.

I'm going to need a bit more information for me to look into this properly.

Tim wrote:I don't even know how to use mail, however infinity's smtp server works fine for sending mail and I'm still receiving system logs from infinity which suggests that mail also works.

I'm going to need a bit more information for me to look into this properly.

Code: Select all

echo "This is a dummy message" | mail -s "This is the subject" recipient@domain

I've tried to e-mail this way to two different addresses (different domains) where I can check the reception, and wonder why nothing arrives.

I don't prefer running /usr/bin/mail directly, but since my usual email client (Emacs/Gnus) did not succeed in sending the e-mail, I ran /usr/bin/mail for diagnostic purposes and to provide you with a test without forcing you to use Emacs/Gnus - you probably won't learn and run Emacs/Gnus

Every E-Mail client configured to call /usr/sbin/sendmail directly (i.e. not going through the SMTP interface) should be Ok to test what I mean.

Does it work, if you run /usr/bin/mail like above?

Regards
Thomas

You're right it doesn't work and I know exactly why.
Well I don't...but my reason explains why it isn't throwing an error.

edit: it should work now...but with my luck it probably doesn't :/

Tim wrote:You're right it doesn't work and I know exactly why.
Well I don't...but my reason explains why it isn't throwing an error.

edit: it should work now...but with my luck it probably doesn't :/

Yeah, I don't know what you did (neither what to break nor what to fix it again), but it works now, thanks. It's a good thing that you repaired it. E.g. CGI mailing programs often need a working sendmail to do their job.

BTW, when sending mails in that way, the realname would be filled in automatically, if it was known by the system. I tried to set my real name using chfn -f, but it's forbidden by configuration, see http://forums.phoenix-hosting.org/viewtopic.php?t=2535. Is there any reason, that the user is not allowed to set his name? Otherwise I suggest to drop that restriction.

Regards
Thomas

I'm assuming its a restriction set by directadmin, it doesn't seem like the kinda thing that would be in a system by default. I'll have a look at it in the weekend or on wednesday or something for you.

Also, it was never broken just the firewall was blocking it; eth0 only allows you to access ports below 1024 now, previously it was only port 80.

Tim wrote:I'm assuming its a restriction set by directadmin, it doesn't seem like the kinda thing that would be in a system by default. I'll have a look at it in the weekend or on wednesday or something for you.

The restriction may be usefull inside a company, where the name field is filled in once by administration/secratary or similiar and should not be changed by the user itself. But here the name field is just empty. Funny: if you fill in another field, e.g. the room number (that's allowed), then the system will generate an e-mail alias by composing the empty name and the room number (e.g. ",42,,", if room number 42 has been entered).

Tim wrote:Also, it was never broken just the firewall was blocking it; eth0 only allows you to access ports below 1024 now, previously it was only port 80.

Yes, e-mail server was working properly, but the e-mails have been blocked since Thursday or Friday. I noticed that, because my ~/.forward file here did work no longer. But know, as the needed port isn't blocked anymore, the queued e-mails are sent out. They're just delayed, not lost.

Thanks
Thomas