SMTPd
Everett M. Greene
[Why change if it works?]
Recently, I was trying to generate a number of test messages
to send to myself for purposes of testing a mailreader of my
own design and construction. When I generated the messages,
SMTPd didn't recognize their being present and wouldn't send
them. All the messages are placed in amitcp:mailspool where
SMTPd is supposed to be looking for them and both X.zzz and
D.zzz files are created there for each message.
Does anyone know if SMTPd has some magic incantation for which
it's looking to recognize what it considers to be "approved"
messages to send?
Everett M. Greene
> Everett M. Greene <moj...@iwvisp.com> wrote:
> >I am using SMTPd from many moons ago as my email poster.
>
> >Recently, I was trying to generate a number of test messages
> >to send to myself
>
> >SMTPd didn't recognize their being present and wouldn't send
> >them.
>
> >Does anyone know if SMTPd has some magic incantation for which
> >it's looking to recognize what it considers to be "approved"
> >messages to send?
>
> Could it be that smtpd is trying to avoid a loop condition?
I don't know what kind it would be avoiding.
> Technically I would expect your poster app to consider your
> tst msg as not to be routed out, but instead being handled
> internally, provided it is at all capable.
All I see when my mailreader creates an outbound message is
an X.nnn and D.nnn file pairs in amitcp:mailspool. (The
mailreader has been told to spool the outbound messages.)
The "nnn" part of the file names appears to be a random
number of 9 decimal digits. I thought maybe there's some
parity check for valid file numbers or similar validity
test that SMTPd uses.
Example "names" I see at the moment are X.949567852 and
D.949568344.
Everett M. Greene
> Everett M. Greene <moj...@mojaveg.lsan.mdsg-pacwest.com> wrote:
> >lkjbkjh <nos...@nospam.invalid> writes:
> >> >Recently, I was trying to generate a number of test messages
> >> >to send to myself
> >> >SMTPd didn't recognize their being present and wouldn't send
> >> >them.
> >>
> >> Could it be that smtpd is trying to avoid a loop condition?
>
> >I don't know what kind it would be avoiding.
>
> well, I thought the possibility of having outbound mail from yourself,
> addressed to yourself, that this could be considered a mail loop
> situation to be avoided, simply by not sending it, or if configured,
> to be delivered to postmaster on the local system.
I see what you were thinking. However, sending messages to
oneself is a normal activity (as in CCing yourself in a
message). SMTPd is simply taking the files it finds and
sending them to the ISP. It doesn't know and doesn't care
that the message will be returned via some other means.
> your smtpd should really have a log that could tell the condition
> of the current spool, and if any errors have been met previously.
> sometimes a log functionality has to be manually configured.
>
>
> >> Technically I would expect your poster app to consider your
> >> tst msg as not to be routed out, but instead being handled
> >> internally, provided it is at all capable.
>
> >parity check for valid file numbers or similar validity
> >test that SMTPd uses.
>
> I doubt it. I'd think the numbers/filenames are just ment to
> be unique. they may be generated partly from your system time
> source or some random function. dont take this as any facts tho.
> just my thoughts on the issue.
That's what I think also but something about it doesn't work.