🚀 go-pugleaf

On Friday, in article <1343367560snz@nospam.demon.co.uk>
     pete@nospam.demon.co.uk wrote:

> In article <20120726.1320.929535snz@twoplaces.co.uk>
>            simon@twoplaces.co.uk "Simon Turner" writes:
> [snip]
> It's reassuring to learn that there is Life After Migration :)
> 
> I've still not been migrated -- at least I've received no notification 
> of migration, and the original 671 byte email is still not budging 
> from the punt.

Really?  It must be more than 30 days now, so it should should have
bounced and/or been silently deleted; their incompetent forgery really
did mess up the SDPS system... 8-)

> > Brief GremNOS status report: non-compliant "Return-Path:" fields are now
> > handled, and I've fixed the bug that stopped it putting POP3 messages in
> > the specified mailbox[*], but at present you have to either (a) set up
> > separate mailboxes for all your active usernames, then collect for each
> > mailbox separately, or (b) leave the single "administrator" mailbox as
> > the catch-all and put up with all messages being put into a single
> > mailbox, regardless of the original recipient address.
> 
> Probably too early to ask, but is there a new POP3 zip available yet?  

I've done new builds of the usual suspects with POP3SMTP added to their
configs; do you want a new build, or just the new pop3smtp.c and
smtpserv.c that I changed yesterday?  (ISTR you use you own modified
Lite build, BICBW.)

> And as probably the only person using "smtp queue" and delivering 
> locally, will the single "administrator" mailbox suffice?  (Of course 
> I'll discover this in due course, but just thought I'd ask as you've 
> BTDT with the code changes.)

Depends on whether you want to deliver to more than one mailbox.  Until
I've written the header-parsing stuff for automatic recipient detection,
there is no way for POP3 on the new platform to determine who the actual
recipient of a message was: so if all you have is the single default
"administrator" username, all you can do is download everything from
that username's mailbox as though it had been sent to a single local
address (which will be "administrator" by default, but can be overridden
to some other name of your choice).

At present I've got three usernames set up (the original administrator
and two others), and -- as you have to do nowadays -- am collecting
separately for each one, with each collection going to a different local
address.  Not ideal, but acceptable (especially since very little of my
Demon mail is of interest to me: < 5 per year on average).  Once I've
got auto-recipient-detection done, I may revert to just having the
administrator username.

> I think I'll disable all mailkill functionality at migration-time to 
> ensure I miss nothing.  I assume the POP3 GremNOS just issues a delete 
> for a mailkill match and logs the deletion?  If not I'll try to 
> implement something like this when the new source becomes available.

Right now, without the *ENV data, it doesn't try to validate the sender,
so mailkill doesn't work with POP3 on the new platform (but it will work
with the old SDPS platform).

When mailkill does match, it logs the rejection just as for SMTP, but it
doesn't explicitly log the POP3 deletion: it is taken as read.  That
could easily be changed, though.  (There's no separate POP3 log; just
the SMTP log.)  If you've set "pop3 bounce on" (which I do *not*
advise!), it will generate a DSN and send it to the address in the
"Return-Path:" header field.

-- 
Simon Turner                                    DoD #0461
simon@twoplaces.co.uk
    Trust me -- I know what I'm doing!          -- Sledge Hammer