On 08/19/2014 09:47 PM, Linda Walsh wrote:
Carlos E. R. wrote:
Nay, the MTA is not broken on systemd systems. It works out of the box,
as always. Maybe, just maybe, you have to just run YaST mail module just
once, in simple mode, accepting defaults (and not configuring fetchmail
in there). But this has been the same for decades.
I agree, I spoke too soon on that because he already said he WAS getting
his email except
for his INBOX. Given that, I think the problem is in him trying to use
format for his inbox. That's non-standard and likely to cause
Will you please stop propagating this nonsense that maildir is non
standard. Its a reliable standard that has been in use for getting on
for 40 years, it long pre-dates Linux, long pre-dates UNIX on PCS. It
history goes back to the MH messaging system and was based on the idea
that the shell/text tools make more sense when email is in a
one-message-per-file format. If that 'stinks' of CLI-ness, then yes,
and it tells you how old this is.
I am all but
certain sendmail doesn't support that and think it would be unlikely for
to support that for '/V/S/M'...
And that too is misinformation as a light browse of the Postfix
documentation shows. For example, this shows how to set Postfix to use
a maildir in the user's home directory:
Googling for 'sendmail + maildir" produces plenty of how-to pages.
So you assertions are misinformation.
None of this is difficult, it is just that it requires *all* the config
files to say the same thing.
Part of the fallacy you are promulgating is false because:
It's not actually sendmail that saves the messages on final delivery,
but the local mail delivery process that sendmail hands the message off to.
Sendmail and postfix both honour the .forward, so the moment ether of
them deliver to the user whatever is in the dot-forward takes over.
That is probably procmail. Anyway, it constitutes a local delivery agent.
beating around the bush, lets have a good look at logs, ok?
Logs? he's on systemd -- aren't the logs in binary somewhere -- if
cleared? I.e. some systemd proponents thought logging wasn't that
that they could be tossed each boot for most users...so he may have to go
generate some before we can read them.
Once again, Linda, you are spreading misinformation.
Logs are whatever you want them to be; systemd only logs what systemd
does. Your oft-stated anti-systemd prejudices are showing and have no
relevance here so please put them back in the box.
As Carlos and I have made very clear in this thread, all these
components can log directly to a file or to syslog. The point is that
you need to enable that and to make sure the logging level is, as I keep
pointing out, adequate. Setting it to "error" is of no use when you
Please, Linda, stop spreading misinformation. Most of your assertions
about what these things cannot do is easy disproved by a few seconds
Many of us get annoyed when we are told that things we've been doing for
years and years with not problems are 'impossible'. Back to my point
about the verb and the noun.
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org